Skip to main content

Connect MCPBundles on Cursor

For how MCP works in Cursor — mcp.json locations, stdio vs remote URLs, OAuth, and troubleshooting with any server — read How to Connect MCP Servers to Cursor.

This page covers connecting MCPBundles MCP servers only.

Requirements​

  • Cursor (recent release with MCP support)
  • An MCP server enabled in your MCPBundles dashboard
  • Credentials connected for the providers on that MCP server

Time to complete: about 2 minutes

Quick start: one-click install​

Install MCPBundles in Cursor →

Cursor shows the server name and URL, then adds it to your MCP config. Complete OAuth when prompted so tools can run.

Manual setup: your MCP server URL​

  1. Open your MCP server in the MCPBundles dashboard.
  2. In Quick Setup, copy the MCP server URL (HTTPS, includes your server slug).
  3. Add it to ~/.cursor/mcp.json or .cursor/mcp.json in your project:
{
  "mcpServers": {
    "mcpbundles": {
      "url": "https://mcp.mcpbundles.com/bundle/YOUR-SERVER-SLUG"
    }
  }
}
  1. Quit Cursor completely and reopen it so MCP servers reload.

MCPBundles CLI (does not edit Cursor)​

pip install mcpbundles
mcpbundles login   # first time
mcpbundles init

mcpbundles init writes the MCPBundles CLI skill (.skills/mcpbundles-cli/) so coding agents learn discovery and tool calls. It does not change Cursor's mcp.json. Use the one-click install or manual setup above for Cursor.

MCPBundles-specific issues​

SymptomFix
Tools missing after config changeFully quit Cursor and reopen; MCP loads on startup.
Authentication errors on tool callsReconnect provider credentials in the dashboard (OAuth or API key).
Wrong or stale URLCopy the URL again from Quick Setup on the MCP server page.

For host JSON, transport, and OAuth errors that are not MCPBundles-specific, see Fix MCP connection errors. For dashboard credential states, see Troubleshooting MCPBundles connections.