How to Use the Wrike MCP in LangChain

Q: What is the best way to audit task history with LangChain and Wrike?

You should chain together listtasks followed by gettaskdetails. This sequence allows your agent to pull a list of tasks, then dive deep into the specific context of each one sequentially.

Build complex, multi-step task workflows with LangChain.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Wrike MCP to LangChain

Create your Vinkius account to connect Wrike to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Wrike with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Execute Multi-Step Task Workflows

You can chain tool calls together to build a full reasoning pipeline. Start by calling `list_tasks` to filter for all 'Active' projects, then pass that filtered list of tasks to the next step. The agent doesn't just run tools; it decides *which* tool runs and in what order based on intermediate results. This lets you build complex logic that goes beyond a single API call.

Gather Deep Task Context

Need to write up a report? First, get the basic task info using `get_task_details`. Then, chain that result by calling `list_task_comments` and `list_task_attachments`. This gathers all context—discussion history and files—into one structured input. This ability lets your agent synthesize information from different data points. It's not just retrieving; it's compiling a complete picture of what happened on the task.

Audit Project Status Changes

An agent can monitor project changes by first calling `list_folders_and_projects` to map the entire hierarchy. Then, you use `get_user_profile` and `list_team_members` to identify who has access to which area. This workflow lets your agent check permissions against current task status. You can verify if a user needs specific rights before attempting an action like using `update_task`.

Setup guide

Set up Wrike MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Wrike tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "wrike-alternative-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Wrike transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Wrike now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Wrike MCP in LangChain

LangChain treats every MCP tool call as a link in a chain. When you pull task details from Wrike, the output of that function becomes the direct input for the next step in your agent's logic.

Yes. The client supports multi-server aggregation. You can combine tools from different MCP Servers into one unified, complex workflow pipeline.

LangChain handles structured project metadata, including task status (Active, Completed, Deferred), user profiles, and the content of comments found via `list_task_comments`.

It does. While stateless by default, you can use client.session() to maintain a persistent context, so your agent remembers the results of previous Wrike tool calls within the same session.

You should chain together `list_tasks` followed by `get_task_details`. This sequence allows your agent to pull a list of tasks, then dive deep into the specific context of each one sequentially.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript