Wrike
by Wrike
Search projects, read your inbox, create tasks and bulk-update up to 20 work items from your AI assistant. OAuth sign-in on a single read-write scope, and a directory listing that still points at v1.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Wrike via MCP
https://mcp.wrike.com/app/mcp/streamWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Wrike Tools & Capabilities (18)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Is the Wrike MCP connector read-only?
No. Anthropic's directory records permissions as Read and write, and Wrike's own tool documentation counts four write tools against thirteen read tools. The writes create tasks, create projects and folders, post comments, and edit existing items in bulk. Every change runs under your own Wrike permissions, so the connector cannot exceed what you could already do manually.
How many Wrike tasks can the connector change in one call?
Up to twenty. Wrike's tool documentation states that update_items applies the same change to as many as twenty items at once, covering title, description, status, dates, custom fields, assignees and parent items. That cap bounds a single call, not a conversation, so an assistant can still issue several calls in sequence to cover a larger set.
Will teammates get notified when an AI assistant updates my Wrike tasks?
Assume yes. Wrike's MCP documentation does not describe any silent write mode, and the same docs describe get_my_inbox as returning mentions, assignments, status changes and replies. Those are precisely the events a write produces, so an assistant reassigning work or posting a comment reaches colleagues through Wrike's normal notification paths.
What OAuth permissions does the Wrike MCP server request?
One scope: wsReadWrite. The server's RFC 9728 descriptor and Wrike's authorization server metadata both list wsReadWrite as the only supported scope, checked live on 2026-08-18. Wrike's REST API documents a narrower wsReadOnly scope for other integrations, but the MCP server does not advertise it, so a read-only connection is not offered.
Why does the connector show old Wrike tools after an update?
Your AI client cached the tool list. Wrike's documentation explains that the server exposes a fixed tool set and that clients store it on first connection, so a client keeps showing the previous list until refreshed. Wrike publishes a per-client refresh table; in Claude the fix is disconnecting and reconnecting the connector in Settings.
Which Wrike MCP endpoint should I use?
Use https://mcp.wrike.com/v2 for a custom connector. Wrike's documentation states that the older /app/mcp/stream and /app/mcp/sse URLs serve MCP v1 and do not carry the v2 tool set. Anthropic's directory still records the v1 stream URL for this listing, and Wrike says directory-installed connectors move to v2 automatically as each marketplace clears review.
Can I use the Wrike MCP server without OAuth?
Yes, with a Permanent Access Token. Wrike documents this as the alternative for automated workflows and clients that cannot complete the OAuth flow, including clients configured through mcp-remote that require Dynamic Client Registration. You generate the token under Apps & Integrations, and Wrike warns that it inherits all of your permissions and should be treated like a password.
Who sets up the Wrike connector, an admin or each user?
Both, in that order. Wrike's setup guide has an administrator create one OAuth app under Apps & Integrations per organization and register the connector with its client ID, secret and redirect URL. Individual users then connect with their own Wrike credentials, and their personal workspace permissions apply to everything the assistant does.
Sources
- Wrike MCP Server Overview — https://developers.wrike.com/docs/wrike-mcp-server-overview (fetched 2026-08-18) · retrieved 2026-08-18
- Available tools on Wrike MCP — https://developers.wrike.com/docs/available-tools-on-wrike-mcp (fetched 2026-08-18) · retrieved 2026-08-18
- Typical Use Cases of Wrike MCP — https://developers.wrike.com/docs/typical-use-cases-of-wrike-mcp (fetched 2026-08-18) · retrieved 2026-08-18
- Setup Claude with Wrike MCP — https://developers.wrike.com/docs/setup-claude-with-wrike-mcp (fetched 2026-08-18) · retrieved 2026-08-18
- Setup other MCP clients with Wrike MCP — https://developers.wrike.com/docs/setup-other-mcp-clients-with-wrike-mcp (fetched 2026-08-18) · retrieved 2026-08-18
- Legacy Authentication: Permanent Access Token — https://developers.wrike.com/docs/mcp-legacy-authentication-pat (fetched 2026-08-18) · retrieved 2026-08-18
- Wrike OAuth 2.0 Authorization reference — https://developers.wrike.com/docs/oauth-20-authorization (fetched 2026-08-18) · retrieved 2026-08-18
- Live RFC 9728 protected-resource descriptor —
https://mcp.wrike.com/.well-known/oauth-protected-resource/app/mcp/stream(probed 2026-08-18) · retrieved 2026-08-18 - Live RFC 8414 authorization-server metadata —
https://login.wrike.com/.well-known/oauth-authorization-server/oauth2(probed 2026-08-18) · retrieved 2026-08-18 - Live unauthenticated probe of both endpoints, HTTP 401 — 2026-08-18 · retrieved 2026-08-18
- Anthropic connector directory — https://claude.ai/directory/baa35676-3f79-4728-aec9-b37870c73deb (snapshot 2026-08-16) · retrieved 2026-08-16
developers.wrike.com/robots.txtallows/docs/;www.wrike.com/robots.txtcarriesContent-Signal: ai-train=no, search=yes, ai-input=yes— synthesis expressly permitted (fetched 2026-08-18) · retrieved 2026-08-18
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Wrike
- Tools
- 18
- Domain
- mcp.wrike.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.