MCP servers¶

MCP adds tools from child processes or remote HTTP services. Server tools are named mcp_<server>_<tool>.

Two kinds of server¶

Transport	Configuration	Execution
stdio	`command`, `args`, `env`	Launch a local program
Streamable HTTP	`url`, `auth_header`, `headers`	Connect to a service

Adding a server¶

gdc mcp add git uvx --arg mcp-server-git --arg=--repo --arg .
gdc mcp add-http docs https://example.com/mcp --auth-header "Bearer YOUR_TOKEN"

Or edit configuration:

[mcp.servers.git]
command = "uvx"
args = ["mcp-server-git", "--repo", "."]
trusted = false

[mcp.servers.docs]
url = "https://example.com/mcp"
auth_header = "Bearer YOUR_TOKEN"
trusted = false

Managing servers¶

gdc mcp list --json
gdc mcp trust git
gdc mcp trust git --no
gdc mcp remove git

Edits preserve TOML comments and formatting.

Scope: project vs. user¶

Scope	File
`project` (default)	`<project>/.gdc/config.toml`
`user`	`~/.gdc/config.toml`

Set --scope user on modifying commands for user-wide configuration.

Trusted or not¶

Untrusted server tools require approval unless a remembered grant or rule allows them. trusted = true allows tools without an approval prompt. Review grants with gdc permissions list --server <name>. See MCP configuration.