Self-Hosted MCP Server Directory — Tool Servers for Sovereign AI Agents

Models are the brain; MCP servers are the hands. This directory maps the established Model Context Protocol tool servers — files, git, browser, databases, reverse engineering, hardware design — by capability, with each author credited and the transport, auth, licence and self-host suitability laid out. Self-host the tools as well as the model and your agent’s capabilities stay yours.

Quick answer

A Model Context Protocol (MCP) server is what gives a local LLM real capabilities — files, git, a browser, a database, a disassembler, a PCB-design tool — through one open interface any MCP client can call. Models are the brain; MCP servers are the hands. This is the sovereignty layer most self-hosters forget: you can run the model on your own hardware and still hand every capability to someone else's cloud tools. Self-host the MCP servers too and the agent's hands are yours. This directory maps the established servers by capability, with each author credited, the transport (private stdio vs networked remote), auth, license and self-host suitability — including D-Central's own Konduit (KiCad/EDA) and Ghidra servers, credited to the open projects they build on.

Start with the MIT reference stdio servers (filesystem, git, fetch, memory) — they cover most of what a local agent needs and self-host trivially. Add a browser (Playwright), a read-only database, and a domain server (Konduit for hardware, Ghidra for RE) as the job demands. Keep sensitive servers on stdio, scope every token, and verify each at its repo — MCP moves monthly, so treat this as a dated map, not a live registry.

Why self-host the tools too? 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. See also which local runtimes speak MCP and the hardware-design leaderboard that benchmarks Konduit.

🟠 Dated map, not a live registry (2026-07-18). MCP moves monthly — transports, licenses and names change. Verify each server at its repository; licenses marked “verify” are not asserted.

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)
LicenseMIT

Version control

Git

easy

Anthropic / MCP reference

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

Transportstdio
Authlocal repo access
LicenseMIT

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
Licenseopen — 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)
LicenseMIT

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
LicenseMIT

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
LicenseMIT

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
LicenseMIT

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)
LicenseApache-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)
Licenseopen — 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
Licensevaries — 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
Licenseopen — 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)
Licensesource-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)
Licenseopen — 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
Licenseopen — 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)
Licensehosted service (client open)

stdio vs remote. 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 in this ecosystem. 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.

Open data (CC BY 4.0): CSV · JSON · API: /wp-json/dc/v1/mcp-servers

Related products, repair, and setup paths

Last reviewed July 18, 2026.