connect_mcp_server
Starts an MCP server in a project sandbox and publishes its tools; use it when automatic detection fails or the server needs custom arguments or environment variables.
Instructions
Start an MCP server that lives inside a project's sandbox (stdio transport) and publish its tools as "__". Use it when the project is an MCP server that was not detected automatically or needs arguments or environment variables. Registering the same name again replaces the earlier registration. Environment values are stored unencrypted in the local registry file.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project": "<project>",
"command": "<command>"
},
"name": "connect_mcp_server"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Working directory (default /workspace/repo; relative paths resolve against it). | |
| env | No | Environment variables for the server, e.g. API keys. | |
| name | No | Name for this server within the project (default: the program name). | |
| command | Yes | Program and arguments, e.g. ["node", "build/index.js"] or ["mcp-server-filesystem", "/workspace/work"]. Not interpreted by a shell. | |
| project | Yes | Installed project: its slug, or its id such as "github:owner/name". |