6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search projects, read your inbox, create tasks and bulk-update up to 20 work items.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Wrike MCP server connects your Wrike work-management account to Claude, ChatGPT and any MCP-compatible agent. It searches spaces and tasks, reads your inbox and comment threads, creates tasks and projects, posts comments with @-mentions, and edits up to twenty work items in a single call. Sign-in is OAuth on one scope: wsReadWrite. Read-only access is not offered.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.
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.
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.
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.
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.
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.
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.
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.
https://mcp.wrike.com/.well-known/oauth-protected-resource/app/mcp/stream (probed 2026-08-18) · retrieved 2026-08-18https://login.wrike.com/.well-known/oauth-authorization-server/oauth2 (probed 2026-08-18) · retrieved 2026-08-18developers.wrike.com/robots.txt allows /docs/; www.wrike.com/robots.txt carries Content-Signal: ai-train=no, search=yes, ai-input=yes — synthesis expressly permitted (fetched 2026-08-18) · retrieved 2026-08-18Connect Wrike once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.