Registry Files

MCP servers are defined in two places:

• mcp-servers.json — server definitions (command, args, env)
• config.json — target config and optional server toggles

In a checkout, edit these files directly. With the published package, they ship as packaged defaults.

User Registry

User-registered MCP servers live in:

~/.agents/library/mcp-servers.json

Add a user MCP server:

bgng library add mcp my-server.json --as my-server

Machine-wide active MCP defaults live in ~/.agents/bgng/config.json under defaults.mcpServers.

Inspecting MCP State

bgng mcp list
bgng mcp list --json

Applying MCP Config

Preview before writing:

bgng mcp apply --dry-run

Apply to all targets:

bgng mcp apply

Limit to one target:

bgng mcp apply --target=cursor

Notes

• Platform-provided entries can live in the registry but are excluded from generated local tool configs
• Optional servers are included only when enabled in config.json
• Parallel MCP is controlled by config.parallel.mcp.enabled
• Project-local extension settings such as extensions.parallel.mcp are applied when commands run inside that project