Cursor MCP: How to Connect MCP Servers to Cursor

When To Use Cursor MCP

Use MCP when Cursor needs live context from files, GitHub, databases, browser automation, design files, or planning systems.

Starter Config

Begin with one server and verify it before adding more.

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"]
    }
  }
}

Common Mistakes

Most Cursor MCP failures are path, Node, npm, or environment variable issues.

• Verify node and npx are available in the environment Cursor uses.
• Avoid storing tokens directly in shared config.
• Test each server independently before combining configs.

Recommended Cursor MCP Rollout

Start with one server, verify it from Cursor, then add servers by category. Most teams should begin with filesystem or GitHub before connecting databases, browser automation, or design tools.

• Phase 1: filesystem or GitHub for project context.
• Phase 2: Playwright or Browser for UI verification.
• Phase 3: database, design, planning, or docs servers after permission review.

Environment Checklist

Cursor MCP issues often come from differences between terminal shells and GUI app environments.

node -v
npm -v
which node
which npx
printenv PATH

Cursor MCP Setup Steps

A reliable setup starts outside Cursor. Confirm the server command works in a terminal, then move the same command into Cursor's MCP configuration. This separates package, credential, and PATH problems from editor-specific behavior.

• Run the server command manually and confirm it starts without missing package errors.
• Use environment variables for tokens instead of hard-coding secrets in a shared config.
• Restart Cursor after changing MCP config so the app picks up the new process environment.
• Add one server at a time and keep a note of the exact command that worked.

Best Servers For Cursor

Cursor users usually get the most value from MCP servers that reduce context switching inside the editor. GitHub helps with pull requests and issues, filesystem can expose scoped local context, and Playwright or Browser can help verify frontend behavior.

• GitHub: useful when coding tasks start from issues, PRs, or code review comments.
• Filesystem: useful for scoped project reads when the editor context is not enough.
• Playwright or Browser: useful for UI checks after Cursor makes frontend changes.
• Database servers: useful only after read-only access and credential handling are reviewed.

Troubleshooting Flow

When Cursor MCP fails, avoid changing multiple settings at once. First identify whether the error happens before the server starts, while the server starts, or after Cursor connects to it.

1. Check the executable: which node && which npx
2. Run the exact MCP command in a terminal
3. Replace npx with an absolute path if Cursor cannot find it
4. Check required env vars
5. Restart Cursor and inspect the MCP status

FAQ