Choose an MCP server for the job it adds to your assistant. This editorial shortlist covers browser work, source research, issue tracking, deployment investigation and notes, with the maintainer and operating tradeoff made explicit.
For developers and IT teams evaluating a first connector or replacing an older MCP configuration.
“Best” means a useful starting point for a named workflow. We selected identifiable implementations with primary documentation and a clear role. The order follows workflows, not a performance score, popularity ranking or promise of production readiness.
Editorial sources reviewed . This selection is based on documentation review, not comparative benchmark testing.
A browser connector helps investigate an interface; a crawler gathers content; an issue connector supplies project context. Start with the system you need to reach. Combining several servers increases the tool surface and the permissions to manage, so add each one for a concrete task.
Official means the linked implementation is maintained by the service vendor or its own software project. Community means an independent integration. Archived means the implementation is no longer maintained. These labels identify provenance and lifecycle; they are not security certifications or endorsements by Anthropic or the MCP project.
The MCP project maintains examples such as Filesystem, Git and Memory. Its repository describes them as educational references, not production-ready solutions. They can help a developer understand the protocol or run a bounded experiment; they are not included in this operational shortlist merely because their maintainer is official.
The PostgreSQL and SQLite reference profiles currently catalogued here are archived. We keep them in the migration notes below and do not recommend them for a new production connection. Verify a maintained connector, database permissions and query limits before granting an assistant database access.
Official Maintainer: Microsoft / Playwright
Accessibility snapshots and a persistent browser session suit an investigation that moves between forms, navigation and page state.
Before connecting: Use a separate browser profile for the task. For repeatable automated tests, compare the MCP workflow with ordinary Playwright scripts and the project’s CLI guidance.
Read the profile and setup notes → · Maintainer documentation ↗
Official Maintainer: Firecrawl
Search, URL discovery, scraping and bounded crawling support research that starts with a question and ends with usable source material.
Before connecting: Choose the appropriate hosted or local configuration. Bound page counts and review credit usage; a website crawl and a single page fetch have different costs.
Read the profile and setup notes → · Maintainer documentation ↗
Official Maintainer: Linear
The provider’s hosted service brings issues, projects and comments into a planning or implementation discussion.
Before connecting: Use the read-only endpoint when the task is research. Enable writes only for a workflow that actually creates or updates Linear records.
Read the profile and setup notes → · Maintainer documentation ↗
Official Maintainer: Sentry
Issue and trace context helps connect a code change to an observed production failure.
Before connecting: Confirm access to the intended organization and project. Hosted and self-hosted Sentry configurations do not expose identical features.
Read the profile and setup notes → · Maintainer documentation ↗
Official Maintainer: Vercel
A supported client can combine deployment logs, project context and Vercel documentation during an investigation.
Before connecting: Complete OAuth with the intended account and check supported clients. The hosted endpoint replaces old, unverified local-package instructions.
Read the profile and setup notes → · Maintainer documentation ↗
Official Maintainer: Cloudflare
The domain-specific endpoints let a team select documentation, browser or container capabilities for a defined task.
Before connecting: Check the current endpoint table and deprecation notices. Broad Cloudflare API access is offered through a separate server and should be evaluated separately.
Read the profile and setup notes → · Maintainer documentation ↗
Community Maintainer: MCP Atlassian contributors
The community connector links issue searches and updates with the documentation surrounding a change.
Before connecting: Choose the correct authentication method for Cloud or Server/Data Center. This implementation is not an Atlassian-maintained product.
Read the profile and setup notes → · Maintainer documentation ↗
Community Maintainer: Markus Pfundstein and contributors
Search and heading-aware edits make the connector useful when the source material already lives in Obsidian notes.
Before connecting: The Local REST API plugin must be enabled and reachable. Configure its key, host and port, and back up the vault before testing edits.
Read the profile and setup notes → · Maintainer documentation ↗
These historical profiles are excluded from the shortlist. Do not select an archived reference implementation for a new production deployment. Check the current provider or project documentation when replacing one.
Each connector above links to its maintainer’s own documentation. Continue with the MCP server hub or the MCP explainer.
