Add and govern MCP servers in CodeBuddy CLI (stdio/SSE/HTTP)
At a glance
Official CodeBuddy MCP docs show how to add local or remote MCP servers with codebuddy mcp add, pick user/project/local scopes, approve project servers, and lock tools with mcp__server__tool allow/deny rules. This workflow is listed under sponsor, coding-agent, devtools, mcp, cli, security.
- Agents / tools
- CodeBuddy Code, MCP
Building a tool for these workflows? See weekly rates.
What they did
Install or open CodeBuddy CLI, then add an MCP server with codebuddy mcp add (stdio for a local process, --transport sse or http for remote URLs). Choose --scope user, project, or local (priority local > project > user for same-named servers). List/get/remove with codebuddy mcp list|get|remove. For project-scope servers, approve on first connect; in non-interactive -p/--print runs, pre-allow via --settings enableAllProjectMcpServers or enabledMcpjsonServers. Put secrets in ${ENV} / ${ENV:-default} expansions instead of hardcoding tokens. Optionally set defer_loading when a server exposes many tools, and gate tools with permissions allow/deny/ask using mcp__<server> or mcp__<server>__<tool> patterns.
Worth knowing
Project-scope MCP needs an explicit approve on first connect; print mode cannot show that UI so you must pass --settings. mcp__* only works in deny/ask—putting it in allow is a no-op. Prefer ~/.codebuddy/.mcp.json (user) and <project>/.mcp.json (project); older mcp.json paths are deprecated. Oversize MCP output defaults to a session tool-results file above MAX_MCP_OUTPUT_TOKENS (default 20000); set CODEBUDDY_DISABLE_MCP_LARGE_OUTPUT_FILES=1 to force truncation instead.
