Project Management MCP Servers: Monday, Jira, Dart

Pick Jira for issue workflows, Monday.com for work tracking, and Dart or Taskade for AI-assisted planning. These project management MCP servers each install with one command in Claude Code, Cursor or VS Code. The CheckMCP audit scores Dart 87/100 and Taskade 91/100 as of September 2026. Read each server's scopes before you connect real data.

Why do project-management tools need an MCP server?

An MCP server gives an AI agent a defined set of tools for reading and changing data in another system. Without one, an agent working in Claude Code or Cursor can only guess at what sits on your board, and you end up pasting ticket text into the prompt by hand. With one, the agent can look up tasks and projects, create entries and update them in the same session where it edits code, so the tracker and the work stay in step.

The project management MCP servers in the MCPizy catalogue fall into two groups. Jira is filed under Developer Tools and manages projects, issues and workflows. Monday.com, Fibery, Dart, Taskade and Routine are filed under Productivity and cover work management, connected workspaces, AI planning and personal scheduling. All of them install the same way: run mcpizy install followed by the server name, or start the package directly with npx or uvx.

Access is the real decision. An agent that can write to your tracker can also close the wrong ticket, so read the upstream documentation and the permissions each token grants before connecting a live workspace. The guide on how to audit an MCP server before install walks through the licence, maintenance and documentation checks worth running first.

Monday.com MCP: work management and project tracking

The Monday.com server is built for work management and project tracking. Install it with mcpizy install monday, or run it directly with npx -y monday-mcp. It works with Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot and any other MCP client, so the same server follows you between editors.

It suits teams whose status already lives in Monday.com and who want an agent to answer status questions or update tracking from inside the editor instead of switching tabs. Because it covers general work management rather than engineering issues specifically, it is a fit when marketing, operations and product teams share one tracker with developers.

Before first use, read the upstream documentation for the scopes the connection needs, and start with read-only access so the agent can summarize before it can change anything. Ask for a status summary of one project first and compare it with what you see in Monday.com; if the two match, allow the agent to create or update items in that same project only.

Jira MCP: projects, issues and workflows for developers

The Jira server manages projects, issues and workflows, and it is the only server in this group filed under Developer Tools. Install it with mcpizy install jira or run npx -y jira-mcp directly. The CLI writes the configuration into your client for you, and the server works in Claude Code, Cursor, Windsurf, Claude Desktop and VS Code with Copilot.

The natural use is a coding agent that reads the issue it is about to work on, makes the change and reports back on the same ticket. The Issue → Branch → PR Pipeline recipe shows that shape with a different tracker, and How to Connect Linear to Cursor with MCP shows the general flow of wiring a tracker into an editor.

Keep the first session narrow. Let the agent search and read issues, review what it proposes to create, and only then allow transitions and edits. Workflow changes on a shared Jira project affect every teammate, so an agent that can move tickets between states deserves the same care as a new colleague with write access.

Which tool fits a small team without heavy overhead?

A small team rarely needs every feature of a large tracker; it needs tasks, a short list of projects and an agent that can keep both current. Dart is built for that: AI project management with task, doc and project tracking, plus smart prioritization and workflows. The CheckMCP audit of its-dart/dart-mcp-server scores it 87/100, grade B, with 128 stars, an MIT licence, 3 open issues and a last commit 24 days old as of September 2026. Install it with mcpizy install dart or npx -y dart-mcp-server.

Taskade is an AI-powered workspace for tasks, projects, notes and team collaboration with real-time sync. The CheckMCP audit of taskade/mcp gives it 91/100, grade A, with 165 stars, an MIT licence, 9 open issues and a last commit 25 days old as of September 2026. Run it with npx -y @taskade/mcp-server or mcpizy install taskade. Tasks and notes in one workspace suit teams that write as much as they track.

If all you need is a task list, Todoist offers task management through the Todoist API and starts with npx -y todoist-mcp-server. Note what the audit numbers measure: the CheckMCP audit scores licence, adoption, maintenance and documentation, so a high grade says the repository is looked after, not that the tools fit your process. Try one on a throwaway project first.

Fibery and Routine: connected workspaces and planners

The Fibery server targets product teams, and it covers queries, entity operations and work management. Install it with mcpizy install fibery or run uvx fibery-mcp-server. Note the runner: this one uses uvx rather than npx, so have uv available on the machine before you configure it. A GitHub repository is linked for the source.

Queries and entity operations suggest an agent working against structured records instead of free-form pages. That fits product teams that already model their work as linked data and want answers that follow the links, such as which items relate to a given piece of work, rather than a keyword match over text. Check the repository's README for the exact tool list before you rely on it.

Routine is an all-in-one planner covering calendars, tasks and notes, with natural language scheduling and time management. Run it with mcpizy install routine or npx -y routine-mcp-server. It reads as a personal planner: closer to organizing your own week than to tracking a team's backlog, so pair it with a tracker like Jira or Dart rather than expecting it to replace one.

How do you pick the right one for your workflow?

Among project management MCP servers, the choice usually comes down to where your work already lives. Start from the tracker your team already uses: an agent is only as useful as the data behind it, and migrating a team to a new tool just to suit an agent rarely pays off. The table sets the six servers side by side, and the rules of thumb after it map each need to one of them.

• Engineering tickets and workflows: Jira.
• General work tracking shared across teams: Monday.com.
• A small team that wants AI planning and a published audit: Dart or Taskade.
• Structured product data with queries: Fibery.
• Personal scheduling: Routine, or Todoist for a plain task list.

If two options look close, a docs-first tool against a tracker is a common split, and Notion MCP vs Plane MCP for Project Tracking is a useful next read. Whatever you choose, install one server first, run it on a low-stakes project for a week, and only then add a second.

FAQ: what should you check before installing?

Do these servers cost anything? The MCP server packages for Dart and Taskade carry an MIT licence according to the CheckMCP audit, which means the code is free to use. The official pages do not state a price for the Monday.com, Jira, Fibery or Routine servers or for the tools behind them, and the accounts you connect to may have their own plans, so check each vendor before you rely on one for a team.

Which servers have a published audit? As of September 2026, the CheckMCP audit covers Dart (87/100, grade B) and Taskade (91/100, grade A) in this group. Monday.com, Jira, Fibery, Routine and Todoist have none published, so read their upstream documentation and review the repository yourself, following the audit guide linked above, before you connect them to live data.

Can I use more than one at a time? Yes. Each server installs on its own with mcpizy install and its name, and the command writes the configuration into your client automatically, so you can pair a tracker such as Jira with a planner such as Routine. Add them one at a time, so that if an agent behaves oddly you know which server's tools to review.