Wrike MCP. Audit every task, project, and department status.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Wrike MCP manages your entire project lifecycle by connecting any AI client directly to your work management data. You can list all projects, browse folder structures, monitor task statuses across departments, and find contact IDs instantly.
It's an operational layer for auditing complex workflows in Wrike.
What your AI agents can do
Get task details
Retrieves full information on a single specified task.
List wrike contacts
Lists every user and contact in the Wrike workspace, useful for finding correct assignee IDs.
List wrike folders
Shows a directory of all folders and projects within your account structure.
Retrieves a directory of every available space and department within the Wrike workspace.
Generates a list of all users and contacts in your account, giving you IDs needed for task assignment.
Lists every active top-level container or major initiative running within Wrike.
Lists all individual tasks, optionally scoping the search to a specific folder for focused results.
Pulls deep details on one task, including descriptions, who owns it, and any custom fields used.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Wrike: Project & Task Operations (6 Tools)
Manage every detail of your work structure, from listing spaces to retrieving granular information on single tasks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Wrike on Vinkius019d7625get task details
Retrieves full information on a single specified task.
019d7625list wrike contacts
Lists every user and contact in the Wrike workspace, useful for finding correct assignee IDs.
019d7625list wrike folders
Shows a directory of all folders and projects within your account structure.
019d7625list wrike projects
Provides a list of every active, top-level project container in the workspace.
019d7625list wrike spaces
Lists all major work areas (spaces) used by different departments or functions.
019d7625list wrike tasks
Finds and lists tasks across the account, allowing you to narrow the search down by folder ID.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Wrike, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Wrike. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Tracking Project Status Without Endless Clicks
Today, checking project status means navigating through a maze of folders. You click on the 'Marketing' space, then find the 'Q3 Launch' folder, and finally drill down to the task list. If you need to check three different departments, that’s three separate sessions, copying IDs and manually compiling a spreadsheet.
With this MCP, your agent does the clicking for you. Instead of manual navigation, you ask it to map out the entire organization using `list_wrike_spaces` or find tasks across multiple areas by running `list_wrike_tasks`. You get one clean report that shows exactly where everything is and who owns it.
Wrike MCP: Get Every Project Detail, Effortlessly
The manual steps of checking task ownership, verifying folder IDs for automation builds, or confirming a project's top-level status are now single commands. You don't manually look up team member IDs; you just ask the agent to run `list_wrike_contacts`.
What changes is that your AI client stops being a glorified search bar and starts acting like an internal process auditor. It gives you complete visibility into every aspect of your project, all from one chat window.
What you can do with this MCP connector
Forget manually digging through nested folders or switching between different project views just to check a status update. This MCP lets your AI agent act as your dedicated Wrike operations assistant.
Instead of writing multi-step reports, you simply tell your agent what data you need—like 'Give me all tasks assigned to John in the Marketing space that are due next week.' The system gathers and presents it instantly, giving you a single source of truth for your entire workspace. You can get project status by listing active projects or audit who is working on what by checking folder hierarchies.
And when Wrike needs to talk to another system—say, sending an alert about a completed task to Slack or creating a record in a CRM—you don't have to copy data manually. Because this MCP runs on Vinkius, your agent can combine Wrike data with other services to build automations that span multiple platforms through one connected process.
019d7625-4acb-7298-a515-f730bccb67db 
How Wrike MCP Works
- 1 Subscribe to this MCP and provide your Wrike Access Token.
- 2 Connect the service to your preferred AI client (Claude, Cursor, etc.).
- 3 Tell your agent what you need—for instance, 'List all projects in the Finance department'. The system handles the rest.
The bottom line is that your agent talks directly to Wrike's data layer without you ever needing to touch a URL or navigate a single menu item.
Who Is Wrike MCP For?
Anyone who manages complex projects and spends too much time cross-referencing statuses between different departments. This is for the operations manager who needs an immediate, comprehensive audit of project health.
Needs to monitor task progress across multiple initiatives without manually checking each folder's contents.
Must audit the entire organizational structure, verifying that tasks are assigned correctly and folders haven't been left unmanaged.
Needs to quickly surface task details or project statuses for board reports, without deep knowledge of Wrike’s internal navigation.
What Changes When You Connect
- Stop guessing who owns what. Use
list_wrike_contactsto get all team member IDs instantly for accurate assignment tracking. - Don't navigate deep folder trees. Your agent can use
list_wrike_spacesorlist_wrike_foldersto map out the entire organizational structure quickly. - Need status checks? Instead of opening ten tabs, ask your agent to run
list_wrike_projectsand get an aggregated overview of all major initiatives. - Get surgical detail on one item. Use
get_task_detailswhen you need specific metadata—like priority or custom field values—for reporting. - Automate across platforms. By connecting Wrike data through Vinkius, your agent can build a process that pulls project info from here and posts it to another system.
- Pinpoint tasks fast. Use
list_wrike_taskswhen you know the general area but need to scope down results by folder ID.
Real-World Use Cases
The Project Health Check
An Operations Director needs a quarterly audit of project completion. They ask their agent to run list_wrike_projects and then pull status reports for every single active container, bypassing manual report generation.
Finding the Right Team Member
A Project Manager needs to assign a task but doesn't know the ID of the new hire. The agent runs list_wrike_contacts and provides the exact IDs needed for assignment, saving minutes of directory searching.
The Deep Dive Task Audit
An EA needs to confirm if a task has all necessary documentation attached before a meeting. The agent uses list_wrike_tasks and then calls get_task_details to verify custom fields.
Mapping Departmental Scope
A new team lead needs to understand the boundaries of their work area. They ask the agent to run list_wrike_spaces and review the resulting hierarchy, understanding where their tasks live relative to other departments.
The Tradeoffs
Listing everything first
Asking the agent: 'Show me projects, spaces, folders, tasks, and contacts.' The resulting data dump is useless because you don't know which list to trust.
→
Start specific. If you need task details for a project, run list_wrike_projects first to identify the container ID, then use that ID when listing tasks via list_wrike_tasks.
Assuming all data is visible
Trying to get details about a task without knowing its exact location or metadata. The agent will fail because the context is missing.
→
If you are checking an old task, first use list_wrike_folders to narrow down the search path, then call get_task_details with the precise ID.
Manually searching for people
Spending ten minutes in Wrike's user directory just to find a team member’s unique ID for an automation script.
→
Use list_wrike_contacts once at the start of your session. This gives you a comprehensive list of IDs that can be referenced immediately.
When It Fits, When It Doesn't
Use this MCP if your workflow requires auditing, reporting, or cross-referencing structured data within Wrike's hierarchy—specifically when you need to map out projects, folders, people, and tasks. You should use it anytime you are moving from 'What is the status?' to 'Show me why the status is what it is.' Don't use this if your only goal is simple messaging or sharing a document link; for those, a dedicated communication MCP works better. If you only need basic project listing and don't care about the underlying folder structure or task metadata, list_wrike_projects alone might suffice, but connecting to all tools gives you full audit capability.
Common Questions About Wrike MCP
How do I check the status of all my Wrike projects using list_wrike_projects? +
Run list_wrike_projects and specify which criteria you want to see. This tool pulls a list of every top-level container, allowing you to monitor them all at once.
What is the difference between listing folders and listing spaces in Wrike? +
Spaces are the high-level departmental containers, while folders are sub-structures within those spaces. Use list_wrike_spaces to see departments, then use list_wrike_folders for granular grouping.
Can I get full metadata using get_task_details? +
Yes. If you provide a task ID, the agent uses get_task_details to retrieve deep information like custom field values and priority levels beyond just the title.
How do I find all team members for assignment? Should I use list_wrike_contacts? +
You should use list_wrike_contacts. This tool generates a clean, comprehensive roster of every user ID in the workspace, making task assignment simple.
When I use `list_wrike_contacts`, how does the MCP handle my Wrike access token? +
The MCP uses a zero-trust proxy for your credentials. They pass through but are never stored locally on disk. This means your keys stay secure while your agent performs actions like listing contacts or accessing any other data.
After running `list_wrike_folders`, how can I use the resulting folder IDs for automation? +
You must pass the specific ID into subsequent calls. For example, when using list_wrike_tasks, supplying a folder ID ensures the task list is scoped only to that container, making your workflows precise.
To improve speed and limit results, should I always filter when using `list_wrike_tasks`? +
Yes, filtering is highly recommended for performance. Always provide a folder ID if you know the scope; this cuts down on data transfer and speeds up agent responses significantly.
Beyond basic assignment status, what kind of specific information can I get using `get_task_details`? +
You retrieve comprehensive metadata that goes far beyond just the task's current status. This includes custom field values and detailed descriptions, helping you understand exactly why a task might be blocked or stalled.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.