Published March 30, 2026
How to Set Up MCP in Cursor: Complete Setup Guide in 2026
Cursor is one of the most AI-native code editors available today, and adding Model Context Protocol (MCP) support takes it to the next level. This guide walks you through the complete setup — from enabling MCP in Cursor to connecting production-grade servers — in about 15 minutes.
Why Use MCP with Cursor?
Cursor already brings powerful AI assistance directly into your code editor — autocompletes, chat, and refactoring all powered by large language models. But by itself, Cursor operates in a sandbox. It knows your open files. It does not know your GitHub repos, your running databases, or your production logs.
MCP bridges that gap. When you connect an MCP server to Cursor, your AI assistant gains real-time access to external tools and data. You can ask Cursor to:
- Pull the latest commits and issues from your GitHub repository
- Query your PostgreSQL or MySQL database directly from a chat prompt
- Search the web without leaving the editor
- Read and write files outside the current project directory
- Interact with Slack, Notion, or other workplace tools
The result is an AI coding assistant that is genuinely aware of your entire development context — not just the file you happen to have open.
Prerequisites
Before starting, make sure you have the following:
Cursor installed
Download Cursor from cursor.com. The free tier supports MCP connections, though some advanced features require a Pro subscription.
Node.js 18+
Most MCP servers run on Node.js. Install it via nodejs.org or use a version manager like nvm. Verify with: node --version
npm or pnpm
Comes bundled with Node.js. You will need this to install MCP server packages.
A Cursor account
Sign up at cursor.com. An account is required to enable MCP features and sync settings across devices.
How to Enable MCP in Cursor
Cursor does not expose MCP settings through a dedicated UI panel yet. Instead, MCP configuration is managed through a JSON file that Cursor reads on startup. Here is the full walkthrough.
Step 1: Open Cursor Settings
Launch Cursor and open the settings panel. You can do this by pressing Cmd + , (macOS) or Ctrl + , (Windows/Linux). Navigate to the Features section and scroll down to MCP.
If you do not see an MCP section yet, make sure you are on the latest version of Cursor — the feature was added in version 0.4x. Update Cursor if needed.
Step 2: Locate the MCP Configuration File
Cursor stores MCP configuration in a JSON file at:
~/Library/Application Support/Cursor/cursor_mcp_config.json
(macOS) — On Windows it is at %APPDATA%/Cursor/cursor_mcp_config.json
You can also access this file directly from Cursor Settings → Features → MCP by clicking Edit JSON.
Step 3: Add Your First MCP Server
Open the configuration file and add your first MCP server. Below is a complete example using the popular filesystem MCP server:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem"],
"env": {
"allowedDirectory": "/Users/yourname/projects"
}
}
}
}This config tells Cursor to launch a filesystem MCP server that is only allowed to access /Users/yourname/projects. Always scope access with allowedDirectory for security.
Adding MCP Servers to Cursor — JSON Config Deep Dive
The JSON configuration format follows the standard MCP client specification. Each server entry requires at minimum a command and args field. Here is the anatomy of a full Cursor MCP config:
{
"mcpServers": {
"server-name": {
"command": "npx", // or "node" for local JS servers
"args": ["-y", "package-name"],
"env": {
"KEY": "VALUE" // server-specific environment variables
},
"scope": "project" // "project" or "global"
}
}
}The scope field determines whether the server is available to just the current project or to all Cursor projects. Use project scope for team-specific servers and global for universal tools like web search.
Production tip: For servers that need to run continuously and handle real workloads, consider hosting them with MCPize. It handles deployment, scaling, and access management — no server运维 required.
Testing MCP Connections Inside Cursor
After saving your configuration file, restart Cursor. You should see an MCP indicator (usually a small tool icon) in the Cursor AI chat panel when servers are active.
To verify a connection is working, try asking Cursor a question that triggers the MCP server. For example, with the filesystem server:
If Cursor responds using the MCP tool, the connection is live. If it fails or says the tool is unavailable, check the console for error messages and verify your JSON config is valid.
You can also use the MCP Inspector CLI to test server connections independently before connecting them to Cursor.
Recommended MCP Servers for Cursor Users
Here are the most useful MCP servers to connect to Cursor in 2026, all available on the MCPize Marketplace:
Filesystem (@modelcontextprotocol/server-filesystem)
Read and write files outside the current project. Essential for cross-directory searches and bulk edits. Scope carefully with allowedDirectory.
GitHub (@modelcontextprotocol/server-github)
Browse repos, read issues, review PRs, and check CI status — all from inside Cursor. Set up with a personal access token.
Brave Search (@modelcontextprotocol/server-brave-search)
Web search directly from the Cursor chat. Great for looking up documentation, library versions, or Stack Overflow answers without switching tabs.
PostgreSQL (@modelcontextprotocol/server-postgres)
Run SQL queries against your database and get results back in natural language. Useful for debugging data issues or generating reports.
Slack (@modelcontextprotocol/server-slack)
Send messages, check channel activity, and manage notifications from Cursor. Perfect for dropping a quick "deployment done" message mid-sprint.
Common Issues and Fixes
❌ MCP section not visible in Cursor settings
Update Cursor to the latest version. MCP support was added in Cursor 0.4x. If it is still missing after updating, check that you are signed into a Cursor account.
❌ Server starts but Cursor shows "tool unavailable"
Check the JSON config for typos. A missing comma or unmatched brace will silently prevent servers from loading. Validate your JSON at jsonformatter.curiouscat.com or similar.
❌ "command not found" error for npx
Ensure Node.js is installed and npx is in your PATH. Run which npx in your terminal to confirm. If missing, reinstall Node.js.
❌ Filesystem server access denied errors
The allowedDirectory in your config must exactly match the directory you are trying to access. Trailing slashes matter — use a normalized path without trailing slashes.
❌ GitHub server returns 401 Unauthorized
Generate a new personal access token at github.com/settings/tokens. Make sure it has the required scopes (repo for full repo access, read:user for user data). Paste it into the env.GITHUB_PERSONAL_ACCESS_TOKEN field.
Boost Your Cursor Workflow with Raycast
While Cursor handles your AI-assisted coding, Raycast supercharges the rest of your macOS workflow. Think of it as a universal command bar that launches apps, runs scripts, manages clipboard history, and integrates with dozens of tools — all without leaving the keyboard.
Used together, Cursor and Raycast form a powerful pair: Cursor for AI-first code editing, Raycast for everything else. Many developers find that once they go all-in on Raycast, switching back to Spotlight feels like downgrading.
Get Started Today
Setting up MCP in Cursor takes less than 15 minutes. Here is your action plan to get running right now:
- Open Cursor Settings (Cmd + ,) and navigate to Features → MCP. Click Edit JSON.
- Add the filesystem MCP server using the JSON config example above. Replace
/Users/yourname/projectswith your actual project directory. - Restart Cursor and look for the MCP tool indicator in the AI chat panel.
- Ask Cursor to read or write a file outside your current project to verify the connection works.
- Browse the MCPize Marketplace and add more servers — the GitHub and Brave Search servers are particularly powerful additions.
Once you have your first MCP server connected and working, you will immediately see how much more context-aware your Cursor AI assistant becomes. From there, it is a matter of exploring which servers fit your workflow best.
Ready to scale? Deploy production MCP servers with MCPize — no server management required. Their marketplace has one-click installs for GitHub, PostgreSQL, Slack, and dozens more.