🖱️Free

Best MCP Servers for Cursor: A Transparent, Dated Shortlist

Published: 2026-08-12Updated: 2026-08-12~9 min

MCP Radar Editorial · Facts verified: 2026-08-12 · Refresh due: 2026-09-12

Direct answer

Choose Cursor MCP servers by the job they improve, not by list popularity. Prefer one narrow docs, browser, repository, database, or design integration that beats Cursor's built-in or terminal path. The ranking below is a screened shortlist; this environment has no Cursor IDE installation, so it does not claim current IDE smoke tests.

Snapshot

2,636 records

Collected 2026-08-05

Cursor rows

2,400

2 verified · 2,398 derived

IDE test

Not run

Cursor CLI reports no IDE installation in this environment

Official config

.cursor/mcp.json

Global: ~/.cursor/mcp.json

JobWhen MCP adds valueWhen built-in/CLI may winFirst smoke test
Docs/contextA maintained current knowledge source with citationsRepository docs are already local and searchableRetrieve one version-specific answer
Browser/testingStructured browser control and repeatable observationsA project test script already covers the flowOpen a local page and inspect one element
RepositoryRemote issue/PR/project data with per-user authgit/gh commands already provide audited JSONRead one issue; do not write
DatabaseSchema/query tools with a read-only identityA local migration or query CLI is sufficientList schema and run a bounded query
DesignLive design-system or file context is requiredExported assets/specs are already in the repoRead one named component without mutation
Run the redundancy test before installation: prefer built-in or CLI capabilities when they are clearer and lower-maintenance.

Use a job-first starter stack

Do not install a generic bundle of 'must-have' servers. Pick the one external system that repeatedly blocks your Cursor workflow. Docs/context is a common first candidate; browser/testing, repository, database, and design follow only when the built-in agent or a trusted CLI cannot satisfy the same task clearly.

How the live Cursor shortlist is computed

The data table includes active developer-workflow entries that declare Cursor compatibility and clear the displayed star floor. Duplicate repositories are collapsed, then TrustScore and adoption order the eligible set. The formula is repeatable and the pool size is printed below the table. A rank is a research starting point, not a safety or workflow guarantee.

#ServerTrustScoreStarsClients
1io.github.D4Vinci/ScraplingScrapling MCP Server9373,830cursor · derived
2io.github.microsoft/playwright-mcpPlaywright Tools for MCP8736,128cursor · derived
3io.github.homeassistant-ai/ha-mcpComprehensive Model Context Protocol server for managing Home Assistant through 874,381cursor · derived
4io.github.bytebase/dbhubDBHub873,365cursor · derived
5io.github.ChromeDevTools/chrome-devtools-mcpChrome DevTools MCP8648,873cursor · derived
6io.github.usekaneo/kaneoOfficial MCP server for Kaneo: manage tasks, projects, and labels from Claude an868,047cursor · derived
7io.github.Ataraxy-Labs/semEntity-level code intelligence: semantic diff, impact analysis, blame, and conte863,302cursor · derived
8io.github.atilaahmettaner/tradingview-mcpReal-time market data, screeners, technical analysis & backtesting for stocks, c853,937cursor · derived
9io.github.zereight/gitlab-mcpGitLab MCP server for projects, merge requests, issues, pipelines, wiki, release851,886cursor · derived
10io.github.github/github-mcp-serverGitHub8432,250cursor · derived

10 of 2077 actively-maintained servers in these categories cleared the 500-star adoption floor, ordered by TrustScore. Regenerated daily from public GitHub, npm and registry signals — see our editorial policy for the full weighting. ✓ means we installed it in a sandbox and confirmed it starts.

Separate derived compatibility from tested behavior

In the frozen snapshot, two catalog samples have stored sandbox startup/tool-list evidence and 2,398 Cursor rows are derived from transport metadata. This environment's Cursor CLI reports that no Cursor IDE is installed, so MCP Radar did not exercise discovery or a real tool invocation in the current stable IDE for this batch. Treat every selected row as requiring a local smoke test.

Configure and verify in Cursor

Put project-specific definitions in `.cursor/mcp.json` or personal global definitions in `~/.cursor/mcp.json`. Cursor supports stdio, SSE, and Streamable HTTP and documents MCP Logs in the Output panel. Enable one server, inspect its tools, run one non-destructive request, and verify the result and permission scope before enabling automatic execution.

Run the redundancy and exclusion tests

Compare the same task through Cursor's built-in capability or terminal command. Exclude the server if it merely wraps a familiar CLI without better schemas or controls, requests broad credentials, duplicates another server, has unclear ownership, or fails the current IDE smoke test. Remove unused servers to reduce tool clutter and attack surface.

Methodology and limitations

  • Dataset frozen at 2026-08-05 and official Cursor docs retrieved 2026-08-12.
  • Compatibility is explicitly labeled verified or derived in the underlying data; derived is never described as a successful Cursor invocation.
  • No macOS/Windows Cursor IDE test matrix was possible in this environment, so the page is a transparent shortlist pending those checks.
  • Maintenance and adoption are public screening signals, not proof of security or task quality.

Frequently asked questions

Were all ranked servers tested in Cursor?

No. Most compatibility rows are transport-derived, and this environment has no Cursor IDE installation. Run a current IDE smoke test before relying on any pick.

Where is Cursor MCP configuration stored?

Use `.cursor/mcp.json` for project configuration and `~/.cursor/mcp.json` for global personal configuration.

Where can I debug a Cursor MCP server?

Open the Output panel, choose MCP Logs, and inspect initialization, tool calls, authentication, and server errors.

Sources

  1. Cursor — Model Context Protocol · retrieved 2026-08-12
  2. Model Context Protocol — security best practices · retrieved 2026-08-12
  3. MCP Radar dataset snapshot (2026-08-05) · retrieved 2026-08-12

Continue reading