MCP Client
Connect an external MCP server and register its advertised tools inside DSH.
On this page
Many official DSH packages are already shipped in the Standard preset or host runtime. Check the install status below before adding dependencies or editing a composition.
Install and usage entry
Optional official capability
This package is not a normal Standard agent-preset row. Use the configuration below and the official source as the authority for a custom composition.
Where you use it
Custom composition → configure one MCP Client instance per server → restart/reload → use the registered mcp__<server>__<tool> tools.
What it does
@deepseek-ai/dsh-mcp-client
- Connects to MCP servers over stdio or Streamable HTTP.
- Registers discovered tools under server-qualified names such as mcp__server__tool.
- Can reconnect after a lost stdio connection using the plugin's reconnect settings.
Is it already enabled?
MCP Client is an official package, but it is not one of the rows shown in the built-in Standard preset. Add one plugin instance for each MCP server you want to connect.
Configuration example
Use this as a reference when editing a custom Cordis composition. Installing a dependency does not by itself guarantee the plugin is mounted; the composition still controls what runs.
- id: mcp-github
name: '@deepseek-ai/dsh-mcp-client'
config:
serverName: github
transport: stdio
command: npx
args: ['-y', '@modelcontextprotocol/server-github']
env:
GITHUB_TOKEN: !!js process.env.GITHUB_TOKENHow to verify it
- Restart or reload the composition after adding the MCP row.
- Check that tools with the mcp__<serverName>__ prefix appear.
- Call one read-only MCP tool before allowing mutations.
Limits and boundaries
- The official bridge exposes MCP tools; MCP Resources and Prompts are not bridged by this package.
- Each live MCP instance needs a unique serverName.
- Secrets should come from environment variables or another credential mechanism, not literal public config examples.