
This list is part of our best-of MCP lists, within The MCP Guide. Entries are checked against each vendor's own pages; inclusion is editorial and not paid.
The best MCP servers for Cursor in 2026 are official ones that Cursor users reach for every day: Context7 for current library docs, Stripe and Supabase or Neon for app data, and Linear, Notion and Figma for the work around the code. Sentry, Vercel and Datadog close the loop on errors, deploys and monitoring.
Cursor is an AI code editor from Anysphere, which Cursor says was acquired by SpaceX in August 2026. Its MCP docs list support for tools, prompts, resources, roots, elicitation and the MCP Apps extension. You add servers in .cursor/mcp.json for one project or ~/.cursor/mcp.json for all of them.
Every server below has its own vendor setup docs that name Cursor or a Cursor install button. We checked each one on 28 October 2026. eSEOspace did not install or test these servers.
Key Takeaways
- Cursor asks you to approve each MCP tool call by default, and you can expand the arguments before you click.
- Most servers here are remote and use OAuth, so you sign in through the browser instead of pasting keys into
mcp.json. - Supabase, Neon and Linear offer read-only modes, which are the safest way to start.
- Stripe will stop accepting full-access and untagged restricted keys over MCP from December 2026, so key-based setups must move to agent API keys or OAuth.
- Official servers appear in the Cursor Marketplace, while community servers live on cursor.directory, which needs more care.
How we chose
We included a server only if it passed these tests:
- Official. Published by the company that owns the product.
- Works with Cursor. The vendor's docs show Cursor setup, a Cursor install link, or list Cursor as a supported client.
- Clear access model. The docs explain sign-in and, where relevant, how to limit scope.
- Clear cost. The docs or pricing page state the price or plan rules.
We skipped servers already covered in depth in our MCP servers for developers list where a Cursor-specific angle added nothing, such as GitHub and Playwright. If you are still choosing an editor, see our MCP clients list first.
Comparison table
| Name | Best for | Pricing | Notable |
|---|---|---|---|
| Context7 | Current library docs in prompts | Free 1,000 calls/mo; Pro $10/seat/mo | Two simple tools |
| Stripe MCP | Payments code and test data | No separate MCP price listed | Human confirmation for refunds |
| Supabase MCP | Postgres apps on Supabase | No separate MCP price listed | read_only and project_ref |
| Neon MCP Server | Serverless Postgres branches | No separate MCP price listed | ?readonly=true |
| Linear MCP | Pulling issues into the editor | No plan requirement stated for Cursor | Separate read-only endpoint |
| Notion MCP | Specs and docs from Notion | Some features need Business or Enterprise | Hosted by Notion |
| Figma MCP server | Design to code | Full or Dev seat for daily use | Approved-client catalog |
| Sentry MCP | Fixing production errors | No separate MCP price listed | Load only the skills you need |
| Vercel MCP | Deploys and logs | All Vercel plans | Only approved clients connect |
| Datadog MCP Server | Logs, metrics and traces | Fair-use limits; no MCP price listed | Toolsets and omit_tools |
1. Context7: up-to-date docs inside Cursor
What it is. Context7 from Upstash "pulls up-to-date, version-specific documentation and code examples straight from the source." It has two MCP tools: resolve-library-id and query-docs.
The remote server is https://mcp.context7.com/mcp. You can click "Add to Cursor" or run npx ctx7 setup --cursor. More detail is in our Context7 MCP server profile.
Best for: Any developer tired of the AI suggesting old APIs.
Pricing: The Context7 plans page lists Free at $0 with 1,000 API calls per month, then 20 bonus calls per day. Pro is $10 per seat per month with 2,000 calls per seat and private repos. Enterprise is custom.
Pros
- Cuts errors from outdated library knowledge.
- Very small tool surface.
- MIT-licensed code.
Cons
- The free tier covers public repositories only.
- Busy teams may hit the free call limit.
Checked against: Context7 on GitHub on 28 October 2026.
2. Stripe MCP: payments with built-in brakes
What it is. The Stripe MCP server at https://mcp.stripe.com has an "Install in Cursor" button and a manual ~/.cursor/mcp.json snippet. It exposes stripe_api_read and stripe_api_write plus docs search and an implementation planner.
Stripe "requires human confirmation before it takes certain stripe_api_write actions, such as refunds and outbound payments." Our Cursor to Stripe guide walks through setup.
Best for: Developers building checkout, billing or subscription code.
Pricing: The MCP docs list no separate charge. Admins can turn MCP access on or off for the team in the Dashboard, separately for live mode and sandboxes.
Pros
- OAuth consent lets you pick sandboxes and live accounts separately.
- Human confirmation on risky writes.
- Sessions can be revoked from the Dashboard.
Cons
- Key-based setups must migrate by 30 November 2026; Stripe says it will then stop accepting full-access keys and restricted keys without the Agent tag.
- Write access to a live account is powerful, so start in a sandbox.
Checked against: Stripe MCP docs on 28 October 2026.
3. Supabase MCP: scoped database access
What it is. Supabase's MCP server runs at https://mcp.supabase.com/mcp and signs in with OAuth. The docs show the exact .cursor/mcp.json entry.
You can add read_only=true to "Execute all queries as a read-only Postgres user" and project_ref to scope it to one project. See our Cursor to Supabase guide.
Best for: Teams building on Supabase who want the AI to read schemas and data.
Pricing: The docs list no separate MCP price. Usage counts against your normal Supabase project.
Pros
- Read-only and project scoping in the URL.
- Feature groups let you hide tools you do not need.
- No personal access token needed.
Cons
- Supabase warns that connecting an LLM to projects "carries security risks."
- Not meant for end users or customers, since it runs with developer permissions.
Checked against: Supabase MCP docs on 28 October 2026.
4. Neon MCP Server: Postgres branches on demand
What it is. Neon's MCP server is at https://mcp.neon.tech/mcp and supports OAuth or API keys. Append ?readonly=true to block writes such as migrations. npx neon@latest plugins installs Neon's plugin for agents that support plugins, including Cursor.
The old /sse endpoint returns 410 Gone from 1 October 2026, so update older configs.
Best for: Developers who use database branches to test schema changes.
Pricing: The MCP docs list no separate price. Usage follows your Neon plan.
Pros
- Read-only switch in the URL or OAuth scope.
- Tool categories can be limited with
?category=. - Branching suits safe experiments.
Cons
- Neon says "We recommend MCP for development and testing only, not production environments."
- Old SSE configs now fail.
Checked against: Neon MCP Server docs on 28 October 2026.
5. Linear MCP: issues without leaving the editor
What it is. Linear's MCP server at https://mcp.linear.app/mcp is "centrally hosted and managed." The docs offer a Cursor install link and OAuth 2.1 sign-in.
For safety, https://mcp.linear.app/mcp/readonly "only ever exposes read tools."
Best for: Developers who want the AI to read the ticket before it writes the code.
Pricing: The docs list plan rules only for Claude, not for Cursor. Linear's own plans apply.
Pros
- Separate read-only endpoint.
- OAuth or API key options.
- Finds, creates and updates issues and projects.
Cons
- The default endpoint can write.
- The deprecated SSE endpoint may linger in old configs.
Checked against: Linear MCP docs on 28 October 2026.
6. Notion MCP: specs and decisions as context
What it is. Notion MCP runs at https://mcp.notion.com/mcp. The setup guide shows the .cursor/mcp.json entry, then you enable Notion under Customize and complete OAuth.
Our Cursor to Notion guide has the steps.
Best for: Teams that keep product specs and architecture notes in Notion.
Pricing: notion-search works on every plan. Connected-source search, unlimited SQL queries and MCP tokens need Business or Enterprise, and some features also need Notion AI.
Pros
- Hosted by Notion with OAuth.
- Works on every Notion plan for core search.
- Owners can restrict clients on Enterprise.
Cons
- Guests cannot connect.
- Several useful features sit behind higher plans.
Checked against: Notion MCP setup guide on 28 October 2026.
7. Figma MCP server: designs into code
What it is. Figma's remote MCP server is at https://mcp.figma.com/mcp. In Cursor you can add it as a plugin with /add-plugin figma, then connect under Tools and MCP.
"Only clients listed in the Figma MCP catalog, such as VS Code, Cursor, and Claude Code, can connect." Our Cursor to Figma guide covers setup.
Best for: Front-end developers turning Figma frames into components.
Pricing: Figma's rate limits page gives View and Collab seats up to 20 calls per month. Full and Dev seats get 200 per day on Professional and up to 600 per day on Enterprise. Some write actions use Figma AI credits.
Pros
- Official client allowlist.
- Can also send a running UI back into Figma.
- Write tools are exempt from read limits.
Cons
- View seats get very few calls.
- AI-credit actions add a second cost to track.
Checked against: Figma remote server docs on 28 October 2026.
8. Sentry MCP: errors straight into the fix
What it is. Sentry MCP is hosted at https://mcp.sentry.dev/mcp and is "optimized for coding assistants like Cursor, Claude Code." Remote sessions use OAuth.
Tools come in skills such as inspect and triage, and ?skills= limits what loads. AI search tools need an LLM provider key.
Best for: Developers who want the AI to read the real stack trace.
Pricing: No separate MCP price is listed on the repo or docs. Sentry's own plans apply.
Pros
- Pulls real error and trace data.
- Skills keep the tool list short.
- OAuth for remote use.
Cons
- The README gives no Cursor-specific install steps.
- AI-powered search needs your own LLM provider.
Checked against: Sentry MCP on GitHub on 28 October 2026.
9. Vercel MCP: deploys and logs
What it is. Vercel MCP at https://mcp.vercel.com is a remote server with OAuth. Cursor is on its supported clients list, with an "Add to Cursor" link.
"Vercel MCP only supports AI clients that have been reviewed and approved by Vercel." It searches docs, manages projects and deployments, reads logs and queries Web Analytics.
Best for: Teams that deploy Next.js or other front ends on Vercel.
Pricing: "Vercel MCP is available on all plans," per the docs.
Pros
- Approved-client list reduces risk.
- Explicit consent for each client connection.
- Can read deployment logs during debugging.
Cons
- Grants the same access as your Vercel user account.
- Now able to deploy and buy, so keep approvals on.
Checked against: Vercel MCP docs on 28 October 2026.
10. Datadog MCP Server: monitoring data on demand
What it is. The Datadog MCP Server "acts as a bridge between your observability data in Datadog and any AI agents." Cursor is a listed client.
It "forwards the authenticated user's own credentials to Datadog APIs," so users get only the access they already have. You can trim tools with toolsets and omit_tools.
Best for: Teams already on Datadog who debug from the editor.
Pricing: No MCP price is listed. Fair-use limits are 50 requests per 10 seconds and 100,000 tool calls per month.
Pros
- Respects existing Datadog permissions.
- Toolsets keep context small.
- HIPAA-eligible.
Cons
- Datadog says it "is under significant development."
- Not available on GovCloud sites.
Checked against: Datadog MCP Server docs on 28 October 2026.
Setting up safely in Cursor
Start with read-only modes where they exist, and keep Cursor's default tool approval on. Put shared servers in the project's .cursor/mcp.json so the whole team uses the same reviewed URLs.
Be careful with community servers from cursor.directory. Cursor's docs point there for community plugins, but those are not vetted like vendor servers. Our Anysphere spotlight covers Cursor's admin controls.
Next step
Want a custom MCP server your developers can use in Cursor? See our MCP development services, or browse more lists in the MCP Guide's best-of section.
Frequently asked questions
How do I add an MCP server to Cursor?
Add an entry to .cursor/mcp.json in your project or ~/.cursor/mcp.json in your home folder. Many vendors also offer a one-click "Add to Cursor" link. Remote servers then ask you to sign in with OAuth.
Does Cursor support remote MCP servers?
Yes. Cursor's docs list stdio, SSE and Streamable HTTP transports, with OAuth for remote servers. Most servers on this list are remote.
Is cursor.directory the same as the Cursor Marketplace?
No. Cursor's docs say official plugins are in the Cursor Marketplace, and they point to cursor.directory for community plugins and MCP servers. Treat community entries with extra caution.
Which of these servers are read-only?
Supabase, Neon and Linear offer read-only modes. Datadog uses your existing permissions, and Stripe adds human confirmation for refunds and payouts. Others can write, so keep approvals on.
Do I need a paid Cursor plan for MCP?
The Cursor MCP docs we read do not mention a plan requirement for MCP. Each server's own plan rules apply, such as Figma seats or Notion's Business features.











