"A proxy MCP server for connecting to other MCP servers" matching MCP servers:

Enables Claude Code to use a filtered subset of Atlassian Rovo MCP tools for Jira and Confluence, automatically injecting required parameters and stripping noisy fields to reduce token usage.

One-pass agentic inbox triage as an MCP server: fetch unread Gmail → classify (action_needed/fyi/newsletter/noise) → summarize → extract tasks → draft replies as Gmail DRAFTS (never sends) → flag calendar → write a triage report. Four stdio tools (fetch_emails, save_gmail_draft, append_tasks, write_report); the host is the LLM, so it runs keyless in Claude Code. Gmail scopes: readonly + compose

Provides AI assistants with a standardized interface to interact with the Todo for AI task management system. It enables users to retrieve project tasks, create new entries, and submit completion feedback through natural language.

Enables multi-user, network-reachable MCP interaction with Redmine, with per-user impersonation and identity-based access control.

Enables an MCP client to retrieve explicitly allowlisted Markdown context, create and read local task contracts, write local handoffs, and return locally configured routing metadata without invoking a model, executing commands, or writing to the vault.

Enables agentic co-authoring of feature specs, decomposition into architecture-validated tickets, and idempotent syncing to Linear as projects with epics, sub-issues, and dependencies.

Lets AI agents turn a repository's git history into proposed GitHub issues grouped into units of work, each with a commit checklist and links, then create and close them only after approval. Planning is read-only and creation defaults to a dry run, skipping anything that already exists.

Enables AI clients like Claude to read and manage Microsoft To Do task lists and tasks via the Microsoft Graph API, running locally over stdio with secure token storage.

MCP server for Microsoft To Do via Microsoft Graph. MSAL device code flow, no client secret needed.

MCP for Azure DevOps Boards is a MCP server that lets your favourite AI browse, query and update Azure DevOps work items as if it were a project manager. Written in Rust and optimized for tokens usagem, It runs via stdio or HTTP mode and uses standard Azure authentication with az login.

Enables managing Microsoft To Do lists and tasks through MCP, including creating, updating, completing, deleting, searching, and checklist operations via Microsoft Graph.

Enables Codex projects to read Git-backed kickoff, acceptance, handoff, progress, and next-step context, and to append validated, audited progress events through scoped MCP tools. This supports visible agent progress, resumable sessions, and safer handoffs.

Enables Codex and other MCP clients to read kickoff cards, acceptance criteria, Git evidence, and next steps, then append validated, audited progress events for resumable project handoffs.

Enables to manage to-do items through natural language, with tools for creating, reading, updating, and deleting tasks.

Enables AI-powered project management by connecting Claude to Planka kanban boards via 75+ MCP tools for creating, updating, and managing projects, boards, lists, and cards.

Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.

Enables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.

Enables agents to read Git-backed project context and append audited, idempotent progress events through scoped, short-lived credentials, supporting resumable handoffs and visible project state.

Enables AI agents and users to verify claims about Jira issues and issue counts against live Jira, retrieve verifiable facts for drafting updates, and re-check previously posted claims. It provides read-only tools and an issue panel so status updates can be evidence-based and mismatches corrected before or after posting.

Enables Codex sessions to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step, then append validated, idempotent progress events backed by matching project-record Git commits. Access is limited to a short-lived, revocable credential scoped to one workspace and project, with high-risk actions kept outside the server.

Enables AI agents to read Git-backed project context and append validated, audited, idempotent progress events through short-lived, scoped credentials, supporting resumable work and safer handoffs.

Enables Codex agents to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail and next step, then append validated, audited, idempotent progress events that become matching project-record Git commits. Access is scoped to one workspace and project through short-lived, revocable, hash-stored credentials that cannot touch members, keys, deletion, publication or deployment.

It enables AI agents to retrieve Git-backed project context, handoff packages, and next actions, then append validated, audited progress events as project-record commits.

It lets AI coding clients read a project’s kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append a validated, audited, idempotent progress event with a matching project-record Git commit.

Enables Codex to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events with a matching Git commit.

Enables Codex to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events backed by a matching project-record Git commit. Access is scoped to one workspace and project via short-lived, revocable, hash-stored credentials that cannot reach members, keys, deletion, publication, or deployment.

Enables Codex agents to read a project's kickoff card, acceptance criteria, progress, Git trail, and handoff package, then append one validated, idempotent progress event with an agent verification note and matching Git commit. Access is limited to short-lived, scoped, revocable credentials bound to a single workspace and project, with high-risk actions kept outside the tool surface.

Enables MCP clients to read a project's Git-backed kickoff, acceptance criteria, handoff package, progress, and next step, and to append validated, audited progress events as project records. It provides short-lived scoped credentials and fail-closed tool allowlisting for safe, resumable AI-assisted development.

Enables AI agents and humans to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step, then append audited, idempotent progress events that are committed to the project's Git record. Access is scoped per project through short-lived, revocable credentials, keeping high-risk actions outside the tool surface for human approval.

Enables MCP clients to read a project’s kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events as Git-backed project records.