17 published servers

Best Developer Tools MCP Servers

Developer tool servers bring software engineering context and actions into an MCP client. Depending on the project, that might mean inspecting code, consulting framework documentation, running a development utility, or examining a debugging session. This category is intended for the work around building software, rather than every service a software team uses. Repository hosting belongs under version control, while infrastructure operations are grouped separately under cloud and DevOps.

Begin by deciding whether the assistant needs read access, execution access, or both. A documentation lookup tool has a very different risk profile from one that can launch commands in your workspace. Read the installation instructions for runtime requirements and check how paths, working directories, and environment variables are selected. Try the server against a small test project before granting access to a production codebase. Useful comparison points include the clarity of tool inputs, the size of returned context, and how errors are reported. Prefer explicit permissions and reproducible commands over broad access that is difficult to audit after a coding session.

Compare Developer Tools servers

# / ServerWhy pick itStarsLast commitRuntimeRemote
Pick it to discover task-relevant MCP servers without knowing their names in advance.89Oct 16, 2026nodeNo
Add symbol-aware IDE capabilities to coding agents instead of relying entirely on text search and edits.30,329Oct 15, 2026pythonNo
Ground coding assistance in targeted library documentation, including version-specific examples.63,157Oct 16, 2026nodeNo
Add agent access to a FastAPI service while retaining native schemas, docs, and authentication patterns.12,025Nov 24, 2025pythonNo
Ground coding questions in public GitHub documentation and code without repository-side setup.8,465May 8, 2026nodeNo
Choose it for Xcode agent tooling available through either MCP or a unified terminal CLI.6,486Oct 16, 2026nodeNo
Consider DevDocs for documentation crawling and MCP retrieval, while accounting for its maintenance notice.2,108Feb 4, 2026nodeNo
Use only for legacy plugin connections; newer JetBrains IDEs provide an integrated replacement.963Jan 7, 2026nodeNo
Choose it to give an MCP coding assistant semantic navigation powered by an existing language server.1,610Mar 1, 2026goNo
Match retrieved UI implementations to the framework and React primitives your project actually uses.3,059Oct 3, 2026nodeNo
A compact two-tool interface for verified Nix ecosystem lookups and reproducible version references.858Sep 5, 2026pythonNo
Bring Sentry investigation and issue triage directly into a human-guided coding session.754Jul 3, 2026nodeNo
Explore experimental MCP context integration at the Nuxt or Vite development-server layer.911Mar 1, 2026nodeNo
Choose wcgw for a shared interactive agent terminal plus code-editing and checkpoint tools.678Sep 12, 2026pythonNo
Use quick file indexing and opt-in deep syntax analysis to help assistants navigate larger repositories.1,003Jul 27, 2026pythonNo
Pick it for repository-grounded coding prompts and programmable Neovim context retrieval.876Feb 23, 2026pythonNo
Pick it for live Vue debugging context that includes components, routes, Pinia, and editable state.578Apr 20, 2025vueNo

Ordered by featured status, editorial order, then repository stars. Stars may cover an entire monorepo and are a dated snapshot, not a quality or security guarantee.

Frequently asked questions

Start with the exact tools your task needs, then compare runtime requirements, supported transports, permissions, and recent project activity. Test with nonsensitive data before connecting a production account. A high star count is a discovery signal, not a security audit.

The directory is free to browse. A server’s code license and any connected provider’s charges are separate matters. Check the upstream license, API pricing, and account requirements before installing.

Compatibility depends on the server’s transport and the client’s supported configuration. Local stdio commands and remote HTTP or SSE endpoints are not interchangeable. Follow the client guides and verify the current upstream documentation.