Wrike MCP. Manage project structure and task data via chat.
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 Server connects your AI agent directly to your Wrike account data. It lets you list and browse tasks, projects, spaces, and team contacts using natural conversation.
You can retrieve detailed task metadata or map out complex folder hierarchies without ever leaving the chat window.
What your AI agents can do
Get task details
Retrieves all the metadata—status, assignee, description, and custom fields—for one specific Wrike task.
List wrike contacts
Lists every user and contact in your Wrike workspace so you can find IDs for assignments.
List wrike folders
Displays the full list of folders and projects, allowing you to see how tasks are organized within the account structure.
List every contact in your Wrike workspace to find IDs for task assignments.
See a list of all available spaces, helping you narrow down which department or function owns the project.
List all top-level projects in your account without knowing their exact folder path.
Retrieve tasks from the entire Wrike account, with an option to filter results based on a specific folder ID.
Pull comprehensive metadata for any single task, including its assignee, status, and custom field values.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Wrike MCP Server: 6 Tools for Project Ops
These six tools let your AI client pull specific data—from user IDs to deep task metadata—directly from your Wrike workspace.
019d7625get task details
Retrieves all the metadata—status, assignee, description, and custom fields—for one specific Wrike task.
019d7625list wrike contacts
Lists every user and contact in your Wrike workspace so you can find IDs for assignments.
019d7625list wrike folders
Displays the full list of folders and projects, allowing you to see how tasks are organized within the account structure.
019d7625list wrike projects
Lists all top-level active projects in your Wrike workspace.
019d7625list wrike spaces
Shows all available work areas (Spaces) that exist for the authenticated user's team or department.
019d7625list wrike tasks
Lists tasks in your Wrike account; you can optionally narrow the search by providing a 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,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
Listen up. This Wrike MCP Server connects your AI agent straight into your work data. You won't waste time clicking through dashboards or digging through menus; you just talk to it, and your agent pulls out exactly what you need. It gives you total visibility across tasks, projects, people, and the whole damn folder structure.
Finding People:
When you need to assign a task, you gotta know who's who. Use list_wrike_contacts to pull every user and contact in your entire Wrike workspace. This gives you all the necessary IDs so you can tell your agent exactly who needs to get it done.
Mapping Your Scope:
You need to figure out where a project lives before you even look for tasks. Start with list_wrike_spaces to see every available work area—the departmental buckets your team uses. Next, use list_wrike_projects to pull all the top-level projects running in your account. If that's still too broad, run list_wrike_folders.
This tool displays a complete list of folders and projects, showing you the deep hierarchy of how everything is organized inside Wrike.
Browsing Tasks:
To see what work is happening, you use two tools. First, list_wrike_tasks lets your agent pull task lists across your whole account; you can narrow that search down by giving it a specific folder ID to focus the results. If you need more than just a status update—if you want the full scoop on one item—you run get_task_details.
This retrieves all the metadata for any single Wrike task, giving you its assignee, its current status, the detailed description, and values from custom fields. It's comprehensive.
This setup means your AI agent handles all the API calls in the background. You just talk to it through your preferred client, and it structures the data about tasks and projects straight into the chat window for you. You don't have to leave the conversation to manage complex enterprise workflows; you just ask, and it gets it done.
How Wrike MCP Works
- 1 Subscribe to the server and provide your Wrike Access Token.
- 2 Your AI client uses the token to make structured calls (e.g., asking for a list of projects).
- 3 The agent returns clean, plain text results—the data you need—right back into the chat interface.
The bottom line is: your AI agent acts as an internal operations assistant that speaks Wrike's API language and translates it to simple conversation.
Who Is Wrike MCP For?
Project Managers who are tired of manually checking 15 different project dashboards. Operations Engineers who need to audit folder structures across multiple departments. Executive Assistants who have to gather status updates from disparate sources before a meeting. This is for anyone whose job requires knowing 'where' something is in the Wrike system.
Uses list_wrike_projects and get_task_details to audit project health, checking task assignments and status without clicking into every folder.
Runs queries using list_wrike_folders or list_wrike_spaces to verify the entire organizational structure and ensure compliance across departments.
Uses list_wrike_contacts to find specific team member IDs and then uses those IDs with task listing tools to quickly surface status reports for meetings.
What Changes When You Connect
- Stop manually clicking through folders. Using
list_wrike_folderslets you audit the entire organizational hierarchy in one request. - Get deep context on individual tasks instantly. The
get_task_detailstool pulls every custom field and status update without opening a single task card. - Find people immediately. Running
list_wrike_contactsgives you all user IDs upfront, so you don't have to guess who owns which project component. - Map your entire team structure by listing spaces using
list_wrike_spaces. This is how you understand departmental boundaries before planning a cross-functional task. - Audit project scope. Combining
list_wrike_projectsand then runninglist_wrike_taskslets you see everything active across the whole account in two steps.
Real-World Use Cases
Checking on a stalled campaign
A marketing lead needs to know if 'Q3 Assets' is moving forward. Instead of going into the folder, they ask their agent: "What tasks are in the 'Q3 Assets' project?" The agent runs list_wrike_tasks and provides a clean list with status updates.
Verifying ownership for a new hire
An Ops Manager needs to assign onboarding tasks but doesn't know the assignee's ID. They run list_wrike_contacts. The agent returns a clean list of names and IDs, allowing the manager to accurately assign work using the found IDs.
Understanding project dependencies
A PM needs to know which projects are related to 'Mobile App Redesign.' They ask their agent to run list_wrike_spaces, identifying all relevant department spaces, and then use that scope with list_wrike_projects.
Preparing for a status meeting
An Executive Assistant needs quick updates on five different tasks assigned to one person. They ask the agent to run get_task_details multiple times, compiling all necessary metadata into a single, readable summary.
The Tradeoffs
Searching for user IDs manually
Trying to find a colleague's ID by guessing or asking them directly. This wastes time and requires multiple back-and-forth messages.
→
Run list_wrike_contacts. The agent immediately lists every contact in the workspace, giving you all the IDs upfront so you can assign tasks right away.
Trying to find a project list from an external source
Copying a screenshot of a folder structure and asking your AI client about it. The agent has no way to validate that data against the live system.
→
You must use list_wrike_projects or list_wrike_folders. These tools pull the actual, current structure directly from Wrike's database.
Forgetting to scope a task list
Asking for 'all tasks' without knowing which project they belong to. The resulting data dump is too large and requires manual filtering.
→
Use list_wrike_tasks and provide the specific folder_id. This limits the output immediately, giving you only the relevant items.
When It Fits, When It Doesn't
Use this server if your primary goal is reading structured data: listing projects, checking task status, or mapping out user/folder hierarchies. If you need to write data—like changing a task's assignee, setting a due date, or creating a new folder—this tool set won't work. You'll need an integration that supports write operations. This server is purely for reading and retrieving metadata. It’s the perfect read-only layer for any AI client building internal reports.
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.
Available Capabilities
Tracking project status means clicking through endless dashboards.
Today, checking on a complex project requires navigating deep into Wrike's folders. You open the main project view, filter by owner, then click into sub-folders to see task lists, and finally drill down to check individual tasks just for status updates. It’s slow, it involves five different clicks, and you lose context every time.
With this MCP server, your AI agent does the work of clicking. You tell it, "List all active tasks in the 'Product Launch' project." The agent runs `list_wrike_tasks`, pulls the status for each one, and hands you a clean, organized list right away. No clicks needed.
Wrike MCP Server: Task & Project Ops
Before this server, if you needed to assign work or even just check who was supposed to do it, you had to manually find the person's ID inside Wrike. It's a tedious lookup process that breaks your flow.
Now, you run `list_wrike_contacts`. The agent gives you every user and their IDs in plain text. You get all the raw data required for assignment or reporting instantly.
Common Questions About Wrike MCP
How do I use list_wrike_tasks to check tasks? +
You must run list_wrike_tasks and, if possible, provide the specific folder ID. This keeps the results focused on one area of your project instead of dumping everything across the entire account.
Can I use list_wrike_contacts to find a user's current projects? +
No. list_wrike_contacts only provides names and IDs for users. To see their projects, you first need the project ID from list_wrike_projects, then pass that scope to your task listing tools.
Does get_task_details provide enough information? +
Yes, it pulls comprehensive metadata. You'll get descriptions, assignees, status, and all custom field values in one go, so you don't have to run multiple checks.
What if I need to see every single project? Which tool should I use? +
Use list_wrike_projects. This is the dedicated function for listing all top-level containers. If you want even more detail on organization, check out list_wrike_folders.
Is this server good for writing new tasks? +
No. The Wrike MCP Server is read-only. It's designed to pull and display information—it cannot create, edit, or change any data in your actual Wrike account.
When I use list_wrike_folders, does it show every folder in the account, or only those visible within a specific space? +
It lists all folders you have access to. The AI agent handles the scope context; if you reference a Space ID first, the subsequent calls to list_wrike_folders will be restricted to that area.
After running list_wrike_spaces, how do I efficiently find all the associated projects and folders using list_wrike_folders? +
The process is sequential. You get the Space ID from the first tool call. Then, you pass that context to the agent so it can correctly filter and execute list_wrike_folders for only the necessary containers.
What happens if I run get_task_details but provide an incorrect or non-existent task ID? +
The agent will immediately report the specific API error code and message. This tells you instantly whether the failure was due to a missing resource, insufficient permissions, or another connection issue.
Can I check the details of a specific task through the agent? +
Yes. The get_task_details tool allows your AI agent to retrieve full metadata for any specific task ID, including its description, current status, assignees, and any custom fields you have configured.
How do I find tasks belonging to a specific folder or project? +
You can use the list_wrike_tasks tool and provide the unique folder_id. Your agent will return all tasks contained within that specific organizational unit, helping you stay focused on a specific project.
Is it possible to see all my team members' contact IDs via chat? +
Absolutely. The list_wrike_contacts tool retrieves all users and contacts in your Wrike workspace, providing their names and unique contact IDs required for task assignment or mentions.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Google Chat Webhook Notifier
This MCP does exactly one thing: it sends messages to your Google Chat spaces. That's its only function, and nothing else. Incredible for giving your AI agents a voice.
People Management Prover
A hiring plan listed 'culture fit' as the primary criterion. That's not a criterion — that's a bias proxy. People Management Prover forces job-related criteria, adverse impact analysis, and validated assessment methods grounded in I-O psychology.
AntEater
Monitor website changes, detect content updates, and receive alerts when key pages are modified across your digital properties.
You might also like
Placetel
Manage Placetel users, devices, numbers, and calls.
Fuzzy String Distance Engine
Calculate exact Levenshtein, Jaro-Winkler, and Dice distances for fuzzy text matching natively local.
Billsby
Manage subscription billing via Billsby — list customers, subscriptions, and invoices directly from any AI agent.