Best Cursor MCP Servers in 2026: 10 Tools That Supercharge Composer

Table of Contents

1. What Are Cursor MCP Servers?
2. How MCP Works Inside Cursor
3. How We Ranked Them
4. The 10 Best Cursor MCP Servers
5. Quick Comparison Table
6. How to Add an MCP Server to Cursor
7. Project-Level vs Global MCP Config
8. Troubleshooting Cursor MCP Setup
9. Frequently Asked Questions

What Are Cursor MCP Servers?

Cursor is an AI-first fork of VS Code, and its Composer agent is one of the strongest coding assistants shipping in 2026. Out of the box it already understands your local codebase. What it cannot do — without help — is reach anything beyond the files on disk. That is the gap MCP servers fill.

A Model Context Protocol server is a small program that exposes a set of tools over a standard JSON-RPC interface. When you connect one to Cursor, the Composer agent gains new abilities mid-task: open a pull request, run a SQL query, fetch the current version of a library's docs, take a screenshot of a running page, or read a Figma frame. The protocol was published by Anthropic in late 2024 and Cursor adopted it in 2025; by 2026 the ecosystem spans 75,000+ servers that Skiln aggregates in one place.

The important thing to understand is that "Cursor MCP servers" are not a special category. They are the same MCP servers that run in Claude Desktop, Claude Code, Windsurf, and Cline. Cursor simply happens to be one of the most popular clients for them, which is why "cursor mcp servers" has become its own search.

How MCP Works Inside Cursor

When Cursor starts, it reads your MCP config, launches each server as a background process, and asks each one for its list of tools. Those tools are then offered to the Composer agent. When you give Composer a task, it decides which tool to call, sends a structured request to the right server, and folds the result back into its reasoning.

Three things are worth knowing about Cursor's specific implementation:

• Tools surface to Composer, not chat. Unlike Claude Desktop's sidebar, Cursor routes MCP tools into the agentic Composer loop. You see tool calls inline as the agent works.
• There is a soft 40-tool ceiling. Cursor truncates the tool list it shows the model. If you run many servers, only the first tools are visible — keep your active set lean.
• stdio and SSE are both supported. Most servers use stdio (a local subprocess). Cursor also supports SSE and streamable HTTP for remote servers, which matters for the email and SaaS servers later in this list.

How We Ranked Them

We scored every MCP server in the Skiln directory on four signals: GitHub stars (community trust), commit recency (active maintenance), README quality (does it document Cursor setup), and breadth of workflow coverage (how many real Cursor tasks it unlocks). The 10 below scored highest on the composite — these are the servers we would add to a fresh Cursor install today.

The 10 Best Cursor MCP Servers

1. GitHub MCP

The single most useful MCP for Cursor users. Maintained by GitHub itself, it gives Composer read/write access to repositories, issues, pull requests, code search, and Actions. Ask Cursor to "open a PR for this branch with a summary of the diff" and it actually does it. See the full GitHub MCP review.

Best for: PR creation, issue triage, cross-repo code search from inside the editor.

Install: npx -y @modelcontextprotocol/server-github

2. Context7 MCP

The antidote to hallucinated APIs. Context7 fetches up-to-date, version-specific documentation for any library and injects it into Composer's context. Add "use context7" to a prompt and Cursor stops inventing methods that never existed. Indispensable when you work with fast-moving frameworks.

Best for: Accurate code generation against current library versions, migration work, unfamiliar SDKs.

Install: npx -y @upstash/context7-mcp

3. Playwright MCP

Hands Cursor a real Chromium browser. Composer can navigate to your running app, fill forms, click through flows, and take screenshots — then fix the bug it just reproduced. The tightest inner loop for front-end work.

Best for: Visual QA, reproducing UI bugs, end-to-end test scaffolding, scraping during research.

Install: npx -y @playwright/mcp@latest

4. Postgres MCP

Lets Cursor query any Postgres database through natural language. It introspects your schema and defaults to read-only, so you can ask "which users signed up last week and never returned" and get a real answer grounded in real rows while you code.

Best for: Schema-aware queries, data debugging, building reports without hand-writing SQL.

Install: npx -y @modelcontextprotocol/server-postgres "postgresql://user:pass@localhost/db"

5. Filesystem MCP

Cursor already edits files in your open workspace, but Filesystem MCP extends reach to folders outside the project — a shared design directory, a docs vault, a sibling repo — scoped to paths you explicitly allow.

Best for: Cross-project context, reading reference material outside the repo, multi-folder refactors.

Install: npx -y @modelcontextprotocol/server-filesystem /path/to/folder

6. Figma MCP

Bridges design and code. The Figma MCP lets Composer read frames, components, and design tokens directly from a Figma file, so "build this screen" can reference the actual layout instead of a vague description. A genuine accelerator for design-to-code work.

Best for: Translating designs to components, extracting design tokens, pixel-faithful UI builds.

Install: See the project README — requires a Figma access token in the config env.

7. Supabase MCP

The official Supabase MCP gives Cursor access to your Postgres database, auth users, edge functions, and branches. It can introspect schemas, run migrations, and debug RLS policies. If your stack is Supabase, this is a must-add. Compare it in our Supabase vs Postgres MCP guide.

Best for: Full-stack Supabase apps, RLS debugging, migration authoring.

Install: npx -y @supabase/mcp-server-supabase --access-token=YOUR_TOKEN

8. Sequential Thinking MCP

A planning and reflection tool that helps Composer break a complex change into ordered steps, track progress, and revise its approach. Especially useful for large multi-file refactors where the agent would otherwise lose the thread.

Best for: Multi-step refactors, architectural changes, anything that needs a plan before edits.

Install: npx -y @modelcontextprotocol/server-sequential-thinking

9. Notion MCP

Connects Cursor to your Notion workspace so the agent can pull spec docs, update task databases, or log decisions while you work. Handy when your requirements live in Notion and you want the agent to honor them without copy-paste.

Best for: Reading specs into context, updating project trackers, decision logs.

Install: npx -y @notionhq/notion-mcp-server

10. Exa Search MCP

Gives Composer high-quality web search built for AI. When you need current information — a new API change, a library release, a Stack Overflow fix — Exa returns clean, relevant results the agent can read instead of guessing from stale training data.

Best for: Live research, finding current fixes, grounding answers in fresh sources.

Install: npx -y exa-mcp-server (requires an Exa API key)

Quick Comparison Table

How to Add an MCP Server to Cursor

Adding an MCP server to Cursor takes under a minute. The universal recipe:

1. Open the MCP config. Either create ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project root, or use Settings, then Features, then MCP, then "Add new MCP server".
2. Add the server to the mcpServers object. Example for Context7 plus GitHub:

{   "mcpServers": {     "context7": {       "command": "npx",       "args": ["-y", "@upstash/context7-mcp"]     },     "github": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-github"],       "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..." }     }   } }

1. Save and check the dot. Cursor shows a status indicator next to each server. Green means connected; red means it failed to start.
2. Use it in Composer. Open Composer (Cmd/Ctrl+I), give it a task, and watch the agent call the tools inline.

The Skiln Config Generator outputs a ready-to-paste mcp.json for any combination of servers you pick — useful when you are setting up a new machine and want five servers at once.

Project-Level vs Global MCP Config

Cursor reads MCP config from two locations, and knowing which to use saves a lot of friction:

• Global (~/.cursor/mcp.json) applies to every project you open. Put your always-on personal tools here — Context7, GitHub, Sequential Thinking.
• Project (.cursor/mcp.json) applies only to that repo and can be committed to source control. Put team-shared, project-specific servers here — the Postgres connection for this app, the Supabase project token, the Figma file for this product.

A common pattern: global config holds your personal productivity servers, and each repo's project config holds the data sources specific to that codebase. Because the project file is committed, every teammate who clones the repo gets the same MCP setup automatically. For more Cursor workflow tips, see our Cursor power-user guide.

Troubleshooting Cursor MCP Setup

Most Cursor MCP problems fall into three buckets:

• Red dot, "failed to start". The command is not found. Make sure Node.js is installed and on your PATH. On Windows, try using cmd /c npx as the command if a bare npx fails.
• Server connects but no tools appear. You probably hit the tool ceiling — disable other servers, or the server needs an env variable it did not get. Click the server in settings and read the log.
• Tool calls hang. The underlying API token is wrong or rate-limited. Verify the token outside Cursor first (a quick curl), then paste it back into the config env block.

If you run Cursor alongside Claude Code on the same repo, point each client's git-touching servers at the same paths but avoid having both commit simultaneously — file locks cause confusing failures. For a broader view of how Cursor compares to other clients, read our Cursor vs Copilot vs Codex MCP comparison and the companion best desktop MCP servers guide.

Frequently Asked Questions

What is a Cursor MCP server?

A Cursor MCP server is a Model Context Protocol server that you connect to the Cursor AI code editor so its agent can use external tools — reading your GitHub repos, querying a Postgres database, fetching live documentation, controlling a browser, or pulling Figma designs. Cursor implements the same MCP spec as Claude Desktop and Claude Code, so the same servers work across all three.

Where do I configure MCP servers in Cursor?

Cursor reads MCP config from two places: a global file at ~/.cursor/mcp.json that applies to every project, and a project-level .cursor/mcp.json committed to a specific repo. You can also add servers through the GUI under Settings, then Features, then MCP. The project-level file is best for team-shared tools; the global file is best for your personal always-on servers.

Do Claude Desktop MCP servers work in Cursor?

Yes. Because MCP is a published JSON-RPC standard, roughly 98% of servers that work in Claude Desktop or Claude Code also work in Cursor with an identical command and args block. The only differences are the config file location and the fact that Cursor surfaces MCP tools to its Composer agent rather than a chat sidebar.

How many MCP servers can Cursor run at once?

Cursor does not enforce a hard limit, but it currently surfaces up to 40 tools to the agent at a time before truncating. In practice, keep 4 to 8 servers active per project. Too many servers dilutes the agent's tool selection and slows the first response while every server boots. Disable servers you are not using for a given task.

Are Cursor MCP servers safe to install?

Most are open source and safe, but MCP servers run as local processes with your permissions, so treat them like any dependency. Prefer servers with public source, 100+ GitHub stars, and recent commits. Scope tokens to read-only when you only need read access, and never point a filesystem or git server at your home directory. Skiln pre-filters every listing for active maintenance.

Why is my Cursor MCP server showing a red dot?

A red status dot means the server failed to start. The three most common causes: the command is not on your PATH (install Node or use the full npx path), a required environment variable like an API token is missing, or the args array has a typo. Open the MCP settings panel, click the server, and read the error log — it almost always names the exact missing piece.

Do I need MCP if Cursor already reads my codebase?

Cursor indexes your local files natively, so you do not need MCP for code context. MCP adds everything outside the repo: live database rows, current library docs, GitHub issues and PRs, browser automation, design files, and web search. It turns Cursor from a code-aware editor into an agent that can act on external systems.

Where can I browse every Cursor-compatible MCP server?

Skiln indexes 75,000+ MCP servers, skills, agents, and hooks across every major registry, all compatible with Cursor. Browse the full directory at /browse or filter to MCP servers at /mcps. Each listing shows the install command, source registry, and trust signals.

Last updated: June 18, 2026 · Skiln tracks MCP server releases daily across 13 source registries including PulseMCP, Smithery, Glama, LobeHub, and mcp.directory.