"The role of planning in project development" matching MCP servers:

Enables AI agents and MCP clients to drive real Chrome, Edge, Brave, and Firefox browsers through native automation protocols. It exposes tools for navigation, page snapshots, form filling, clicks, screenshots, console/network inspection, and tab management.

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.

Self-hosted Nightingale (n9e) includes a native Streamable HTTP MCP server at /mcp for querying alerts, rules, metrics, logs, hosts and dashboards with the caller's existing permissions. Users deploy the Nightingale server themselves; the implementation and deployment documentation are in the main repository, and the official website is https://n9e.io.

Give your AI app any GitHub link and the job you want done. UGT gets the project running on your computer and hands you the result.

Serves the review notes left at lines of a diff in seam, a terminal diff viewer, to an agent with the code around them. The agent answers each note, and the answer shows in seam at that line.

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

Lets a model use hundreds or thousands of MCP tools without loading them: it puts five tools in front of a large MCP server or gateway, so the model searches for the tool it needs and calls it. Search combines BM25 with a multilingual embedding model that runs inside the proxy.

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

Lets AI agents drive terminal apps built with Limoni (a Go TUI engine) through their semantic tree instead of scraping the screen: widgets are found by role and label, clicked, typed into, and waited on. Runs locally over the app's automation socket; secret fields never reach the agent.

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.

The Terraform MCP Server is a Model Context Protocol (MCP) server that integrates seamlessly with Terraform Registry and HCP Terraform APIs, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.

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.

Control-plane proxy that sits in front of MCP servers, enforcing per-identity policy (YAML/OPA/Cedar), budget limits, and an audit trail on every call. Includes real-time anomaly detection that auto-blocks a compromised agent without a human in the loop.

Enables an assistant to work inside gitlab.com projects as the signed-in user: issues, merge requests, code reviews, repositories, CI pipelines and job logs, plus optional gated toolsets for wiki, snippets, releases, planning, deployments and activity. It authenticates through a user-supplied OAuth application with the token kept in the OS keyring, and registers only the tools that are switched on.

A command-line interface and MCP server for managing and monitoring multiple development services through a unified terminal UI. It enables users to interact with service logs, filter messages, and control development environments directly via Model Context Protocol integration.

An MCP (Model Context Protocol) server for managing Tailscale resources using the official Tailscale Go client library v2. This server provides complete coverage of the Tailscale API with enhanced, self-descriptive tools powered by OpenAPI documentation.

Gives AI coding agents persistent, structured memory of a software project across sessions — goals, architecture, tech stack, decisions, and progress — stored locally in an embedded SQLite vault. Agents recall and update that context automatically through MCP tools whenever they open the project.

A modern community hub with forum and knowledge base. Native MCP built-in, ready for the next era of internet culture.

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.

Enables governed multi-agent software factory operations through eight typed, audited tools for Sprint planning, submission, decisions, inspection, cancellation, and resumption.

Persistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.

mcp-resile is a resilience gateway for the Model Context Protocol that sits in front of your own MCP servers and protects them from autonomous-agent traffic, with zero backend code changes.

Enables permission-aware codebase onboarding inside IBM Bob by exposing only the code, history, and answers a user's role is allowed to see. It filters context before the model sees it, cites every item, and reports what was withheld.

Enables AI agents to orchestrate 100+ security tools over MCP for authorized penetration testing, including recon, scanning, exploitation, attack-chain planning, and knowledge-base retrieval.

Manages multiple development services with colored logs, filtering, and MCP integration for Claude Code.

The implementation of Model Context Protocol (MCP) server for VictoriaLogs.

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

A single MCP server with 40 tools across 7 categories - PM, Research, Brand, UX, GTM, File, and Web. Built in Go, zero dependencies, one binary. Handles file operations, web fetching, screenshots, search, and planning workflows through one MCP connection.

Provides MCP multi-cluster Kubernetes management and operations, featuring a management interface, logging, and nearly 50 built-in tools covering common DevOps and development scenarios. Supports both standard and CRD resources.