Developer Tools MCP Servers

49 developer tools MCP servers are cataloged, 6 with verified current-spec support.

MCP servers that front developer platforms and workflows: source control, code review, CI, project and deployment management.

• Adeu - Earlier Revision

  DOCX redlining engine exposed as an MCP server, in Python and Node.js implementations: translates .docx files to a Markdown representation for LLM editing and applies edits back as native Word Track Changes. npm's latest @adeu/mcp-server is 2.4.0 (2026-08-13); the registry record trails at 1.7.1 (2026-05-16). No surface names a supported MCP revision. Resolved from the published package: @adeu/mcp-server 2.4.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Agent Swarm - Spec Support Unverified

  First-party Desplega Labs server for its own agent-swarm product, distributed as npm:@desplega.ai/agent-swarm and self-hosted: the registry declares the remote as https://{swarm_host}/mcp, where the operator supplies the host of their own instance, so there is no vendor endpoint to probe. Auth is a bearer API key plus an X-Agent-ID header naming a registered agent. No documentation names a supported MCP specification revision. Two protocol versions appear in source, both as defaults in code rather than support statements: an outbound MCP client wrapper defaults to 2025-03-26, and a dashboard-generated debug snippet hardcodes 2025-06-18. The declared streamable-http transport is a transport, not a revision.

• agent-device - Earlier Revision

  Callstack's CLI and MCP server for driving iOS, Android, TV, desktop, and web apps from coding agents, run locally via agent-device mcp over stdio. Its hand-rolled MCP implementation hard-codes protocol revision 2025-11-25 in the initialize handshake; 2026-07-28 support is not implemented.

• aiterm-mcp - Earlier Revision

  Distributed as npm:aiterm-mcp. Resolved from the published package: aiterm-mcp 0.27.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Apify MCP Server - Current Spec Verified

  Apify's first-party MCP server, hosted at mcp.apify.com over streamable HTTP, which exposes the Apify Store of scrapers and automations as MCP tools and can load an individual Actor's own MCP tools. Auth is OAuth or an Apify API token as a bearer header; an unauthenticated request to the endpoint returns 401. Endpoint probe confirmed support for 2026-07-28 via server/discover.

• Argent - Earlier Revision

  Distributed as npm:@swmansion/argent. Resolved from the published package: @swmansion/argent 0.21.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Ash AI MCP Server - Current Spec Verified

  AshAi.Mcp.Server is a library module the ash_ai package (hex:ash_ai) ships for the Elixir Ash Framework; operators mount it themselves via forward "/mcp", AshAi.Mcp.Router, tools: [...], otp_app: :my_app in their own Phoenix router, or as a plain Plug in any Plug-based application, so there is no single hosted Ash AI MCP Server to point at, only per-deployment mounts of the same library code. It runs over the MCP Streamable HTTP transport only; its SSE support is an in-band response-encoding option within Streamable HTTP requests, not the deprecated standalone HTTP+SSE transport, which the source explicitly disclaims. Authentication defaults to none: the README's authentication section documents two opt-in options, "OAuth 2.1 - the right choice for 'remote' MCP clients that self-register and run the standard OAuth flow" via ash_authentication_oauth2_server, and "API keys - the quickest way to value when your clients are configured by hand with a static credential" via AshAuthentication.Strategy.ApiKey.Plug, and the router forwards without either configured by default. Both the shipped source (lib/ash_ai/mcp/server.ex at v1.0.3) and the live hexdocs page for the same module state, under "Protocol versions," that "the server supports multiple protocol revisions in tandem on the same endpoint": 2026-07-28, 2025-06-18, and 2025-03-26, grounding spec_status as current. The README's separate "Production MCP Server" section still states "The protocol version we implement is 2025-03-26," language the shipped v1.0.3 source and hexdocs supersede.

• Bitbucket MCP (MatanYemini) - Earlier Revision

  Community MCP server for the Bitbucket Cloud and Server APIs by an individual developer; not published by Atlassian. npm's latest is 5.0.6 (2025-12-22), one patch ahead of the registry record's 5.0.5. No surface names a supported MCP revision. Resolved from the published package: bitbucket-mcp 5.0.6 depends on @modelcontextprotocol/sdk@1.1.1, whose artifact implements 2024-11-05. This records what the artifact implements, not what a deployment negotiates.

• browser-devtools-mcp - Earlier Revision

  Distributed as npm:browser-devtools-mcp. Resolved from the published package: browser-devtools-mcp 0.9.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Chrome DevTools MCP - Spec Support Unverified

  Google's Chrome DevTools MCP server: lets a coding agent control and inspect a live Chrome browser with DevTools-grade debugging, performance tracing, and Puppeteer-based automation, run locally over stdio via npx chrome-devtools-mcp. Hand check 2026-08-25: no MCP revision statement in README, CHANGELOG or docs; @modelcontextprotocol/sdk 1.30.0 is a devDependency of a bundled build, so the SDK chain cannot ground a revision. v1.8.0 released 2026-08-25.

• claude-flow - Earlier Revision

  Community agent-orchestration harness by the developer rUv, exposing MCP tools for multi-agent workflows. Renamed to "ruflo" (repo ruvnet/ruflo, npm ruflo); the registry record still uses the claude-flow name at a September 2025 alpha. A critical unauthenticated RCE (CVE-2026-59726) was patched in ruflo 3.16.3. Checked 2026-08-25: the v3 MCP package README in the ruflo repository states "MCP 2025-11-25 Compliant - Standalone Model Context Protocol server implementation with full Resources, Prompts, and Tasks support". Both npm packages claude-flow and ruflo ship 3.38.20 from the same commit; releases 3.38.18 and 3.38.19 (2026-08-22) name MCP HTTP transport fixes.

• Codebase Memory MCP - Spec Support Unverified

  Community MCP server (by developer Martin Vogel) that indexes a codebase into a persistent knowledge graph for AI agents, distributed as a static binary via npm or PyPI and run locally over stdio. Hand check 2026-08-25: no MCP revision statement in README or docs; ships as a native binary whose npm package declares no runtime dependencies, so no SDK chain exists.

• Concord MCP - Spec Support Unverified

  Local-first coordination server distributed as npm:@concord-ai/concord-mcp, giving coding agents shared work-state across harnesses (Claude Code, Codex, Cursor, Gemini CLI, Grok Build) through five tools backed by a local SQLite store. It runs over stdio only, installed globally via npm and registered into each client's own MCP config by a `concord setup` command; no auth token or OAuth flow gates the MCP interface itself. The vendor's own site, getconcord.ai, links directly to this repository and instructs installing this exact package, establishing Concord AI as the vendor whose product the server fronts. No documentation names a supported MCP specification revision, so spec_status is unknown.

• Context7 - Current Spec Verified

  Upstash's Context7 documentation server: pulls current, version-specific library docs into prompts. Hosted at mcp.context7.com/mcp with bearer API keys (anonymous use is rate-limited); also runs locally via npm. The 4.0.0 release of 2026-08-07 migrated to the 2026-07-28 revision, and an endpoint probe the same day confirmed it. Endpoint probe confirmed support for 2026-07-28 via server/discover.

• ctxlint - Spec Support Unverified

  MCP server and CLI that lints AI agent context files (CLAUDE.md, AGENTS.md, and similar) against the actual codebase they describe. Registry and npm agree on 0.22.0 (2026-08-08). No project surface names a supported MCP revision.

• Desktop Commander - Earlier Revision

  MCP server giving an assistant terminal command execution, process management, and filesystem operations on the local machine, run over stdio via npx @wonderwhy-er/desktop-commander. Telemetry is on by default with a documented opt-out. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @wonderwhy-er/desktop-commander 0.2.47 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Doc Bridge - Spec Support Unverified

  Resolves documentation ownership, edit roots and human handoffs before an agent edits code, distributed as npm:@agentskit/doc-bridge and launched via npx ak-docs mcp over stdio. First-party rests on four agreeing surfaces: the AgentsKit-io GitHub organization, the @agentskit npm scope, the doc-bridge.agentskit.io product page (which links only to this repository) and the parent agentskit.io site, which lists Doc Bridge among its own products. The dedicated docs/mcp.md page enumerates eight tools, while the README separately states a packaged bundle advertises fourteen; the extra six are not itemized anywhere fetched. The official MCP Registry record is pinned at version 1.2.6 from 2026-08-03, roughly forty releases behind npm's 1.7.45 as of 2026-08-29, and GitHub's own release feed stopped at v1.4.3. No file fetched, including the README, CHANGELOG and docs pages, names an MCP protocol revision, so spec support is recorded as unknown.

• fiori-mcp-server - Spec Support Unverified

  Distributed as npm:@sap-ux/fiori-mcp-server. Hand check 2026-08-25: no MCP revision statement in the package README; src/server.ts negotiates the protocol version with FALLBACK_PROTOCOL_VERSION '2024-11-05', and @modelcontextprotocol/sdk 1.29.0 appears as a devDependency, so the SDK chain cannot ground a revision. Frequent releases (1.11.14 on 2026-08-25).

• Framelink MCP for Figma - Earlier Revision

  Community MCP server (Framelink, by Graham Lipsman) that fetches Figma file data through Figma's REST API and simplifies it for coding agents to implement designs; requires a Figma personal access token and runs locally over stdio. Not published by Figma. No vendor documentation surface names a supported MCP revision. Resolved from the published package: figma-developer-mcp 0.13.2 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• GitHub MCP Server - Current Spec Verified

  GitHub's first-party MCP server: a GitHub-hosted remote endpoint at api.githubcopilot.com/mcp/ (OAuth, or a personal access token) plus a local Docker distribution over stdio. Toolsets cover repositories, issues, pull requests, and code analysis. Supports the stateless 2026-07-28 revision, shipped ahead of the revision's release on the official Go SDK.

• GitLab MCP Server - Earlier Revision

  GitLab's official MCP server, built into the GitLab application at /api/v4/mcp. GitLab docs state support for the 2025-03-26 and 2025-06-18 MCP protocol specifications was added in GitLab 18.7. Beta on all tiers of GitLab.com, Self-Managed, and Dedicated. No GitLab surface names 2026-07-28 support; a probe on 2026-08-14 answered with an OAuth challenge, so revision behavior is not observable without credentials.

• gitlab-mcp - Earlier Revision

  Community MCP server (by independent developer zereight) fronting the GitLab API: projects, merge requests, issues, pipelines, wiki, releases. Requires a GitLab personal access token by default, with OAuth modes for self-hosted remote deployments. Not published by GitLab, which operates its own official MCP server. No surface names a supported MCP revision. Resolved from the published package: @zereight/mcp-gitlab 2.1.49 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• gk-cli - Spec Support Unverified

  Distributed as npm:@gitkraken/gk. Authority resolved 2026-08-25: the repository is owned by the gitkraken GitHub organization and the npm package is maintained by axosoft (dev.subs@gitkraken.com); the MCP server is the CLI's own gk mcp subcommand wrapping git, GitHub, Jira actions and GitKraken APIs. No MCP revision statement in the README or the GitKraken help page for the MCP server (checked 2026-08-25).

• growthbook-mcp - Earlier Revision

  Distributed as npm:@growthbook/mcp. Resolved from the published package: @growthbook/mcp 2.1.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Ignite UI Theming MCP Server - Spec Support Unverified

  Generates Sass palettes, typography, elevations and component themes for Infragistics' Ignite UI design system, distributed as the single npm package igniteui-theming, which bundles both the Sass library and the MCP server binary. The server runs over stdio only, launched with npx, and documents no authentication scheme. No README, changelog or registry manifest names a supported MCP specification revision; the resolved @modelcontextprotocol/sdk artifact implements up to protocol version 2025-11-25, but that is a fact about the underlying SDK build rather than a vendor statement about this server's own revision support, so spec_status stays unknown. The vendor's root README and its packages/mcp sub-package README disagree on tool count, eight versus twelve, a documentation drift rather than a protocol ambiguity.

• jshookmcp - Earlier Revision

  Distributed as npm:@jshookmcp/jshook. Resolved from the published package: @jshookmcp/jshook 0.3.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• loki-mode - Spec Support Unverified

  Distributed as npm:loki-mode. Hand check 2026-08-25: no MCP revision statement in README, CHANGELOG or mcp/server.py; the Python adapter requires mcp>=1.0.0,<2.0.0, an ambiguous range spanning SDK eras. MCP is one interface of a multi-agent SDLC framework (36 tools via loki mcp).

• Mailtrap MCP Server - Earlier Revision

  Mailtrap's official MCP server for its email delivery and testing platform, run locally from the mcp-mailtrap npm package with a MAILTRAP_API_TOKEN. npm's latest is 0.7.0 (2026-08-04); the registry record trails at 0.6.0. No vendor surface names a supported MCP revision. Resolved from the published package: mcp-mailtrap 0.8.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• mcp-server - Earlier Revision

  Distributed as npm:@cap-js/mcp-server. Resolved from the published package: @cap-js/mcp-server 0.0.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• mcp-server - Earlier Revision

  Distributed as npm:@ui5/mcp-server. Resolved from the published package: @ui5/mcp-server 0.2.18 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• mcpcap - Spec Support Unverified

  MCP server for analyzing PCAP network capture files, distributed on PyPI and run locally. Registry record and PyPI agree on 0.9.6. Hand check 2026-08-25: no MCP revision statement in README, docs or release notes; PyPI requires fastmcp>=2.12.2,<2.15.0, a third-party framework the SDK chain does not cover. Last release v0.9.6 on 2026-03-17.

• mdk-mcp-server - Earlier Revision

  Distributed as npm:@sap/mdk-mcp-server. Resolved from the published package: @sap/mdk-mcp-server 0.4.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• next-devtools-mcp - Earlier Revision

  Distributed as npm:next-devtools-mcp. Resolved from the published package: next-devtools-mcp 0.4.0 depends on @modelcontextprotocol/sdk@1.25.2, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Octocode MCP - AI Context Platform - Earlier Revision

  Distributed as npm:octocode-mcp. Resolved from the published package: octocode-mcp 18.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• postman-mcp-server - Earlier Revision

  Listed with a remote endpoint. Resolved from the published package: @postman/postman-mcp-server 2.12.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• PraisonAI MCP Server - Spec Support Unverified

  Heavy-host MCP server package (pypi:praisonai-mcp), one of three MCP packages PraisonAI documents alongside a client (praisonaiagents[mcp]) and a light server (praisonai-code). Serves 86 tools, 7 resources, and 7 prompts via `praisonai-mcp serve` (or `praisonai mcp serve`) over stdio (default) or --transport http-stream at a default /mcp endpoint, gated by a single wildcard-scoped --api-key or a --keys-file of per-key scopes. The one Official MCP Registry record found (io.github.MervinPraison/praisonai, v2.3.42, stdio only) describes the older monolithic praisonai package, not this package, and is stale against current releases, so no registry_name is recorded here. No vendor page fetched this session names an MCP spec revision for this server role; the client transports page's "Protocol Revision: 2025-11-25" statement covers only the separate praisonaiagents MCP client class and does not speak for this package. Six CVE records have been filed against PraisonAI's MCP-adjacent code since 2026-08-25, spanning three surfaces: the pip praisonai HTTP-stream transport (three records), the pip praisonai UI host app's stdio-spawn client path (one record), and the separate npm praisonai TypeScript MCPServer (two records); all six are fixed in current releases.

• python-mcp - Spec Support Unverified

  Distributed as pypi:files-com-mcp. Spec revision support not yet verified.

• ROS 2 MCP Server - Spec Support Unverified

  Python MCP server bridging MCP clients to ROS 2 nodes, topics, services and actions over stdio, distributed as the Docker image mcp/ros2 in Docker's curated MCP catalog. No documentation names a supported MCP specification revision: the README links the 2025-06-18 prompts section to explain what prompts are, which is a pointer to the spec rather than a support claim, and the pyproject dependency mcp[cli]>=1.23.0 records an SDK floor, not a revision. The registry record is stale: the repository was renamed from mcp_server_ros_2 to ros2_mcp and its own server.json now declares io.github.wise-vision/ros2_mcp, while the published registry entry still carries the old name and version 1.0.0 from 2025-11-26.

• rsdoctor - Spec Support Unverified

  Distributed as npm:@rsdoctor/mcp-server. Hand check 2026-08-25: no MCP revision statement on rsdoctor.rs, in the repository or the npm README; @modelcontextprotocol/sdk 1.29.0 is a devDependency only. Identity note: the npm package's source directory (packages/ai) is not present on the repository's main branch; the primary npm maintainer is yifancong, matching the registry namespace, while the repository lives in the web-infra-dev organization.

• ruv-swarm - Spec Support Unverified

  Distributed as npm:ruv-swarm. Hand check 2026-08-25: no MCP revision statement in the monorepo or ruv-swarm READMEs or the MCP docs set; npm ruv-swarm 1.0.20 declares no MCP SDK dependency and was last published 2025-09-10, while the repository (ruvnet/ruv-FANN) last pushed 2026-08-09.

• Safari MCP Server - Spec Support Unverified

  Apple ships an MCP server inside Safari, delivered through the safaridriver binary, exposing 17 tools for web development and debugging. No Apple page names any MCP specification revision, transport, license or source repository, so spec support is recorded as unverified rather than inferred from the announcement date.

• Sentry MCP Server - Earlier Revision

  Sentry's first-party MCP server for error monitoring and issue data, hosted at mcp.sentry.dev with OAuth, plus a work-in-progress local stdio transport using a Sentry user auth token. A 2026-08-07 probe confirmed the OAuth requirement first-hand; no vendor documentation surface names a supported MCP revision. Resolved from the published package: @sentry/mcp-server 0.37.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Snyk MCP Server - Earlier Revision

  Snyk's MCP server ships inside the Snyk CLI and runs via the snyk mcp command, exposing Snyk security scans (open source, code, IaC, container, SBOM, secrets) to agentic tools. Checked 2026-08-25: the studio-mcp repository ships MCP specification conformance tests stating they "verify compliance with the Model Context Protocol specification" for versions 2025-11-25 and 2025-06-18 (internal/mcp/mcp_spec_conformance_test.go). The server is a Go binary inside the Snyk CLI, invoked as snyk mcp and built on mark3labs/mcp-go v0.31.0; the npm snyk package itself declares no MCP SDK dependency.

• socraticode - Earlier Revision

  Distributed as npm:socraticode. Resolved from the published package: socraticode 1.12.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Storybook MCP Addon - Spec Support Unverified

  Storybook addon that serves an MCP endpoint from the Storybook dev server (default http://localhost:6006/mcp) so agents can read component docs, generate stories, and run story tests. AI features are in preview and React-only per Storybook's docs. Hand check 2026-08-25: no MCP revision statement in the monorepo README, addon README or changelogs. The addon migrated from @modelcontextprotocol/sdk to the third-party tmcp library (addon 0.7.0 depends on tmcp ^1.19.4), which the SDK chain does not cover.

• Svelte MCP - Current Spec Verified

  Endpoint probe confirmed support for 2026-07-28 via server/discover.

• token-optimizer-mcp - Earlier Revision

  Distributed as npm:@ooples/token-optimizer-mcp. Resolved from the published package: @ooples/token-optimizer-mcp 5.7.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Vercel MCP - Current Spec Verified

  Vercel's first-party hosted MCP server: docs search, project and deployment management, log analysis, and Web Analytics queries. Serves the stateless 2026-07-28 revision and 2025-era clients from the same endpoint, with OAuth authorization.

• Yaw MCP - Spec Support Unverified

  Distributed as npm:@yawlabs/mcp. First-party: the server is YawLabs' own product (yaw.sh/mcp documents it as "A CLI that runs MCP servers on your machine"). An orchestrator that fronts other MCP servers from one connection; local-first, no account. No MCP revision statement found on yaw.sh/mcp or in the README (checked 2026-08-27).