"filesystem" matching MCP servers:

Provides project management capabilities through terminal, web UI, or MCP stdio, including plans, code analysis, and filesystem-safe operations.

Exposes a filesystem-driven four-lane kanban board as a read-only MCP server, enabling agents to inspect board state, card details, and lane counts.

An MCP server for intelligent project planning and task management featuring task tracking, bug reporting, and feature specification with SQLite persistence. It includes full-text search capabilities and automatic filesystem synchronization to keep project data organized and accessible.

A filesystem-backed MCP server with REST API for AI tool integration and project workflow tracking. Zero database required.

Enables read-only querying, evaluation, challenge, and judging of an Oracle project's rules and evidence without modifying the filesystem, plus task tracking for agents.

Companion MCP server for the OllamaDev Android app, providing 36 tools for SDLC phases including filesystem, code intelligence, build, sprint workflow, and agentic self-prompt via a local Ollama model.

Enables AI agents to manage a filesystem-based issue tracker through typed MCP tools such as list_tasks, create_task, change_task_status, log_work, and get_sprint, instead of shelling out to a CLI. Tasks and sprints are plain folders of Markdown files, so agents can create, claim, comment on, and move work by topic without any database or server state.

Gives AI coding providers a shared, provider-agnostic workflow for authoring use cases and specs, claiming and tracking tasks across lead, explorer, consultant, builder, and reviewer roles, recording handoffs, and gating completion on native health scripts. It owns task claims, action logs, handoffs, and final health results over MCP, so teams can move from a request to verified work while specifications stay as Markdown files on the filesystem.

Provides a stdio MCP server that drives structured multi-agent development workflows: claiming and updating tracked tasks, logging actions and handoffs, gating work on server-owned health checks, and managing use-case, functional, and technical specification documents on the filesystem. It also exposes read-only skills for triage, consultation, review, and product guidance while enforcing approval and repair authorizations.

Gives AI coding providers a shared, provider-agnostic workflow server for drafting and approving Markdown specifications, claiming tracked tasks, logging actions, routing role handoffs, and gating completion on verifiable health checks. It works across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode, keeping documents on the filesystem while task, evidence, and health data live in a configured database.