"Information about Docker - A Platform for Software Containers" matching MCP servers:

Facilitates software development planning through interactive sessions that break down projects into manageable tasks with complexity scoring, code examples, and implementation plan management.

Facilitates interactive software development planning by managing tasks, tracking progress, and creating detailed implementation plans through the Model Context Protocol.

An MCP server that facilitates interactive software development planning by breaking down projects into manageable tasks, tracking progress, and saving implementation plans.

Provides software development planning tools to help users create implementation plans and manage todo items.

Lets an AI assistant read and write business records in plain language, including looking up people, creating and updating tasks, logging time, and pulling utilization reports through a synthetic ops platform or an optional ClickUp adapter.

MCP server wrapping a mock internal ops platform (FastAPI + SQLite) so Claude Code can read and write employee, project, task, and time data through natural language.

Enables multi-tenant task management through a remote MCP server with OAuth2 authentication, per-tenant data isolation, rate limiting, and a client SDK.

Enables Claude Code to read and write issues on the Testing Platform via natural language, including listing projects, filtering issues, creating and updating issues, and adding comments.

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.

Automates enterprise Power Platform project setup and management via MCP, reducing setup time from weeks to hours through template-based provisioning, Azure DevOps orchestration, and direct API integration.

A standalone MCP server that provides AI tools by proxying requests to the FTC Platform's REST API, enabling tasks like fetching event applications, evaluations, and scoring criteria.

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 AI assistants to search and manage construction project economic data, including unit price analyses, resource catalogs, budget trees, and price lists, with secure multi-tenant access.

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 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 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.

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.