From 877855d1ee2abe95f5656113174d893be4d2122a Mon Sep 17 00:00:00 2001 From: Stibbs Date: Wed, 27 Aug 2025 07:27:44 +1000 Subject: [PATCH] docs: mcp access mgmt instructions (#2087) --- .../web/src/content/docs/docs/mcp-servers.mdx | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/packages/web/src/content/docs/docs/mcp-servers.mdx b/packages/web/src/content/docs/docs/mcp-servers.mdx index 861efc6c..207b328b 100644 --- a/packages/web/src/content/docs/docs/mcp-servers.mdx +++ b/packages/web/src/content/docs/docs/mcp-servers.mdx @@ -91,3 +91,39 @@ Local and remote servers can be used together within the same `mcp` config objec } } } +``` + +--- + +## Granular access management + +If you have a large number of MCP servers you may want to disable them globally +and manage access at the agent level instead. To achieve this: + +1. Configure the MCP server. +2. Disable it as a tool globally. +3. In your [Agent Configuration](/docs/agents#agent-configuration) enable +the MCP server as a tool. + +```json title="opencode.json" +{ + "$schema": "https://opencode.ai/config.json", + "mcp": { + "my-mcp": { + "type": "local", + "command": ["bun", "x", "my-mcp-command"], + "enabled": true + } + }, + "tools": { + "my-mcp*": false + }, + "agent": { + "my-agent": { + "tools": { + "my-mcp*": true + } + } + } +} +```