cordis.yml builder
Configure one MCP server
1–32 letters, numbers, underscore, or hyphen. Must be unique.
Unique Cordis plugin entry ID.
Executable DSH will spawn.
Comma-separated; each item becomes one YAML argument.
One OUTPUT_NAME=PROCESS_ENV_NAME per line. Enter names, never literal secret values.
Leave empty to omit Authorization.
Generated cordis.yml entry
Configuration fields are valid.
Where this entry belongs
The official MCP client bridge uses one plugin instance per MCP server in cordis.yml. It registers each server Tool under a qualified name such as mcp__github__create_issue. Server names must be unique across live instances.
What the generator validates
| Field | Boundary |
|---|---|
| serverName | Required for both transports; 1–32 characters matching letters, numbers, underscore, or hyphen. |
| command / args / env | stdio process and environment references. |
| url / headers | Streamable HTTP endpoint and optional authentication headers. |
| toolCallTimeoutMs | Per-tool timeout; official default is 60,000 ms. |
| reconnect | Automatic reconnect, delay backoff, and attempt budget. |
Current MCP bridge limitations
- Tools only: Resources and Prompts are not bridged.
- Schema cost: discovered Tool definitions consume context on each request while registered.
- Cache stability: unchanged tools stay prefix-stable; a changed tool set or schema can invalidate reuse from the first changed token.
- Non-text rendering: images, audio, resources, and unsupported blocks become placeholders in native model context even though canonical execution data retains JSON blocks.
- Startup timeout: connection/discovery currently inherits the MCP SDK’s 60-second request default.
Primary source
Official DSH MCP client README ↗ — configuration fields, namespacing, behavior, reconnect, model experience, and current limitations.