{"version":"2.1.301","anchor":"org-mcp-restriction-keeps-only-repository-tools-of-claude-co","canonical_anchor":"org-mcp-restriction-keeps-only-repository-tools-of-claude-co","heading":"Organizations that restrict MCP servers lose some remote-session tools","tier":"notice","area":"MCP","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/org-mcp-restriction-keeps-only-repository-tools-of-claude-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Organizations that restrict MCP servers lose some remote-session tools\n\nIf your organization restricts MCP servers, Claude Code's own server in remote sessions keeps only its repository tools, without routines or PR tools\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. In remote sessions, where Claude Code runs in the cloud rather than on your computer, Claude Code adds an MCP server of its own. When your organization restricts which MCP servers may be used, Claude Code now keeps only that server's repository tools and says so. These tools are not available:\n\n- Scheduling routines.\n\n- Steering the session.\n\n- Pull request activity.\n\n**Why**\n\nIf your organization has an MCP policy, expect these remote-session tools to be missing.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}