Wrike MCP Server
Related Servers
Alternatives to Wrike MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceComplete Model Context Protocol server for ClickUp, enabling interaction with tasks, spaces, lists, docs, goals, time tracking, and more through 93 tools and 18 React MCP apps.-
- FlicenseNot gradedqualityDmaintenanceFull-featured MCP server integrating all 71 endpoints of the Weeek API as MCP tools for AI clients, enabling task, project, and workspace management via natural language.3-
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server providing 89 tools and 13 React UI apps for complete Zendesk Support API integration, enabling ticket, user, organization, and automation management.-
- FlicenseNot gradedqualityCmaintenanceComplete MCP server for Calendly API v2 with 40+ tools and 12 interactive React apps, enabling calendar management, scheduling, and user operations.-
- FlicenseCqualityDmaintenanceComprehensive MCP server for Mailchimp Marketing API v3.0 with over 104 tools and 15+ React UI apps, enabling management of campaigns, audiences, ecommerce, automations, reports, and more via natural language.1001-
- FlicenseNot gradedqualityDmaintenanceA modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.-
TDQS
Scored across 88 tools
Most tools follow a clear resource+action pattern, but there is some overlap between wrike_list_tasks and wrike_search_tasks, and between wrike_get_attachment, wrike_download_attachment, wrike_get_attachment_url, and wrike_get_attachment_preview, which could cause confusion about which tool to use.
All tools use the wrike_ prefix followed by a consistent verb_noun convention (e.g., list_tasks, get_task, create_comment, delete_folder). The naming pattern is highly predictable and uniform throughout, with no mixed styles or arbitrary verb choices.
With 88 tools, the server is significantly over-scoped, well beyond the typical 3-15 range. While it attempts to cover a wide API surface, the sheer number makes it unwieldy and increases cognitive load on agents, fitting the 'too many (25+)' descriptor.
The server covers a broad range of Wrike resources (tasks, folders, comments, approvals, contacts, custom fields, etc.) with full CRUD for most. However, notable gaps exist: there is no tool to upload/create an attachment, and workflows lack a delete operation, leaving some lifecycle coverage incomplete.