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.

Wrike MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: Wrike
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to Wrike through Vinkius, pass the Edge URL in the `mcps` parameter and every Wrike tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Wrike Specialist",
    goal="Help users interact with Wrike effectively",
    backstory=(
        "You are an expert at leveraging Wrike tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Wrike "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Wrike MCP Server

Connect your Wrike account to any AI agent and manage your enterprise workflows through natural conversation.

When paired with CrewAI, Wrike becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Wrike tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Task Monitoring — List and browse tasks across your entire account or filter by specific folder/project IDs
Deep Task Analysis — Retrieve comprehensive metadata for specific tasks, including descriptions, assignees, and custom fields
Project Navigation — Browse top-level project containers and monitor their current status and organization
Folder Hierarchy — Explore your organizational structure to understand how tasks are grouped and categorized
Team Discovery — List all users and contacts within your Wrike workspace to find IDs for task assignment
Space Access — List all available work areas (spaces) to navigate your team's different departments or functions
Workflow Automation — Quickly find unique task and folder IDs required for building automated project management flows

The Wrike MCP Server exposes 6 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Wrike to CrewAI via MCP

Follow these steps to integrate the Wrike MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 6 tools from Wrike

Why Use CrewAI with the Wrike MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Wrike through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Wrike + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Wrike MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Wrike for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Wrike, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Wrike tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Wrike against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Wrike MCP Tools for CrewAI (6)

These 6 tools become available when you connect Wrike to CrewAI via MCP:

get_task_details

Retrieves comprehensive details for a specific Wrike task

list_wrike_contacts

Lists all users and contacts within the Wrike workspace

list_wrike_folders

Lists all folders and projects in the Wrike account

list_wrike_projects

Lists all active projects in the account

list_wrike_spaces

Lists all Wrike spaces available to the authenticated user

list_wrike_tasks

You can optionally provide a folder_id to scope the results. Lists tasks in the Wrike account, optionally filtered by folder

Example Prompts for Wrike in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Wrike immediately.

"List all my Wrike projects."

"Show me tasks in the 'Product Launch 2026' folder."

"Get full details for task ID 'IEA...'."

Troubleshooting Wrike MCP Server with CrewAI

Common issues when connecting Wrike to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Wrike + CrewAI FAQ

Common questions about integrating Wrike MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.