Répertoire des serveurs MCP

Réponse rapide

Un serveur Model Context Protocol (MCP) est ce qui donne à un LLM local de vraies capacités — fichiers, git, un navigateur, une base de données, un désassembleur, un outil de conception de PCB — via une interface ouverte que tout client MCP peut appeler. Les modèles sont le cerveau ; les serveurs MCP sont les mains. C'est la couche de souveraineté que la plupart des auto-hébergeurs oublient : vous pouvez exécuter le modèle sur votre propre matériel et confier quand même chaque capacité aux outils cloud de quelqu'un d'autre. Auto-hébergez aussi les serveurs MCP et les mains de l'agent sont les vôtres. Ce répertoire cartographie les serveurs établis par capacité, chaque auteur crédité, le transport (stdio privé vs distant en réseau), l'authentification, la licence et l'adéquation à l'auto-hébergement — y compris les propres serveurs Konduit (KiCad/EDA) et Ghidra de D-Central, crédités aux projets ouverts sur lesquels ils s'appuient.

Commencez par les serveurs stdio de référence MIT (filesystem, git, fetch, memory) — ils couvrent l'essentiel de ce dont un agent local a besoin et s'auto-hébergent trivialement. Ajoutez un navigateur (Playwright), une base de données en lecture seule, et un serveur de domaine (Konduit pour le matériel, Ghidra pour la RE) selon la tâche. Gardez les serveurs sensibles sur stdio, limitez la portée de chaque jeton, et vérifiez chacun à son dépôt — MCP évolue chaque mois, alors traitez ceci comme une carte datée, pas un registre en direct.

Pourquoi auto-héberger aussi les outils ? This is the sovereignty layer everyone forgets. You can self-host the model and still hand all your capability to someone else's cloud tools. Self-hosting the MCP servers too means your agent's hands are yours: the filesystem server runs on your disk, the git server on your repo, the hardware-design server on your bench — no third party sees the data your agent touches. Our model database and runtime comparison cover the brain; this covers the hands. Voir aussi quels runtimes locaux parlent MCP et le classement de conception matérielle qui évalue Konduit.

🟠 Carte datée, pas un registre en direct (2026-07-18). MCP évolue chaque mois — transports, licences et noms changent. Vérifiez chaque serveur à son dépôt ; les licences marquées « verify » ne sont pas affirmées.

Files & local

Filesystem

easy

Anthropic / MCP reference

The canonical reference server: give an agent scoped read/write to chosen directories. The first server most self-hosters wire up.

Transportstdio
Authlocal FS permissions (scoped roots)
LicenceMIT

Version control

Git

easy

Anthropic / MCP reference

Read, search and manipulate local Git repositories — history, diffs, commits — without shelling out.

Transportstdio
Authlocal repo access
LicenceMIT

GitHub MCP Server

moderate

GitHub (official)

Official GitHub server: issues, PRs, repos, Actions. Available as a GitHub-hosted remote endpoint or self-hosted locally; scope the token tightly.

Transportremote HTTP + local
AuthOAuth / personal access token
Licenceopen — verify at repo

Search & fetch

Fetch

easy

Anthropic / MCP reference

Fetch a URL and convert it to clean markdown for the model. The minimal, self-hosted alternative to a hosted browse tool.

Transportstdio
Authnone (outbound HTTP)
LicenceMIT

Memory & knowledge

Memory

easy

Anthropic / MCP reference

A persistent knowledge-graph memory the agent reads and writes across sessions — local, yours, no cloud.

Transportstdio
Authlocal store
LicenceMIT

Reasoning

Sequential Thinking

easy

Anthropic / MCP reference

A structured step-by-step reasoning scaffold exposed as a tool. Pure local logic, no external calls.

Transportstdio
Authnone
LicenceMIT

Testing

Everything

easy

Anthropic / MCP reference

The reference/test server that exercises every MCP feature (tools, resources, prompts) — the thing you point a new client at to confirm it speaks MCP correctly.

Transportstdio
Authnone
LicenceMIT

Browser automation

Playwright MCP

easy

Microsoft

Drives a real browser via the accessibility tree rather than screenshots — fast, deterministic web automation an agent can run locally.

Transportstdio
Authnone (drives a local browser)
LicenceApache-2.0 (verify)

Chrome DevTools MCP

easy

Google / Chrome

Exposes Chrome DevTools to an agent for debugging, performance traces and DOM inspection of a locally-driven browser.

Transportstdio
Authnone (local Chrome)
Licenceopen — verify at repo

Databases

Database (Postgres / SQLite)

moderate

community / MCP ecosystem

Query and inspect a database over MCP. Multiple implementations exist (official reference + community forks); pick one that supports read-only mode for safety. Verify the exact server you choose.

Transportstdio
AuthDB connection string
Licencevaries — verify at repo

Reverse engineering

Ghidra MCP

moderate

community (e.g. LaurieWired) — verify upstream

Drives the open-source Ghidra disassembler from an agent — decompile, rename, analyse binaries. D-Central uses a Ghidra MCP server in its reverse-engineering work; credit to the open Ghidra project and the community server authors.

Transportstdio
Authlocal Ghidra instance
Licenceopen — verify at repo

EDA / hardware design

DCENT_Konduit D-Central

moderate

D-Central

D-Central's own KiCad MCP server: ~182 tools across schematic, PCB, routing, DRC/ERC and manufacturing. A single Rust binary driving KiCad 10 over its IPC API. It is the benchmark subject of our hardware-design LLM leaderboard. 🟠 Built on the shoulders of mixelpixx/Konnect (which it forks) and the wider KiCad-MCP ecosystem — credited below.

Transportstdio + Streamable HTTP
Authlocal KiCad 10 (IPC)
Licencesource-available — verify

Konnect (upstream)

moderate

mixelpixx

The upstream Rust KiCad MCP server (native KiCad 10 plugin, ~171 tools) that DCENT_Konduit forks. Credited as the predecessor our hardware-design work builds on.

Transportstdio + HTTP
Authlocal KiCad (IPC)
Licenceopen — verify at repo

KiCAD-MCP-Server

moderate

mixelpixx

The earlier, most-popular Python KiCad MCP server (schematic + PCB tooling, JLCPCB, Freerouting). The predecessor generation to the Rust Konnect/Konduit line — credited.

Transportstdio
Authlocal KiCad
Licenceopen — verify at repo

Docs & knowledge

Context7

remote-first

Upstash

Injects up-to-date library/framework documentation into the model's context — reduces hallucinated APIs. Primarily a hosted endpoint; included as the pragmatic docs option.

Transportremote HTTP
AuthAPI key (free tier)
Licencehosted service (client open)

stdio vs distant. Two transports matter. stdio servers run as a local subprocess of the client — the most private, the default for anything touching local files or hardware. Remote servers speak Streamable HTTP (or the older SSE) and run as a network service — convenient and shareable, but now something is listening on a port, so authentication and scope matter. Prefer stdio for anything sensitive; reach for remote only when you deliberately want a shared, multi-client tool.

D-Central dans cet écosystème. D-Central builds in this ecosystem, not just alongside it. DCENT_Konduit is our own KiCad MCP server — the tool behind the hardware-design leaderboard on our LLM benchmark hub — and we run a Ghidra MCP server for reverse-engineering work. Both stand on open predecessors: Konduit forks mixelpixx/Konnect, which followed the earlier KiCAD-MCP-Server, and the Ghidra server builds on the open Ghidra project. We credit them plainly, because that is how this ecosystem is supposed to work.

Données ouvertes (CC BY 4.0) : CSV · JSON · API : /wp-json/dc/v1/mcp-servers

Produits, réparations et guides connexes

Dernière révision: 27 juillet 2026.