41 lines
1011 B
Markdown
41 lines
1011 B
Markdown
# MCP client configuration
|
|
|
|
## Remote HTTP
|
|
|
|
Use an API key configured as `SUBJECT=TOKEN` in `CODING_AGENT_MCP_API_KEYS`.
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"coding-agent-mcp": {
|
|
"transport": "http",
|
|
"url": "https://mcp.example.com/coding-agent/mcp",
|
|
"headers": {
|
|
"Authorization": "Bearer REPLACE_WITH_TOKEN",
|
|
"x-workspace-subpath": "project-a"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
This uses the standard Streamable HTTP endpoint. The workspace subpath is bound during the initial `initialize` request and remains immutable for the MCP session.
|
|
|
|
For a client that only supports the former SSE transport, use `https://mcp.example.com/coding-agent/sse`. The older custom `/events` endpoint is also retained for existing integrations.
|
|
|
|
## Local stdio
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"coding-agent-mcp": {
|
|
"command": "node",
|
|
"args": [
|
|
"/absolute/path/to/coding-agent-mcp/src/coding-agent-index.js",
|
|
"--root",
|
|
"/absolute/path/to/workspace"
|
|
]
|
|
}
|
|
}
|
|
}
|