dsh-tencent-docs-bridge: Let DeepSeek Harness Operate Tencent Docs in Natural Language

What Does It Do?

Tencent Docs MCP Bridge is a DSH plugin for DeepSeek Harness that lets you operate Tencent Docs in plain language from inside the harness. It connects to the official MCP endpoint of the Tencent Docs open platform and reuses the official MCP client, so the plugin itself only handles credential retrieval and config injection. Credentials are your own space_secret, kept only in a local vault or environment variables, with zero plaintext in the repository or config files. It is maintained by hs666-ai under the MIT license as a community, unofficial project.

Core Features

• Natural-language document editing: ask the model to change row 5 of a sheet to 100 and highlight it, and the request runs through the official MCP endpoint.
• Self-contained credential chain: resolves tokens from environment variables, a local vault, or a local gateway, so no token is ever embedded in the repo.
• Dynamic mounting of the official client: after retrieving a token at startup it mounts the official MCP client, exposing tools under the mcp__tencent-docs__ prefix such as sheet info, cell writing, and file search.
• Local credential vault: stores secrets with tightened permissions and logs only a length-plus-first-four-characters fingerprint, so the model sees tool results but never the token.
• Declarative fallback mode: if you prefer not to use runtime mounting, you can declare the MCP entry manually in your profile config with the token injected via environment variable.

How to Use This Plugin?

After enabling it in DSH and restarting, the plugin automatically mounts the official MCP client and its tools appear under the mcp__tencent-docs__ prefix. Before that, prepare your own space_secret: use the bundled credential CLI to scan a QR code in the browser and write it into the local vault, or switch to an environment variable, or read it from a compatible local gateway. To verify, just tell the model to list your recent Tencent Docs; to switch to manual declaration instead, add the MCP entry to your profile config and turn off runtime mounting.

How to Troubleshoot This Plugin?

Expired credentials are the most common issue: once a space_secret is rotated the old value stops working immediately, so retrieve and store a fresh one. If the tools never appear, first confirm the plugin loaded correctly with the profile and that the official MCP client is in place, then restart DSH so mounting takes effect. Rejected calls usually mean the official rate limit was hit, since the free tier allows 2000 calls per day and that limit is enforced by the official service rather than bypassed here. To inspect credential state, use the status command of the credential tool, which shows only a redacted vault summary with no plaintext.