33 markdown files organized for GitBook import with SUMMARY.md navigation. Covers installation, core concepts, auto mode, configuration, all providers, cost management, skills, parallel orchestration, remote questions, teams, headless CI, and full command reference. User-facing only — no internal/dev content. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.7 KiB
1.7 KiB
MCP Servers
GSD can connect to external MCP (Model Context Protocol) servers for local tools, internal APIs, self-hosted services, or integrations not built in as native extensions.
Configuration Files
GSD reads MCP config from these project-local paths:
.mcp.json— repo-shared config (safe to commit).gsd/mcp.json— local-only config (not shared)
If both exist, server names are merged and the first definition found wins.
Supported Transports
| Transport | Config Shape | Use When |
|---|---|---|
stdio |
command + optional args, env, cwd |
Launching a local MCP server |
http |
url |
Connecting to an already-running server |
Examples
stdio Server
{
"mcpServers": {
"my-server": {
"type": "stdio",
"command": "/absolute/path/to/python3",
"args": ["/absolute/path/to/server.py"],
"env": {
"API_URL": "http://localhost:8000"
}
}
}
}
HTTP Server
{
"mcpServers": {
"my-http-server": {
"url": "http://localhost:8080/mcp"
}
}
}
Verifying a Server
After adding config, verify from a GSD session:
mcp_servers— confirms GSD sees the configmcp_discover(server="my-server")— confirms the server starts and respondsmcp_call(server="my-server", tool="<tool>", args={...})— confirms a real tool call works
Tips
- Use absolute paths for executables and scripts
- Set required environment variables directly in the MCP config's
envblock - Use
.mcp.jsonfor team-shared servers;.gsd/mcp.jsonfor machine-local ones - If a server depends on local paths or personal secrets, keep it in
.gsd/mcp.json