Appearance
MCP Ecosystem Landscape — Q2 2026
Executive Summary
The window has closed. The marketing strategy written in March 2026 claimed only 4 PM tools had MCP support (Linear, Shortcut, Plane, Kendo) with a ~12 month first-mover window. As of April 2026, at least 10 major project management tools have official or first-party MCP servers, including every tool in Kendo's competitive set. Jira, Asana, Monday.com, ClickUp, Notion, and GitHub all shipped MCP servers. Wrike and Teamwork have also entered. MCP has gone from niche differentiator to table stakes in under a year.
Kendo's MCP server (26 tools, 10 resources) is no longer rare — it's now a question of depth and developer-workflow fit rather than mere existence.
1. Who Has MCP Servers Now?
Tier 1: Official First-Party MCP Servers (Vendor-Built and Maintained)
| Tool | MCP Server | Tools | Transport | Status | Notes |
|---|---|---|---|---|---|
| Jira (Atlassian) | Atlassian Rovo MCP Server | ~46+ | Remote (Streamable HTTP) | GA | Covers Jira, Confluence, Compass, JSM, Teamwork Graph. OAuth 2.1. Hosted on Cloudflare. Anthropic was first official partner. |
| Linear | linear.app/docs/mcp | ~21 (expanded Feb 2026) | Remote + stdio | GA | Added initiatives, milestones, project updates in Feb 2026. Product management focus. |
| Asana | developers.asana.com/docs/mcp | ~30+ | Remote (Streamable HTTP v2) | GA | V2 launched Feb 2026. V1 (SSE) deprecated, shutting down May 2026. |
| Monday.com | monday.com/w/mcp | ~18 standard + dynamic API tools | Remote | GA | Available on all plans at no cost. Dynamic API Tools unlock full GraphQL surface. |
| ClickUp | developer.clickup.com/docs/mcp-tools | 20+ (official), 170+ (community) | Remote | Public Beta | Tasks, docs, time tracking, comments. No deletion tools (safety). All plans. |
| Notion | developers.notion.com/docs/mcp | ~18 | Remote (Streamable HTTP) | GA | Read/write. Search, content management, database queries. V2 with data sources. |
| GitHub | github.com/github/github-mcp-server | 51 | Remote + stdio | GA | 28k+ stars. Issues, PRs, Actions, Projects (consolidated toolset Jan 2026). |
| Shortcut | help.shortcut.com MCP Server | ~24 | Remote (OAuth) + stdio | GA | Stories, epics, iterations, objectives, docs. Read-only mode available. |
| Plane | developers.plane.so/dev-tools/mcp-server | 55+ | stdio, SSE, streamable HTTP | GA | Largest tool count in PM category. Issues, cycles, modules, work logs. Agent framework with @mention. |
| Wrike | developers.wrike.com/wrike-mcp | Unknown (full API coverage) | Remote | GA | Tasks, sprints, blockers, time entries. OAuth 2.0. Announced via press release. |
| Teamwork | PulseMCP listing | Unknown | Unknown | Available | Tickets, customers, companies. Less documented than others. |
| Todoist | PulseMCP listing | Unknown | stdio | Available | Task management via REST API. |
| Kendo | kendo.dev/docs | 26 tools, 10 resources | stdio | GA | Issues, sprints, time tracking, epics, GitHub sync. |
Tier 2: Community / Third-Party MCP Servers
| Tool | Source | Notes |
|---|---|---|
| Trello | Multiple community repos (delorenj/mcp-server-trello, etc.) | No official Atlassian Trello MCP, but community implementations exist. Board, list, card, label management. |
| Basecamp | BusyBee3333/basecamp-mcp-2026-complete | Community-built, claims 100+ tools. Not official. |
| Zoho Projects | PulseMCP listing | Community implementation. |
Summary
Of the 10 tools in Kendo's original competitive matrix, every single one now has MCP support — either official (Jira, Asana, Monday.com, ClickUp, Notion, GitHub, Linear, Shortcut, Plane) or community-built (Trello).
2. How Do They Compare to Kendo's 26 Tools + 10 Resources?
Tool Count Comparison
| Tool | Approx. Tool Count | Scope | Time Tracking via MCP | Resources/Prompts |
|---|---|---|---|---|
| Plane | 55+ | Issues, cycles, modules, work logs, agent framework | Yes (work logs) | Unknown |
| GitHub | 51 | Repos, issues, PRs, Actions, Projects, security | No | No |
| Atlassian (Jira) | 46+ | Jira, Confluence, Compass, JSM, Teamwork Graph | Via JSM/add-ons | Unknown |
| Asana | 30+ | Tasks, projects, portfolios, goals, custom fields | No | Unknown |
| Kendo | 26 tools + 10 resources | Issues, sprints, time tracking, epics, GitHub sync | Yes (native) | Yes (10 resources) |
| Shortcut | ~24 | Stories, epics, iterations, objectives, docs | No | Unknown |
| Linear | ~21 | Issues, projects, initiatives, milestones, comments | No | Unknown |
| ClickUp | 20+ (official) | Tasks, docs, time tracking, comments | Yes (timers + logs) | Unknown |
| Monday.com | ~18 + dynamic API | Boards, items, columns, groups, subitems | Via column values | Unknown |
| Notion | ~18 | Pages, databases, search, content management | No | Unknown |
| Wrike | Unknown | Tasks, sprints, blockers, time entries | Yes | Unknown |
Analysis
- Plane has overtaken everyone on raw tool count (55+), significantly exceeding Kendo's 26.
- Jira's scope is massive — 46+ tools spanning 5 Atlassian products. Enterprise AI integration.
- GitHub's 51 tools cover far more than project management (repos, PRs, Actions, security).
- Kendo's 26 tools + 10 resources is mid-pack on quantity, but still has a unique combination: native time tracking via MCP + resource endpoints for structured data access.
- ClickUp now has time tracking via MCP — timers, historical log entries, and fetching entries. This was previously listed as absent.
- Wrike also has time tracking via MCP — a new entrant with built-in time entries.
Where Kendo Still Has an Edge
- MCP resources — Most competitors expose only tools. Kendo's 10 resources provide structured read access (project overview, sprint status, etc.) that tools can consume for context. This is architecturally more sophisticated for agent workflows.
- Time tracking + sprints + AI in a single tool — While ClickUp and Wrike now have time tracking via MCP, Kendo bundles it at every tier without add-on pricing.
- Developer-workflow focus — Kendo's MCP server is designed for the Claude Code / Cursor terminal workflow, not for enterprise chatbot integrations. This is a positioning choice, not a feature gap.
- EU hosting + audit logging — None of these MCP servers change the data residency or compliance story.
Where Kendo Has Lost Ground
- Tool count — 26 tools is no longer impressive. Plane (55+), GitHub (51), and Jira (46+) all exceed it significantly.
- "One of only 4" — This claim is now false. At least 10 major tools have official MCP servers.
- First-mover window — The 12-month window did not materialize. It was more like 3-6 months before the wave hit.
3. Is the Window Closing?
The window is closed. Here's the timeline:
| Period | Event |
|---|---|
| Nov 2024 | MCP launched by Anthropic |
| Early 2025 | Linear, Shortcut, Plane ship MCP servers. Kendo ships MCP. |
| Jun 2025 | Atlassian Rovo MCP server goes GA (25 tools for Jira + Confluence) |
| Oct 2025 | GitHub MCP server adds Projects support |
| Late 2025 | OpenAI, Google, Microsoft all adopt MCP. SDK downloads hit 68M/month. |
| Dec 2025 | MCP donated to Agentic AI Foundation (Linux Foundation). Becomes vendor-neutral standard. |
| Jan 2026 | GitHub MCP server expands Projects tools + OAuth scope filtering |
| Feb 2026 | Asana ships MCP V2. Linear expands to product management (initiatives, milestones). Monday.com MCP goes GA. |
| Early 2026 | ClickUp MCP enters public beta. Wrike announces MCP server. Notion MCP GA. |
| Mar 2026 | SDK downloads reach 97M/month. 17K+ MCP servers indexed across registries. |
| Apr 2026 | Atlassian expands to 46+ tools across 5 products. |
The acceleration was faster than predicted. The marketing strategy estimated a 12-month window. In reality:
- The major enterprise players (Jira, Asana, Monday.com, ClickUp) all shipped within 6-9 months of the early movers.
- The MCP donation to the Linux Foundation in Dec 2025 removed the "Anthropic-only" perception and accelerated enterprise adoption.
- OpenAI, Google, and Microsoft all backing MCP made it an industry standard, not a niche protocol.
4. MCP Ecosystem Growth
Scale
| Metric | Value | Date |
|---|---|---|
| Monthly SDK downloads | 97M | Mar 2026 |
| MCP servers in public registries | 17,000+ | Q1 2026 |
| PulseMCP directory | 11,170+ servers | Apr 2026 |
| GitHub MCP server stars | 28,300+ | Apr 2026 |
| Major vendor backing | Anthropic, OpenAI, Google, Microsoft, AWS | Nov 2025 |
| Governance | Agentic AI Foundation (Linux Foundation) | Dec 2025 |
Growth Trajectory
- Nov 2024: ~100K monthly SDK downloads at launch
- Apr 2025: 22M downloads/month (after OpenAI adoption)
- Jul 2025: 45M downloads/month (Microsoft integration)
- Nov 2025: 68M downloads/month (AWS Bedrock support)
- Mar 2026: 97M downloads/month
For comparison: the React npm package took ~3 years to reach 100M monthly downloads. MCP achieved comparable scale in 16 months.
Protocol Evolution
- Streamable HTTP is now the preferred transport (replacing SSE). Asana, Atlassian, and others have migrated.
- OAuth 2.1 is becoming the standard auth method for remote MCP servers.
- Remote MCP servers (hosted, no local install) are up 4x since May 2025.
- The 2026 MCP Roadmap focuses on enterprise-readiness: token management, access control, response filtering.
5. Discrepancies with Existing Kendo Documents
shared/competitors.md
| Claim | Reality | Severity |
|---|---|---|
| Jira listed as "MCP Support: No" | Atlassian has an official Rovo MCP Server with 46+ tools, GA since mid-2025 | Critical |
| Asana listed as "MCP Support: No" | Asana has an official MCP V2 server (30+ tools), GA | Critical |
| Monday.com listed as "MCP Support: No" | Monday.com has an official MCP server, available on all plans | Critical |
| ClickUp listed as "MCP Support: No" | ClickUp has an official MCP server in public beta | High |
| Notion listed as "MCP Support: No" | Notion has an official MCP server, GA | High |
| GitHub Projects listed as "MCP Support: No" | GitHub MCP server has 51 tools including Projects support | High |
| Trello listed as "MCP Support: No" | Community-built MCP servers exist (not official) | Low |
company/marketing-strategy.md
| Claim | Reality | Severity |
|---|---|---|
| "Only 4 PM tools support MCP" (S2, O1) | At least 10 major PM tools have official MCP servers | Critical — remove this claim immediately |
| "First-mover advantage window is ~12 months" (O1) | Window was ~3-6 months. It's closed. | Critical — requires strategy revision |
| "MCP support is rare" (Key Takeaways) | MCP support is now ubiquitous among PM tools | Critical |
| Linear "MCP but limited" (Feature Messaging Matrix) | Linear has 21+ tools with initiatives and milestones | High — understates competitor |
| Competitive table shows only Linear, Shortcut, Plane with MCP | All 10 competitors now have MCP | Critical — table is outdated |
6. Strategic Implications
What This Means for Kendo
"We have MCP" is no longer a differentiator. Everyone has MCP. The messaging must shift from "we have it, they don't" to "ours is built for developer terminal workflows."
Depth over existence. The new competitive question is: How deep is your MCP integration? Kendo's 10 resources (structured context endpoints) are still unusual — most competitors only expose tools. This is a technical nuance worth emphasizing.
The combination is the moat, not MCP alone. MCP + native time tracking + EU hosting + audit logging + developer focus — the bundle still differentiates. No single competitor matches all five.
Tool count gap. Plane (55+), GitHub (51), and Jira (46+) all exceed Kendo's 26 tools significantly. Consider whether expanding Kendo's MCP tool surface is a priority.
Messaging overhaul needed. Every instance of "only 4 tools" and "12-month window" must be removed from marketing materials, landing pages, and strategy documents before public launch.
Recommended Messaging Pivot
Before (March 2026): "One of only 4 PM tools with MCP support."
After: "The deepest MCP integration for developer workflows — 26 tools, 10 resources, and native time tracking. No add-ons, no enterprise tier required."
The emphasis shifts from scarcity to quality: structured resources for agent context, terminal-native design, and a bundle that competitors gate behind higher tiers or add-ons.
7. Open Questions for Future Research
- What do competitors' MCP resources look like? Kendo has 10 resources — do any competitors expose MCP resources (not just tools)? This could be a genuine remaining differentiator.
- MCP usage analytics. How many developers are actually using MCP servers for PM tools vs. just having them available? Adoption != usage.
- Pricing impact. Several competitors (Monday.com, ClickUp) offer MCP on all plans. Does this change the willingness to pay for Kendo's MCP?
- Agent framework patterns. Plane has an agent framework with @mention and Agent Run lifecycle. Is this the next competitive frontier after basic MCP support?
- MCP auth standardization. OAuth 2.1 and streamable HTTP are becoming standard. Does Kendo's stdio-only transport become a limitation for remote/hosted use cases?
[Librarian] Research conducted 2026-04-04. All tool counts are approximate and based on public documentation and registry listings as of the research date. Exact counts change frequently as vendors update their MCP servers.
Related
- ai-native-dev-tools-landscape-2026.md — Broader AI-native positioning context
- mcp-apps-kendo-pilot.md — Follow-up on the next MCP ecosystem shift: MCP Apps (SEP-1865, GA 2026-01-26) — interactive UI widgets rendered inside Claude Desktop. Asana, Monday.com, Canva, Figma, Box, and Slack were launch partners. Kendo pilot scoped at 3-5 days.
- ../shared/competitors.md — Competitive landscape updated from these findings
- ../company/marketing-strategy.md — Go-to-market strategy updated with MCP reality check