{
    "meta": {
        "title": "D-Central — Self-Hosted MCP Server Directory",
        "description": "A sovereign builder's map of 15 established Model Context Protocol (MCP) tool servers by capability category (files, version control, browser, databases, reverse engineering, EDA/hardware design, docs): author, transport (stdio vs remote), auth, license, self-host suitability. Features D-Central's own Konduit and Ghidra servers, credited to their upstream predecessors. A dated, curated index — not a live registry.",
        "generated": "2026-07-18T22:30:49+00:00",
        "as_of": "2026-07-18",
        "version": "1.0",
        "license": "https://creativecommons.org/licenses/by/4.0/",
        "license_name": "CC BY 4.0",
        "source": "https://d-central.tech/fr/mcp-server-directory/",
        "method": "A curated, DATED directory of well-established MCP servers organized by capability, not an exhaustive live registry — MCP moves monthly. Transports and licenses are stated where we can state them with confidence and marked \"verify at repo\" otherwise, never asserted when uncertain. D-Central's own servers are flagged and credited to the upstream projects they fork/build on (Konnect, KiCAD-MCP-Server, the Ghidra project).",
        "provenance": "MCP specification + the servers' own repositories; D-Central first-party for the Konduit/Ghidra entries. Companion to /local-ai-runtime-comparison/ (which runtimes speak MCP) and the hardware-design leaderboard on /llm-benchmarks/.",
        "disclaimer": "MCP is a fast-moving ecosystem: verify each server's current transport, license and status at its repository before relying on it. Licenses marked \"verify\" are not asserted. Self-host sensitive (stdio) servers and scope every credential."
    },
    "rows": [
        {
            "name": "Filesystem",
            "author": "Anthropic / MCP reference",
            "category": "Files & local",
            "transport": "stdio",
            "auth": "local FS permissions (scoped roots)",
            "license": "MIT",
            "self_host": "easy",
            "dcent": false,
            "note": "The canonical reference server: give an agent scoped read/write to chosen directories. The first server most self-hosters wire up."
        },
        {
            "name": "Git",
            "author": "Anthropic / MCP reference",
            "category": "Version control",
            "transport": "stdio",
            "auth": "local repo access",
            "license": "MIT",
            "self_host": "easy",
            "dcent": false,
            "note": "Read, search and manipulate local Git repositories — history, diffs, commits — without shelling out."
        },
        {
            "name": "Fetch",
            "author": "Anthropic / MCP reference",
            "category": "Search & fetch",
            "transport": "stdio",
            "auth": "none (outbound HTTP)",
            "license": "MIT",
            "self_host": "easy",
            "dcent": false,
            "note": "Fetch a URL and convert it to clean markdown for the model. The minimal, self-hosted alternative to a hosted browse tool."
        },
        {
            "name": "Memory",
            "author": "Anthropic / MCP reference",
            "category": "Memory & knowledge",
            "transport": "stdio",
            "auth": "local store",
            "license": "MIT",
            "self_host": "easy",
            "dcent": false,
            "note": "A persistent knowledge-graph memory the agent reads and writes across sessions — local, yours, no cloud."
        },
        {
            "name": "Sequential Thinking",
            "author": "Anthropic / MCP reference",
            "category": "Reasoning",
            "transport": "stdio",
            "auth": "none",
            "license": "MIT",
            "self_host": "easy",
            "dcent": false,
            "note": "A structured step-by-step reasoning scaffold exposed as a tool. Pure local logic, no external calls."
        },
        {
            "name": "Everything",
            "author": "Anthropic / MCP reference",
            "category": "Testing",
            "transport": "stdio",
            "auth": "none",
            "license": "MIT",
            "self_host": "easy",
            "dcent": false,
            "note": "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."
        },
        {
            "name": "GitHub MCP Server",
            "author": "GitHub (official)",
            "category": "Version control",
            "transport": "remote HTTP + local",
            "auth": "OAuth / personal access token",
            "license": "open — verify at repo",
            "self_host": "moderate",
            "dcent": false,
            "note": "Official GitHub server: issues, PRs, repos, Actions. Available as a GitHub-hosted remote endpoint or self-hosted locally; scope the token tightly."
        },
        {
            "name": "Playwright MCP",
            "author": "Microsoft",
            "category": "Browser automation",
            "transport": "stdio",
            "auth": "none (drives a local browser)",
            "license": "Apache-2.0 (verify)",
            "self_host": "easy",
            "dcent": false,
            "note": "Drives a real browser via the accessibility tree rather than screenshots — fast, deterministic web automation an agent can run locally."
        },
        {
            "name": "Chrome DevTools MCP",
            "author": "Google / Chrome",
            "category": "Browser automation",
            "transport": "stdio",
            "auth": "none (local Chrome)",
            "license": "open — verify at repo",
            "self_host": "easy",
            "dcent": false,
            "note": "Exposes Chrome DevTools to an agent for debugging, performance traces and DOM inspection of a locally-driven browser."
        },
        {
            "name": "Database (Postgres / SQLite)",
            "author": "community / MCP ecosystem",
            "category": "Databases",
            "transport": "stdio",
            "auth": "DB connection string",
            "license": "varies — verify at repo",
            "self_host": "moderate",
            "dcent": false,
            "note": "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."
        },
        {
            "name": "Ghidra MCP",
            "author": "community (e.g. LaurieWired) — verify upstream",
            "category": "Reverse engineering",
            "transport": "stdio",
            "auth": "local Ghidra instance",
            "license": "open — verify at repo",
            "self_host": "moderate",
            "dcent": false,
            "note": "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."
        },
        {
            "name": "DCENT_Konduit",
            "author": "D-Central",
            "category": "EDA / hardware design",
            "transport": "stdio + Streamable HTTP",
            "auth": "local KiCad 10 (IPC)",
            "license": "source-available — verify",
            "self_host": "moderate",
            "dcent": true,
            "note": "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."
        },
        {
            "name": "Konnect (upstream)",
            "author": "mixelpixx",
            "category": "EDA / hardware design",
            "transport": "stdio + HTTP",
            "auth": "local KiCad (IPC)",
            "license": "open — verify at repo",
            "self_host": "moderate",
            "dcent": false,
            "note": "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."
        },
        {
            "name": "KiCAD-MCP-Server",
            "author": "mixelpixx",
            "category": "EDA / hardware design",
            "transport": "stdio",
            "auth": "local KiCad",
            "license": "open — verify at repo",
            "self_host": "moderate",
            "dcent": false,
            "note": "The earlier, most-popular Python KiCad MCP server (schematic + PCB tooling, JLCPCB, Freerouting). The predecessor generation to the Rust Konnect/Konduit line — credited."
        },
        {
            "name": "Context7",
            "author": "Upstash",
            "category": "Docs & knowledge",
            "transport": "remote HTTP",
            "auth": "API key (free tier)",
            "license": "hosted service (client open)",
            "self_host": "remote-first",
            "dcent": false,
            "note": "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."
        }
    ],
    "context": {
        "what": "The Model Context Protocol (MCP) is the open standard that lets an AI model call external tools and read external data through a uniform interface. An MCP server is a small program that exposes a capability — your filesystem, a git repo, a browser, a database, a disassembler, a PCB design tool — that any MCP-speaking client (Claude, and a growing list of local runtimes) can call. Models are the brain; MCP servers are the hands.",
        "why": "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.",
        "transport": "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.",
        "dcent": "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.",
        "verdict": "Start with the reference stdio servers (filesystem, git, fetch, memory) — they are MIT, trivially self-hosted, and cover most of what a local agent needs. Add a browser server (Playwright) when the agent needs the web, a database server (read-only) when it needs data, and a domain server (Konduit for hardware, Ghidra for RE) when you have a specialist job. Keep the sensitive ones on stdio, scope every token, and verify each server at its repo — this list is a dated map, and MCP moves monthly."
    }
}