"Noun 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, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates

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

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.

Your coding agent can read the code. It can't read the argument behind it. lema-mcp gives your agent the recorded why — and the alternatives a project already ruled out — cited to the source. For React, Kubernetes, and Rust out of the box, and for your own repo with one command.

Coordination layer for AI coding agents working on the same codebase. Adds file locks, shared project memory, and cross-machine file sync so Claude Code, Cursor, Windsurf, and other MCP agents stop overwriting each other.

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.

Enables coding agents to natively invoke Java project scaffolding operations such as initializing projects, adding modules, designing systems, and suggesting architectures.

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.

ZCP is a CLI with Zerops MCP that makes your agent a Zerops power-user. It runs either inside your project, or is connected through zCLI's VPN functionality to the project from your terminal. Your agent. Your subscription. Your code. Your infrastructure. Your IDE.

Provides long-term local memory for AI coding agents via MCP, enabling persistent recall of preferences and project facts across chat sessions.

Enables ChatGPT on Windows to securely access codebases, Git, terminals, language servers, debuggers, SQLite, local HTTP services, adaptive project memory, engineering skills, checkpoints, audit logs, and sandboxed command execution through MCP tools.

Manages Claude Code configuration and provides cross-session intelligent memory via the Luoshu system, enabling Claude to remember decisions and project context across conversations.

Provides MCP multi-cluster Kubernetes management and operations. It can be integrated as an SDK into your own project and includes nearly 50 built-in tools covering common DevOps and development scenarios. Supports both standard and CRD resources.

Deterministic, schema-driven Go Fiber project scaffolder with an embedded MCP server.

Gru-sandbox(gbox) is an open source project that provides a self-hostable sandbox for MCP integration or other AI agent usecases.

Enables reading and searching API documentation from YApi instances, allowing AI models to access interface definitions, project API lists, and search through API endpoints using YApi URLs or project IDs.

Once configured, you can use natural language commands like: "Search for failed builds in the last week" "Why last deploy was failed" "Search the most failed builds" "Trigger a build for the main branch" "Show me recent builds for project X" "Pin the latest successful build" "Cancel the running bui

Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.