MCP servers that ship as code — a repository or a package you install and run locally (usually over stdio). They have no hosted endpoint, so we cannot probe or grade them: instead each one shows its repository, install command, license, stars and when it was last updated.
Collected from GitHub repositories and npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems packages tagged as MCP servers, the official MCP Registry, Docker's MCP catalog, ModelScope, Baidu MCP World, Cline and other public directories; one entry per repository. A server that also offers a hosted endpoint is listed under Remote instead. These entries are not counted in our reachability, verification or readiness statistics.
-
Claude Code Multi-Worktree Helper - Single-session parallel worktree automation with MCP server
npm MIT -
Coding agents are single-player. Motif makes your team's multiplayer, Claude Code, Codex and Cursor sessions on your own server, recalled by your agents over MCP. Self-hosted.
npm Apache-2.0 -
Persistent, cross-session memory for Claude Code. Archives every session transcript losslessly, indexes it at turn granularity, and gives the model precise recall over its own history. A single static Rust binary, local-only.
MIT ★ 3 -
Paid MCP servers for the MCPize marketplace. Multi-Project Coordinator: manage multiple repos from a single Claude Code session.
-
Local MCP server bridging Claude Code and Telegram — drive Claude from your phone: replies, tool approvals, background runs, fresh sessions. Single Go binary.
MIT -
Your AI forgets everything between sessions. SAME fixes that. Local-first, no API keys, single binary.
NOASSERTION ★ 24 -
Rust MCP code intelligence for coding agents — live indexes, bounded hybrid retrieval, host-neutral workflows, single-writer sessions, and mutation gates.
Apache-2.0 ★ 3 -
Proxy MCP: one server that runs Playwright, Figma, Chrome DevTools, Shopify Dev and Context7 behind a single connection - and cuts their token cost with compact snapshots, caching and session recovery.
npm MIT ★ 24 -
anti-botgithub.com/TaroYamada08/anti-botupdated this year
Its fetchers bypass anti-bot systems like Cloudflare Turnstile out of the box. And its spider framework lets you scale up to concurrent, multi-session crawls. 🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!
BSD-3-Clause ★ 1 -
Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF search with episode batching. Single SQLite DB, no external services. Alternative to claude-mem with 600x lower cost.
MIT ★ 68 -
Turns any text stream into a dated history of how its subject changed. Point it at your Claude Code, OpenCode or Codex sessions to track how you think and work, or at market news, research, or any corpus to track how it changed — raw records to observations to bi-temporal facets to narrative, with provenance, served over MCP. Single pure-Go binary.
npm MIT ★ 12 -
agentedgithub.com/frane/agentedno update data
A text editor for LLMs, not humans. Take ed, the line editor that nobody has voluntarily used since about 1975, and rebuild it for an environment where the typing user is a language model. Short verbs, line addresses, no modes, no TUI. What an editor optimises for changes when the user is the model: round trips per task, tokens per command, an editing buffer with a long memory, and an undo tree that remembers the branches the agent abandoned, because that's often where the interesting work was. ## Features - **Fewer round trips.** Read-before-Edit is unnecessary; on conflict the response carries the new content so you reconcile in one call instead of pre-reading every time. - **Branching undo.** Walked-back work stays addressable instead of being thrown away when you pick a different path. - **Three-way merge.** Concurrent agents get a structured conflict response instead of a silent overwrite. - **Atomic batches.** Multi-file refactors run all-or-nothing instead of leaving half-applied state on failure. - **Cross-file moves and regex replace as primitives.** Operations the built-in tools can't express cleanly become single calls. - **Drift detection.** External edits to an open file are folded into the tree instead of being clobbered by the next write. - **Inline diagnostics.** Type errors and lint findings surface on save, not at the next build many edits later. - **Cross-session memory.** Per-file notes persist between sessions and surface inline on the next open. - **Audit log.** Every operation recorded with actor and timestamp, so two agents in one workspace can't argue about who moved the head. ## Multi-workspace (v0.4.0) One MCP server registration handles every project you mention. Tool calls route to the workspace owning the absolute path you pass; each project gets its own SQLite, its own undo tree, its own LSP daemon — lazily spawned on first touch. Desktop hosts (Claude Desktop, Codex Desktop, Cursor) install the server once globally and use it across projects without per-project config. ## Install `ae` must be installed locally; this MCP bundle registers `ae serve` as a stdio server. ```sh brew tap frane/tap && brew install agented # or curl -sSL https://raw.githubusercontent.com/frane/agented/master/install.sh | sh ``` Pure Go, single static binary, Apache 2.0. Source: https://github.com/frane/agented
smithery -
the-metis-fca-handbook-ai-harness-mcpno update data
# Metis FCA Handbook AI Harness — MCP Server An MCP (Model Context Protocol) server that integrates the Metis FCA Handbook AI Harness into Claude Desktop and other MCP-compatible agents. **Tool name:** `evaluate_fca_handbook_applicability` Use this tool to analyze FCA Handbook applicability for a product, service, or firm. Returns structured compliance reasoning with verbatim handbook citations. ## Why choose The Metis FCA Handbook AI Harness? - **Efficiency** Multiplies effectiveness of compliance advice. Saves £80+ in token fees per Harness run. - **Deals with "Hard Problem"**, in which LLMs' token incentives prioritise training data so results are unreliable. - **Verbatim citations** Quotes verbatim entries from the FCA Handbook. Other AI systems struggle to do this. - **Matches real-world need** You do not have to start off knowing which sections you are looking for. Carries out structured searches across all 10,000+ FCA Handbook entries. - **Secure Design** Harness compartmentalisation, one-shot structure, and statelessness fits natively with emerging AI agent security standards such as OWASP Top 10 for Agentic Applications 2026. - **AI Accessible** Integrates easily with AI workflows and agents. Your LLM can use it as a tool. ## Design Principles The Harness is built on proven principles: - **Stateless** — Each request is independent; no session coupling - **One-shot** — Complete analysis in a single call; no multi-turn state - **Clear contract** — Explicit input/output schemas for easy integration - **Hosted** — Single canonical source; no version drift or stale data ## Use Cases ### Compliance AI Platforms Embed FCA reasoning as a service within your compliance platform. Users ask natural-language questions; your platform calls the Harness and presents structured reasoning. ### AI Agent Workflows Agents building compliance workflows can include FCA Handbook reasoning as a composed tool—no external API calls, just MCP configuration. ### Compliance Review Automation Integrate into document review or due-diligence pipelines. Automatically screen new rules against FCA applicability. ## For Regulatory Screening FS firms screening MCP servers will find: - **Simple model:** Stateless, no hidden state, no background jobs - **Clear contract:** Explicit input schema, output schema, error modes - **Transparent updates:** Version pinning; no automatic upgrades - **Single point of failure:** If the Harness is down, it is obvious; no cascading config issues - **Audit-friendly:** All calls logged centrally, not distributed
smithery -
Contextualno update data
## Contextual — Persistent Memory for AI Coding Agents AI coding agents forget everything the moment your session ends. **Contextual** fixes that by giving any MCP-capable AI client — for developers who use multiple AI coding tools at once — a real, persistent memory of your codebase: not just what the code says, but what changed and why. It's a **local-first MCP server**: your code, your index, and every query stay on your machine. The only network call is a lightweight, infrequent license check — no code, ever, leaves your device. Under the hood, Contextual builds a real understanding of your repository, not a text-similarity guess: - **Structural search** — tree-sitter AST parsing + call-graph resolution, so agents reason about how your code actually connects. - **Bitemporal history** — tracks not just when your code changed, but when the AI learned about it. Ask "did this bug fix happen before or after the agent's understanding of this function?" and get a real answer. - **Git-aware retrieval** — temporal, history-grounded context instead of a stale snapshot. - **Fast, self-contained** — index a 50k-line repository in about 5 minutes, then query it in ~94ms median, from a single ~0.8GB install. This extension connects Claude Desktop (or any MCP-capable client) to a Contextual installation already set up and activated on your machine — it does not provision Contextual from scratch.
smithery