How to integrate Wrike MCP with Claude Agent SDK

Framework Integration Gradient
Wrike Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Wrike to the Claude Agent SDK 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, delete completed tasks from design folder through natural language commands.

This guide will help you understand how to give your Claude Agent SDK 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.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Wrike
  • Configure an AI agent that can use Wrike as a tool
  • Run a live chat session where you can ask the agent to perform Wrike operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

Supported Tools & Triggers

Tools
Bulk modify group membersAdds or removes members for multiple wrike groups in a single request; all specified user ids must correspond to existing wrike users.
Create a folderCreates 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 a groupCreates a new user group in wrike with a specified title, optionally setting members, parent group, avatar, and custom metadata.
Create invitationInvites 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 task in folderCreates 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.
Delete custom field by idPermanently deletes a custom field by its id; this action is irreversible and requires a valid, existing custom field id.
Delete folderPermanently deletes the folder specified by `folderid` and all its contents (e.
Delete group by idPermanently deletes a group by its `groupid`; this action is irreversible and does not affect user accounts that were members of the group.
Delete invitationPermanently deletes an existing invitation, specified by its unique `invitationid`; this action cannot be undone.
Delete taskPermanently deletes a wrike task and all its associated data by its id; this action is irreversible and the task must exist.
Fetch all tasksFetches tasks from a wrike account, allowing filtering by status, due date, and subfolder inclusion, with customizable response fields and pagination.
Get account informationRetrieves detailed wrike account information, where the response content is influenced by selected fields, account subscription, and user permissions.
Get all custom fieldsRetrieves 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 contactsRetrieves a list of wrike contacts (e.
Get foldersRetrieves folders and/or projects from wrike, with filters; when using `nextpagetoken`, all other filter parameters must match the initial request.
Get specific contact informationRetrieves detailed information for a specific wrike contact using their unique `contactid`, optionally including `metadata` and `customfields` if specified in the `fields` parameter.
Get specific userRetrieves detailed information about a specific user in wrike using their unique user id.
Get task by idRetrieves read-only detailed information for a specific wrike task by its unique id, optionally allowing specification of fields to include in the response.
Launch folder blueprint asyncAsynchronously launches a new project or folder structure in wrike from a specified folder blueprint, typically returning a task id to track progress.
Launch Task Blueprint AsyncAsynchronously 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 Folder BlueprintsRetrieves all account-level folder blueprints, which are templates for standardizing folder/project creation with predefined structures, custom fields, and workflows.
List space folder blueprintsLists all folder blueprints (templates for new folders/projects) within a specified wrike space, requiring a valid and accessible space id.
List space task blueprintsLists task blueprints (templates for creating tasks with consistent structures) available in a specific, accessible wrike space.
List subfolders by folder idLists subfolders (metadata only, not their contents) for an existing wrike folder specified by `folderid`, supporting recursive descent, filtering, and pagination.
List Task BlueprintsRetrieves a list of defined task blueprints (predefined task templates) from the wrike account, supporting pagination.
Update account metadataUpdates or adds custom key-value metadata to the wrike account, useful for integrations, storing app-specific data, or mapping external system identifiers.
Modify folder attributesModifies 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 groupUpdates 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 taskModifies 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 idRetrieves a wrike custom field's detailed information (e.
Query invitationsRetrieves all active invitations in wrike, useful for viewing and auditing pending invitations or managing user onboarding.
Get group by idRetrieves detailed information for a specific wrike group using its `groupid`, optionally including 'metadata'.
Query workflowsFetches 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 groupsRetrieves a list of user groups from the wrike account, supporting metadata filtering, pagination, and inclusion of specific fields; this is a read-only operation.
Update custom field by idUpdates properties of an existing wrike custom field by its id, such as its title, type, scope, or sharing settings.
Update invitationUpdates a pending wrike invitation (`invitationid`) to resend it or change user's role/type (use `usertypeid` over deprecated `role`/`external`).
Update metadata on a specific contactUpdates 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 userUpdates specified profile attributes (e.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Wrike account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Wrike functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Wrike
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["wrike"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Wrike
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Wrike tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Wrike
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Wrike and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Wrike
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["wrike"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Wrike tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

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

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Wrike MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Wrike MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK 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.

Can I manage the permissions and scopes for Wrike while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.