Cursor MCP and token overhead

Each enabled MCP server in Cursor adds tool schemas to Agent context on every turn—even when no tool is called.

Hub: Tokenminning in Cursor.

Disable MCP

Cursor MCP docs :

• Disable servers you are not using this week
• One narrow, task-specific server beats five overlapping ones
• Audit after spikes in dashboard Input tokens — Usage

MCP does not replace built-in codebase search for local fixes — schemas still load if enabled.

Related

• Cursor hub
• Usage dashboard
• Context hygiene