"Connecting MCP Servers to a Local Project" matching MCP servers:

Enables reading books from Project Gutenberg via MCP, with tools to search books, fetch metadata and full text, and retrieve passages by fixed-size keys.

Local-first Microsoft Outlook MCP server: a single Go binary that manages calendar events and mail through the Microsoft Graph API over stdio, with tokens stored in the OS keychain and no Entra ID app registration required. Exposes four aggregate tools (calendar, mail, account, system) dispatched by an operation verb, with multi-account support and read-only and mail-gating modes.

Connects AI tools to GitHub and local git repositories, enabling natural language management of issues, PRs, code analysis, and workflows.

This project is intended as a both MCP server connecting to Kubernetes and a library to build more servers for any custom resources in Kubernetes.

Minimal Go library for building stdio MCP servers on the official go-sdk — struct-derived JSON Schema, tiny static binaries.

Local, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates

Baryon connects MCP-compatible AI assistants to Proton Mail through a local bridge, enabling email search, reading, attachment handling, and draft creation while enforcing deliberate permission limits. It runs locally and cannot send, delete, or modify mail.

Local-first MCP proxy with BM25 tool discovery, quarantine security, Docker isolation, OAuth support, activity logging, and web UI. Routes multiple upstream MCP servers through a single endpoint.

MCP gateway/proxy: multiplexes tool calls across upstream MCP servers into one aggregated, namespaced catalog and logs every call. Local, single-user, $0/month by default.

MCP server that exposes Google Jules AI agent as tools, allowing local AI agents to list authorized repositories and delegate coding tasks to Jules, receiving session URLs for tracking.

Local ledger for development ports: leases a block of ports per project slot (one per working copy), renders env files, and resolves service names to URLs. No daemon, no listener.

An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository. There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code

Enables read-only search and retrieval of your email across multiple IMAP accounts through a local notmuch index, served over authenticated HTTP for MCP clients like Claude or Codex.

rhizome-mcp is a local-first MCP server for task tracking and coordination of autonomous AI coding agents, providing crash-safe issue claiming, durable project memory, and dependency graphs using SQLite. It enables agents from different MCP-compatible clients to share a consistent view of project work with no accounts, Docker, or network dependency.

MCP server that reads Duplicacy backup metrics from a Prometheus exporter and exposes them to LLMs for monitoring backup status, progress, and health.

An MCP orchestration layer that aggregates multiple MCP servers while exposing only 8 meta-tools, dramatically reducing context window usage, and provides SLOP scripting, event monitoring, and tool customization.

Zero trust gateway for MCP servers. Aggregate, filter, and securely access MCP tools from anywhere without VPNs, open ports, or exposed endpoints. Built on OpenZiti, zrok, and Agora with cryptographic identity, mTLS, per-client isolation, and tool-level permission control.

Seamlessly bring real-time production context—logs, metrics, and traces—into your local environment to auto-fix code faster.

This project implements a simple MCP server in Go that exposes a single tool (create_short_link) to generate short URLs using the Rebrandly API.

Official MCP server built into Casdoor, the open-source identity and access management (IAM) and single sign-on (SSO) platform. It exposes Casdoor's users and applications as MCP tools over a JSON-RPC endpoint at /api/mcp, with per-tool authorization driven by OAuth scopes, and can also act as an MCP gateway that proxies and authorizes agent access to upstream MCP servers.