How to integrate Wrike MCP with LangChain

This guide walks you through connecting Wrike to LangChain using the Composio tool router. By the end, you'll have a working Wrike agent that can create a new task in marketing folder, add multiple users to project group, invite a teammate to the workspace through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Wrike account through Composio's Wrike MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Wrike logoWrike
Oauth2

Wrike is a project management and team collaboration platform with customizable workflows, Gantt charts, and reporting. It helps teams boost productivity with centralized planning and resource management.

144 Tools

Introduction

This guide walks you through connecting Wrike to LangChain using the Composio tool router. By the end, you'll have a working Wrike agent that can create a new task in marketing folder, add multiple users to project group, invite a teammate to the workspace through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Wrike account through Composio's Wrike MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Wrike with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Wrike project to Composio
  • Create a Tool Router MCP session for Wrike
  • Initialize an MCP client and retrieve Wrike tools
  • Build a LangChain agent that can interact with Wrike
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Wrike MCP server, and what's possible with it?

The Wrike MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Wrike account. It provides structured and secure access to your project spaces, so your agent can perform actions like creating tasks, managing folders, handling group memberships, sending workspace invitations, and automating project workflows on your behalf.

  • Automated task creation and management: Let your agent quickly create new tasks in specific folders, assign details, and keep your projects moving forward without manual input.
  • Dynamic folder and project organization: Have your agent generate new folders or subfolders to structure work, or clean up by deleting old folders and their contents when projects wrap up.
  • Efficient user and group management: Easily add, remove, or modify group memberships and create new user groups to keep team permissions organized and up-to-date.
  • Seamless workspace invitations: Direct your agent to invite teammates or collaborators to your Wrike workspace via email, including customizing invitation details for better onboarding.
  • Custom field and data cleanup: Empower your agent to delete custom fields, tasks, or groups when they're no longer needed, helping you maintain a clean and efficient workspace.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Wrike functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Wrike tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['wrike']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Wrike tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Wrike tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "wrike-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Wrike MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Wrike tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Wrike related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Wrike and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['wrike']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "wrike-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Wrike related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Wrike through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Wrike action and event your agent gets out of the box.

Bulk modify group members

Adds or removes members for multiple Wrike groups in a single request; all specified user IDs must correspond to existing Wrike users.

Copy folder

Copies a Wrike folder synchronously to a specified parent location with customizable options.

Copy folder async

Duplicate a folder asynchronously in Wrike, creating a copy in a specified parent location.

Create account webhooks

Creates a webhook for the current account to receive notifications about changes.

Create equipment asset

Tool to create equipment/asset in Wrike.

Create custom field

Tool to create a new custom field in Wrike.

Create a folder

Creates a new Wrike subfolder within the specified `folderId`, optionally as a project if `customItemTypeId` is given; the folder is auto-shared with its creator.

Create folder booking

Tool to create a booking in a Wrike folder.

Create approval in folder

Tool to create a new approval in a Wrike folder.

Create folder comment

Creates a new comment on a specified Wrike folder.

Create timelog lock period for folder

Creates a timelog lock period for a specific folder.

Create a webhook on folder

Tool to create a webhook for a Wrike folder or project.

Create a group

Creates a new user group in Wrike with a specified title, optionally setting members, parent group, avatar, and custom metadata.

Create invitation

Invites a user to a Wrike workspace by email, optionally with name, specifying EITHER `userTypeId` OR a combination of `role`/`external`; custom email subject/message available for paid accounts.

Create space timelog lock period

Tool to create a timelog lock period for a space to prevent time entries from being edited.

Create space webhook

Tool to create a webhook on a Wrike space for receiving notifications about changes to tasks, folders, and projects.

Create task in folder

Creates a new task in a specified Wrike folder; if setting priority with `priorityBefore` or `priorityAfter`, the referenced task must be in the same folder or project.

Create task attachment

Tool to upload a file attachment to a Wrike task.

Create task comment

Tool to create a new comment on a Wrike task.

Create task approval

Tool to create an approval on a specific task in Wrike.

Create task dependency

Tool to create a new dependency relationship between Wrike tasks.

Create task timelog

Tool to create a timelog entry for a specific task in Wrike.

Create timesheet

Tool to create a timesheet for a user for a specified time period.

Create workflows

Tool to create a new custom workflow in Wrike.

Delete approval

Cancels/deletes an approval by its identifier.

Delete asset

Permanently deletes a Wrike asset/equipment by assetId.

Delete attachment

Tool to permanently delete a Wrike attachment by its ID.

Delete booking

Permanently removes a resource booking allocation by its ID; use when deallocating resources from projects or tasks.

Delete comment

Permanently deletes a Wrike comment by its ID; this action is irreversible and the comment must exist.

Delete custom field by id

Permanently deletes a custom field by its ID; this action is irreversible and requires a valid, existing custom field ID.

Delete dependencies

Permanently removes a task dependency relationship by its ID; use when unlinking predecessor/successor task relationships.

Delete folder

Permanently deletes the folder specified by `folderId` and all its contents (e.

Delete timelog lock period for folder

Deletes a timelog lock period for a specific folder.

Delete group by id

Permanently deletes a group by its `groupId`; this action is irreversible and does not affect user accounts that were members of the group.

Delete invitation

Permanently deletes an existing invitation, specified by its unique `invitationId`; this action cannot be undone.

Delete job role

Permanently deletes a job role by its identifier; deleted job roles are removed from all tasks and users and cannot be restored.

Delete space

Permanently deletes a Wrike space and all its contents by spaceId; this action is irreversible and should be used with caution.

Delete spaces timelog lock period

Tool to unlock (delete) a timelog lock period for a specific space in Wrike.

Delete task

Permanently deletes a Wrike task and all its associated data by its ID; this action is irreversible and the task must exist.

Delete timelog

Permanently deletes a Wrike timelog entry by its ID; use when removing an incorrect or obsolete time log entry.

Delete webhook

Tool to permanently delete a webhook by webhook_id.

Fetch all tasks

Fetches tasks from a Wrike account, allowing filtering by status, due date, and subfolder inclusion, with customizable response fields and pagination.

Get account information

Retrieves detailed Wrike account information, where the response content is influenced by selected fields, account subscription, and user permissions.

Get all custom fields

Retrieves all custom field definitions (including ID, name, type, and settings) from the Wrike account; this returns the definitions themselves, not their specific values on Wrike items, and is useful for obtaining custom field IDs.

Get all webhooks

Tool to retrieve a list of all webhooks created using the same API token.

Get approvals

Tool to retrieve all approvals accessible to the authenticated user.

Get approvals by IDs

Tool to retrieve specific Wrike approvals by their IDs (up to 100).

Get async job status

Tool to retrieve status and details for an asynchronous job in Wrike.

Get attachments by IDs

Tool to retrieve multiple Wrike attachments by their IDs (up to 100).

Download attachment

Tool to download a Wrike attachment file.

Get attachment preview

Tool to download a preview version of a Wrike attachment.

Get attachment URL

Tool to get a public access URL for a Wrike attachment.

Get bookings

Retrieves one or more Wrike bookings by their IDs.

Get colors

Tool to query the list of available colors in Wrike.

Get comments

Tool to retrieve all comments accessible to the authorized user.

Get comments by IDs

Tool to retrieve multiple Wrike comments by their IDs.

Get contact hourly rates

Tool to retrieve hourly budget rates for up to 100 Wrike contacts.

Get contacts

Retrieves a list of Wrike contacts (e.

Get contacts history

Tool to access field modification history for Wrike contacts.

Get contact timelogs

Tool to retrieve all timelog records created by a specific contact in Wrike.

Get custom item types

Tool to retrieve all custom item types from Wrike.

Get dependencies by IDs

Tool to retrieve one or more Wrike dependencies by their IDs (up to 100).

Get folder bookings

Tool to query bookings for a specific folder in Wrike.

Get folders

Retrieves folders and/or projects from Wrike, with filters; when using `nextPageToken`, all other filter parameters must match the initial request.

Get folder approvals

Tool to retrieve all approvals from a specific Wrike folder.

Get folder attachments

Tool to retrieve all attachments from a specific Wrike folder.

Get folders by IDs

Tool to retrieve multiple Wrike folders by their IDs.

Get folder comments

Tool to retrieve comments from a specific Wrike folder.

Get folders history

Tool to access field modification history for Wrike folders.

Get folder hourly rates

Tool to retrieve hourly budget rates for a specific Wrike folder.

Get folder rollups

Tool to query rollup settings for items in a folder.

Get folder tasks

Query tasks within a specific folder.

Get folder timelog lock periods

Tool to query timelog lock periods for a specific folder.

Get folders timelogs

Tool to retrieve all timelog records for a specific folder.

Convert legacy v2 IDs to v4

Tool to convert legacy Wrike API v2 IDs to current v4 format.

Get specific contact information

Retrieves detailed information for a specific Wrike contact using their unique `contactId`, optionally including `metadata` and `customFields` if specified in the `fields` parameter.

Get job roles by IDs

Tool to retrieve details for one or more Wrike job roles by job role IDs.

Get placeholder hourly rates

Tool to retrieve hourly budget rates for one or more Wrike placeholders.

Get placeholders by IDs

Tool to retrieve details for one or more Wrike placeholders by their IDs.

Get space by ID

Tool to retrieve details for a single Wrike space by spaceId.

Get space custom item types

Tool to retrieve all custom item types scoped to a specific Wrike space.

Get space folders

Tool to retrieve the folder tree for a specific Wrike space.

Get space custom fields

Tool to retrieve all custom fields defined for a specific Wrike space.

Get spaces tasks

Tool to query tasks within a specific Wrike space.

Get space workflows

Tool to query workflows for a specific Wrike space.

Get space timelog lock periods

Tool to query timelog lock periods for a specific space.

Get specific user

Retrieves detailed information about a specific user in Wrike using their unique user ID.

Get task by id

Retrieves read-only detailed information for a specific Wrike task by its unique ID, optionally allowing specification of fields to include in the response.

Get task dependencies

Retrieves all dependency relationships for a specific task.

Get task approvals

Retrieves all approval records for a specific task.

Get task attachments

Tool to retrieve all attachments from a specific Wrike task.

Get task comments

Tool to retrieve all comments from a specific Wrike task.

Get tasks history

Query task field modification history for up to 100 tasks.

Get task rollups

Tool to query rollup settings for a specific task.

Get task timelog lock periods

Tool to query timelog lock periods for a specific task.

Get task timelogs

Retrieves all timelog records for a specific task.

Get timelog categories

Tool to query the list of timelog categories in Wrike.

Get timelogs

Retrieves timelog records from Wrike with optional filters for dates, users, and task scope.

Get timelogs by IDs

Retrieves detailed information for one or more Wrike timelogs by their unique IDs (up to 100), optionally including export and lock status.

Get timesheets

Tool to query timesheets from Wrike.

Get timesheet submission rules

Tool to retrieve global timesheet submission rules across all work schedules.

Get API version

Tool to retrieve current Wrike API version information.

Get webhook by ID

Tool to retrieve details for a specific webhook by webhook_id.

Get work schedule timesheet rules

Tool to retrieve timesheet submission rules for a specific work schedule.

Launch folder blueprint async

Asynchronously launches a new project or folder structure in Wrike from a specified Folder Blueprint.

Launch Task Blueprint Async

Asynchronously launches a Wrike Task Blueprint to create tasks/projects, requiring either `super_task_id` (parent task) or `parent_id` (parent folder/project) for placement.

List all attachments

Tool to retrieve all attachments from the Wrike account.

List Folder Blueprints

Retrieves all account-level Folder Blueprints, which are templates for standardizing folder/project creation with predefined structures, custom fields, and workflows.

List all placeholders

Retrieves all placeholders accessible to the authenticated user; placeholders are templates used in Wrike for creating standardized tasks or projects.

List space folder blueprints

Lists all folder blueprints (templates for new folders/projects) within a specified Wrike space, requiring a valid and accessible space ID.

List spaces

Tool to list spaces the authorized user can access.

List space task blueprints

Lists task blueprints (templates for creating tasks with consistent structures) available in a specific, accessible Wrike space.

List subfolders by folder id

Lists subfolders (metadata only, not their contents) for an existing Wrike folder specified by `folderId`, supporting recursive descent, filtering, and pagination.

List Task Blueprints

Retrieves a list of defined Task Blueprints (predefined task templates) from the Wrike account, supporting pagination.

Update account metadata

Updates or adds custom key-value metadata to the Wrike account, useful for integrations, storing app-specific data, or mapping external system identifiers.

Modify folder attributes

Modifies an existing Wrike folder: updates title, description, parents (not root/recycle bin), sharing, metadata, custom fields/columns; restores, converts to project, or manages access roles.

Modify group

Updates an existing Wrike user group's attributes like title, members, parent, avatar, or metadata, using its `groupId` and specifying only the fields to change.

Modify task

Modifies an existing Wrike task by its ID, allowing updates to attributes such as title, status, dates, assignees, and custom fields; `priorityBefore` and `priorityAfter` are mutually exclusive, and parent folder IDs for `addParents`/`removeParents` cannot be the Recycle Bin.

Retrieve custom field by id

Retrieves a Wrike custom field's detailed information (e.

Query invitations

Retrieves all active invitations in Wrike, useful for viewing and auditing pending invitations or managing user onboarding.

Query job roles

Tool to retrieve all available job roles in the Wrike account.

Get group by id

Retrieves detailed information for a specific Wrike group using its `groupId`, optionally including 'metadata'.

Query workflows

Fetches a list of all workflows with their detailed information from the Wrike account; this is a read-only action and does not support pagination or filtering through its parameters.

Retrieve list of groups

Retrieves a list of user groups from the Wrike account, supporting metadata filtering, pagination, and inclusion of specific fields; this is a read-only operation.

Search eDiscovery

Tool to perform eDiscovery search across Wrike items (folders, projects, tasks).

Update approval

Updates an existing Wrike approval by its ID, allowing modifications to the title, description, and due date.

Update asset

Tool to update a Wrike asset/equipment by ID.

Update attachment

Tool to update a Wrike attachment by uploading new file content.

Update booking

Updates a Wrike booking's date range by ID.

Update comment

Tool to update an existing Wrike comment.

Update custom field by id

Updates properties of an existing Wrike custom field by its ID, such as its title, type, scope, or sharing settings.

Update dependency

Tool to modify an existing Wrike dependency relationship between tasks.

Update folder rollup settings

Tool to update rollup settings for a folder.

Update invitation

Updates a pending Wrike invitation (`invitationId`) to resend it or change user's role/type (use EITHER `userTypeId` OR `role`/`external`).

Update job role

Updates an existing Wrike job role by its ID, allowing modifications to the title and short title.

Update metadata on a specific contact

Updates metadata, job role, or custom fields for an existing Wrike contact specified by `contactId`; if `jobRoleId` is provided, it must be a valid ID.

Update a specific user

Updates specified profile attributes (e.

Update task rollup settings

Updates rollup settings for a task.

Update timelog entry

Tool to modify an existing timelog entry in Wrike.

Update timesheet row

Updates a Wrike timesheet row by its ID, allowing modification of the timelog category.

Update timesheet

Tool to update a timesheet's approval status in Wrike.

Update webhook state

Tool to update the state of a Wrike webhook.

Update workflow

Tool to modify an existing Wrike workflow.

Update work schedule timesheet rules

Tool to update timesheet submission rules for a work schedule.

FRAMEWORKS

How to build Wrike MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Wrike MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Wrike MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Wrike MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Wrike MCP with Claude Cowork

Codex logo

Codex

Use Wrike MCP with Codex

OpenClaw logo

OpenClaw

Use Wrike MCP with OpenClaw

Hermes logo

Hermes

Use Wrike MCP with Hermes

CLI logo

CLI

Use Wrike MCP with CLI

Google ADK logo

Google ADK

Use Wrike MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Wrike MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Wrike MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Wrike MCP with LlamaIndex

CrewAI logo

CrewAI

Use Wrike MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Wrike MCP server, the agents and LLMs can only access a fixed set of Wrike tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Wrike and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LangChain fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Wrike tools.

Yes, absolutely. You can configure which Wrike scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Wrike data and credentials are handled as safely as possible.

Start with Wrike.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Wrike tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies