Wrike MCP Server
Connect Wrike to your AI agents with the Wrike MCP server.
Updated
What is Wrike MCP?
The Wrike MCP server is a Model Context Protocol server that connects Wrike to AI agents and assistants as a set of tools. With it connected, an agent can work with Wrike (project management — tasks, folders, projects, and team workflows) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses a bearer token, so you point your client at the server URL, authorize once, and the Wrike tools become available to the model.
Connect the Wrike MCP server
Connect Wrike MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Wrike MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (a bearer token) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Wrike tool to confirm the connection is live.
Connect Wrike MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Wrike
Provide the Wrike MCP server URL or command and complete authentication.
- 3
Test
Reference Wrike from chat to confirm Cursor can reach the tools.
Using Wrike MCP with Gamut
On Gamut, the Wrike MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Wrike and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Wrike MCP server?
It is a Model Context Protocol server that exposes Wrike to AI agents as tools so they can work with it (project management — tasks, folders, projects, and team workflows).
How do I connect the Wrike MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Wrike MCP server URL and complete authentication (a bearer token). See the official documentation for the exact URL and scopes.
Can I use Wrike MCP with Gamut?
Yes — Gamut supports the Wrike MCP server, so your agents can use it as a tool in automated, triggered workflows.