Skip to content
Back to search

cove-sensory-mcp

Give text-only LLMs eyes and ears through a privacy-safe local MCP server.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/moonlin1213--cove-sensory-mcp/badge.svg)](/listings/moonlin1213--cove-sensory-mcp)

HTML

<a href="/listings/moonlin1213--cove-sensory-mcp"><img src="/api/listings/moonlin1213--cove-sensory-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

This repository is distributed as source code. It does not require a packaged desktop app or a standalone installer. Install [Git](https://git-scm.com/), Python 3.11+, and [uv](https://docs.astral.sh/uv/), then clone and set up the locked environment:

git clone https://github.com/moonlin1213/cove-sensory-mcp.git
cd cove-sensory-mcp
uv sync --locked
uv run cove-sensory-mcp doctor
uv run cove-sensory-mcp print-config --client generic

Supported renderers are `generic`, `codex`, `claude-desktop`, and `claude-code`. Copy the printed local stdio entry into your client, restart it, then ask the Agent to call `sensory_setup_guide`. Official configuration references: [Codex MCP](https://developers.openai.com/codex/mcp/), [Claude Desktop](https://modelcontextprotocol.io/quickstart/user), and [Claude Code MCP](https://docs.anthropic.com/en/docs/claude-code/mcp). Client surfaces change independently; if a surface does not support local stdio MCP, run the server from a compatible host instead.

Run later commands from the cloned repository with `uv run cove-sensory-mcp ...`. FFmpeg is optional for initial setup and image sensing, but video/audio preparation requires a working system FFmpeg discoverable on `PATH` or configured locally.

Do not paste an API key into chat. Run `cove-sensory-mcp configure` in a local terminal: hidden input goes to the operating-system credential store, while `env:VARIABLE_NAME` stores only the variable name. Add each readable local directory separately with `cove-sensory-mcp configure paths`.

Continue an interrupted setup

Run `uv run cove-sensory-mcp configure` again and select the same Provider. For a custom Provider, select `custom` and enter its existing identifier. The wizard detects the saved entry **before** asking for credentials and offers to continue setup. It keeps the saved model, endpoint, and credential source; this is not a credential-edit or overwrite operation.

Choose the eye and/or ear roles you want to enable. The wizard checks whether the credential can be read locally, then requests permission to send tiny test media for only the selected, still-unverified capabilities. Previously verified capabilities can be enabled without another paid test. A capability becomes the default only after verification succeeds. Replacing a different default requires a separate confirmation; continuing an existing default preserves its authorized fallbacks. Declining or cancelling keeps the Provider settings and any completed verification, so you can retry.

Use these local diagnostics when setup is incomplete:

uv run cove-sensory-mcp --version
uv run cove-sensory-mcp status
uv run cove-sensory-mcp doctor

`status` distinguishes configured-but-not-verified capabilities from verified-but-not- enabled defaults, and checks local credential availability separately. `sensory_status` is a configuration-only MCP status tool: it does not read credentials or check Provider connectivity. Do not manually mark capabilities verified to bypass a failed test.

With `env:VARIABLE_NAME`, the variable must actually be set in the process running the MCP. Typing that reference does not set an API key. On Windows, a variable set only in one terminal is not necessarily available to an already-running desktop client; make it available to the MCP launch process and restart the terminal/client as needed. Missing local credentials are not the same as a Provider rejecting a key. Verification failures show bounded error codes, not secret values or raw Provider responses. Never send API keys, environment dumps, or entire configuration files in chat.

You do not need all five capabilities enabled: MiniMax's built-in eye covers `image` and `video_visual`, not hearing. In an MCP self-test, request only the capabilities you have configured (for example, `modalities: ["image", "video_visual"]`). The CLI `self-test` command still requests all five; use the configuration wizard for role-

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 141 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Cove Sensory MCP
  2. **Cove Sensory MCP——给纯文本 LLM 一双眼睛和耳朵** is a local stdio MCP server
  3. that lets an Agent ask configured multimodal providers to inspect an explicitly supplied
  4. image, video, audio file, or music file. It is a sensory layer only: it does not provide
  5. chat, memory, personality, playback, continuous monitoring, or a calling policy.
  6. ## Install and connect from source
  7. This repository is distributed as source code. It does not require a packaged desktop
  8. app or a standalone installer. Install [Git](https://git-scm.com/), Python 3.11+, and
  9. [uv](https://docs.astral.sh/uv/), then clone and set up the locked environment:
  10. ```console
  11. git clone https://github.com/moonlin1213/cove-sensory-mcp.git
  12. cd cove-sensory-mcp
  13. uv sync --locked
  14. uv run cove-sensory-mcp doctor
  15. uv run cove-sensory-mcp print-config --client generic
  16. ```
  17. Supported renderers are `generic`, `codex`, `claude-desktop`, and `claude-code`. Copy the
  18. printed local stdio entry into your client, restart it, then ask the Agent to call
  19. `sensory_setup_guide`. Official configuration references:
  20. [Codex MCP](https://developers.openai.com/codex/mcp/),
  21. [Claude Desktop](https://modelcontextprotocol.io/quickstart/user), and
  22. [Claude Code MCP](https://docs.anthropic.com/en/docs/claude-code/mcp).
  23. Client surfaces change independently; if a surface does not support local stdio MCP,
  24. run the server from a compatible host instead.
  25. Run later commands from the cloned repository with `uv run cove-sensory-mcp ...`.
  26. FFmpeg is optional for initial setup and image sensing, but video/audio preparation
  27. requires a working system FFmpeg discoverable on `PATH` or configured locally.
  28. Do not paste an API key into chat. Run `cove-sensory-mcp configure` in a local terminal:
  29. hidden input goes to the operating-system credential store, while `env:VARIABLE_NAME`
  30. stores only the variable name. Add each readable local directory separately with
  31. `cove-sensory-mcp configure paths`.
  32. ### Continue an interrupted setup
  33. Run `uv run cove-sensory-mcp configure` again and select the same Provider. For a
  34. custom Provider, select `custom` and enter its existing identifier. The wizard detects
  35. the saved entry **before** asking for credentials and offers to continue setup. It
  36. keeps the saved model, endpoint, and credential source; this is not a credential-edit
  37. or overwrite operation.
  38. Choose the eye and/or ear roles you want to enable. The wizard checks whether the
  39. credential can be read locally, then requests permission to send tiny test media for
  40. only the selected, still-unverified capabilities. Previously verified capabilities
  41. can be enabled without another paid test. A capability becomes the default only after
  42. verification succeeds. Replacing a different default requires a separate confirmation;
  43. continuing an existing default preserves its authorized fallbacks. Declining or
  44. cancelling keeps the Provider settings and any completed verification, so you can retry.
  45. Use these local diagnostics when setup is incomplete:
  46. ```console
  47. uv run cove-sensory-mcp --version
  48. uv run cove-sensory-mcp status
  49. uv run cove-sensory-mcp doctor
  50. ```
  51. `status` distinguishes configured-but-not-verified capabilities from verified-but-not-
  52. enabled defaults, and checks local credential availability separately. `sensory_status`
  53. is a configuration-only MCP status tool: it does not read credentials or check Provider
  54. connectivity. Do not manually mark capabilities verified to bypass a failed test.
  55. With `env:VARIABLE_NAME`, the variable must actually be set in the process running the
  56. MCP. Typing that reference does not set an API key. On Windows, a variable set only in
  57. one terminal is not necessarily available to an already-running desktop client; make
  58. it available to the MCP launch process and restart the terminal/client as needed.
  59. Missing local credentials are not the same as a Provider rejecting a key. Verification
  60. failures show bounded error codes, not secret values or raw Provider responses. Never
  61. send API keys, environment dumps, or entire configuration files in chat.
  62. You do not need all five capabilities enabled: MiniMax's built-in eye covers `image`
  63. and `video_visual`, not hearing. In an MCP self-test, request only the capabilities
  64. you have configured (for example, `modalities: ["image", "video_visual"]`). The CLI
  65. `self-test` command still requests all five; use the configuration wizard for role-
  66. specific testing and activation. A standalone self-test records verification but does
  67. not choose your default Providers; return to `configure` to enable them.
  68. ## Choose the eyes and ears
  69. - Gemini can be an eye for images/video and an ear for video audio, ordinary audio, and
  70. music.
  71. - MiniMax-M3 can be an image/native-video eye; it is not treated as an ear, so choose a
  72. separate audio provider for a video's soundtrack.
  73. - An OpenAI-compatible provider using the `audio_url_data_uri` media mode can serve as
  74. the ear on platforms that accept an `audio_url` content part (for example SiliconFlow's
  75. Qwen3-Omni-Instruct), covering audio, music, and video audio. One bounded retry covers
  76. transient 408, 429, 500, 502, 503, and 504 responses, connection/timeout failures, or
  77. malformed structured output, and may incur one additional Provider call or charge.
  78. - A custom provider must declare capabilities and pass the tiny-media self-test before
  79. those capabilities are advertised. The self-test sends project-created media, can
  80. incur a small API cost, and requires confirmation. It verifies that the Provider call
  81. returns a valid structured observation; it does not score the model's wording or
  82. description style.
  83. Media is sent only to the selected, authorized Provider. Its privacy policy, retention,
  84. region, and billing rules apply. Cross-provider fallback is never inferred. Local paths
  85. must be absolute and within configured roots. URLs must be direct HTTPS media URLs;
  86. redirects, credentials, private networks, localhost, and metadata endpoints are blocked.
  87. ## Tools
  88. The seven public tools are:
  89. - `sensory_status` — show redacted, verified capability status.
  90. - `sensory_setup_guide` — explain missing local setup without requesting secrets.
  91. - `sensory_self_test` — verify selected capabilities using tiny included media.
  92. - `sense_image` — inspect an authorized image; e.g. “read the visible labels.”
  93. - `sense_video` — inspect visuals and, when configured, its audio timeline.
  94. - `sense_audio` — describe speech and non-speech events in an audio clip.
  95. - `sense_music` — describe structure, rhythm, instrumentation, and key moments.
  96. Run `cove-sensory-mcp doctor` for local configuration, credential-presence, cache, and
  97. FFmpeg diagnostics. It never prints secret values or contacts a Provider. The optional
  98. FFmpeg download stays disabled until each platform binary has audited provenance; a
  99. working system FFmpeg can be used meanwhile.
  100. ## Uninstall and privacy
  101. Remove the `cove-sensory-mcp` Python tool with the installer you used, or run the
  102. standalone installer's uninstall command. Uninstall preserves configuration and OS
  103. credentials unless you explicitly request data removal. Temporary derived media is
  104. request-scoped and removed after completion; the original is never modified.
  105. The project is Apache-2.0. Dependencies and FFmpeg keep their own licenses; see
  106. [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md). Please read [SECURITY.md](SECURITY.md)
  107. before processing untrusted media.
  108. ## Development
  109. ```console
  110. uv sync --group dev
  111. uv run pytest
  112. uv run ruff check src tests scripts
  113. uv run mypy src/cove_sensory_mcp
  114. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.