How to integrate Order Desk MCP with Claude Agent SDK

This guide walks you through connecting Order Desk to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Order Desk agent that can look up orders, add order items, create shipments, add order notes, and manage your inventory through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Order Desk account through Composio's Order Desk MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Order Desk logoOrder Desk
Api Key

Order Desk is an order management platform for ecommerce orders, shipments, inventory, and store data. It helps teams centralize fulfillment workflows across multiple ecommerce integrations.

20 Tools

Introduction

This guide walks you through connecting Order Desk to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Order Desk agent that can look up orders, add order items, create shipments, add order notes, and manage your inventory through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Order Desk account through Composio's Order Desk MCP server.

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

Also integrate Order Desk with

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 Order Desk
  • Configure an AI agent that can use Order Desk as a tool
  • Run a live chat session where you can ask the agent to perform Order Desk 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 Order Desk MCP server, and what's possible with it?

The Order Desk MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Order Desk account. It provides structured and secure access to your orders, shipments, inventory, and store data, so your agent can find orders, manage line items, track shipments, update inventory, and organize orders on your behalf.

  • Order search and review: Have your agent find matching orders and retrieve their addresses, items, shipments, notes, discounts, and other details.
  • Order item management: Let the agent list, add, update, or remove line items from an existing order.
  • Shipment management: Direct your agent to create shipment records, review an order's shipments, update shipment details, or remove incorrect records.
  • Inventory management: Instruct your agent to search, create, review, update, or delete inventory items using details such as SKU, name, location, or update time.
  • Order organization and store context: Have your agent add permanent history notes, move orders into the right folder, and review store settings such as locale, timezone, and folder names.

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 step09 STEPS
1

Prerequisites

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

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.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

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
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

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

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Order Desk
  const session = await composio.create(USER_ID, {
    toolkits: ['order_desk'],
  });
  const mcpUrl = session?.mcp.url;
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 Order Desk
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Order Desk tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Order Desk
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

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

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['order_desk']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Order Desk tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Order Desk 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.
TOOLS

Supported Tools

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

Add Order History Note

Append a timestamped note permanently to an existing order's history.

Add Order Item

Add one line item to an existing order.

Add Order Items

Add two to 10 line items sequentially to the same order and return a result for every processed item.

Create Inventory Item

Create one inventory item with a unique SKU and return its positive Order Desk ID and complete created representation.

Create Inventory Items

Create two to 10 inventory items sequentially and return each created ID or error.

Create Shipments

Create one or more shipment records across orders in one request and report the success or error returned for every shipment.

Delete Inventory Item

Permanently delete one inventory item by its positive Order Desk ID.

Delete Order Item

Permanently remove one line item from an order.

Delete Shipment

Permanently remove one shipment record from an order.

Get Inventory Item

Get one inventory item by its positive Order Desk ID.

Get Order

Get one order and its addresses, line items, shipments, metadata, notes, and discounts by Order Desk internal ID.

Get Store Metadata

Return safe store identity, locale, timezone, page-size settings, and folder IDs and names without exposing credentials or email configuration.

List Inventory Items

Search inventory items in the connected store by ID, SKU, name, metadata, manufacturer SKU, location, or update time.

List Order Items

Return all line items for one order.

List Orders

Find orders in the connected store using at least one narrowing filter and return one bounded page.

List Order Shipments

Return all shipments recorded for one order.

Move Orders

Move one or more orders to exactly one destination folder selected by positive ID or exact name, with a result for every order.

Update Inventory Items

Safely update selected fields on one or more inventory items while preserving every omitted field.

Update Order Item

Safely update selected fields on one order line item while preserving every omitted field.

Update Shipment

Safely update selected fields on one shipment while preserving every omitted field.

FAQ

Frequently asked questions

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

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 Order Desk tools.

Yes, absolutely. You can configure which Order Desk 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 Order Desk data and credentials are handled as safely as possible.

Start with Order Desk.It takes 30 seconds.

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

Start building