Bring Enterprise Collaboration
to Claude Code
Learn how to connect Wrike to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Wrike MCP Server?
Connect your Wrike account to any AI agent to automate your complex project management workflows through natural conversation. Wrike provides a robust environment for enterprise-scale collaboration, task tracking, and resource management.
What you can do
- Project Lifecycle — List, create, and update tasks with granular control over importance levels, statuses, and custom metadata.
- Hierarchical Organization — Navigate and manage the work using a structured system of folders and projects for different departments or clients.
- Team Collaboration — Retrieve discussion threads and post comments directly to task feeds to keep your team aligned programmatically.
- Workspace Monitoring — List contacts, track custom workflows, and manage task attachments to maintain a clear overview of operational progress.
- Operational Efficiency — Automate task assignments and progress tracking to reduce manual coordination effort.
How it works
1. Subscribe to this server
2. Enter your Wrike Permanent Token from your account settings
3. Start managing your enterprise projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — automate the coordination of large-scale projects and team assignments via natural language.
- Team Leads — monitor progress across multiple folders and projects without switching applications.
- Operations Teams — streamline task tracking and ensure all organizational workflows are following standard procedures.
Built-in capabilities (12)
Post comment to task
Add new folder/project
Add new task
Get full task info
Get current user
List task workflows
List hierarchy
List task files
Get task discussion
Can filter by status (Active, Completed, Deferred, Cancelled). List project tasks
List workspace users
Modify task info
Why Claude Code?
Claude Code registers Wrike as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Wrike data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Wrike tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Wrike in Claude Code
Wrike and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Wrike to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Wrike in Claude Code
The Wrike MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Wrike for Claude Code
Every tool call from Claude Code to the Wrike MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is the difference between Folders and Projects in Wrike?
In Wrike, a Project is technically a Folder with added metadata such as owners, start/end dates, and project-specific statuses to help track deadlines and responsibility.
Can I move a task to a different project via AI?
Yes, you can use the update_task tool and provide the addParents or removeParents parameters in the attributes to change which project or folder the task belongs to.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable