Summary
There is no way to remove or hide the built-in "Not connected" connectors (Asana, Atlassian, Box, Canva, HubSpot, Intercom, Krisp, Linear, Microsoft 365, Miro, monday.com, Notion) from the Connectors panel.
Expected behavior
Users should be able to remove or hide connectors they have no intention of using, to keep the list clean and avoid noise.
Actual behavior
- The Connectors UI (claude.ai desktop app) shows only a Connect button for unconnected integrations — no remove/hide/dismiss option.
claude mcp remove "<name>" explicitly blocks removal with: Cannot remove MCP server from scope: claudeai
- These connectors are fetched server-side and synced into the
claudeai scope, which the CLI treats as read-only.
Steps to reproduce
- Open Claude Code desktop app → Connectors panel
- Click any "Not connected" connector (e.g. Linear)
- Observe: only a "Connect" button is shown, no way to remove
OR run:
claude mcp remove "claude.ai Linear"
# Error: Cannot remove MCP server from scope: claudeai
Impact
- Clutters the Connectors panel with services the user will never use
- These connectors also appear as deferred tools in every session, adding noise to the system context
Request
- Add a Remove or Hide option per connector in the UI
- OR allow
claude mcp remove to work for claudeai-scoped servers
Summary
There is no way to remove or hide the built-in "Not connected" connectors (Asana, Atlassian, Box, Canva, HubSpot, Intercom, Krisp, Linear, Microsoft 365, Miro, monday.com, Notion) from the Connectors panel.
Expected behavior
Users should be able to remove or hide connectors they have no intention of using, to keep the list clean and avoid noise.
Actual behavior
claude mcp remove "<name>"explicitly blocks removal with:Cannot remove MCP server from scope: claudeaiclaudeaiscope, which the CLI treats as read-only.Steps to reproduce
OR run:
Impact
Request
claude mcp removeto work forclaudeai-scoped servers