# How to integrate Workiom MCP with Claude Code

```json
{
  "title": "How to integrate Workiom MCP with Claude Code",
  "toolkit": "Workiom",
  "toolkit_slug": "workiom",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/workiom/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/workiom/framework/claude-code.md",
  "updated_at": "2026-05-12T10:30:38.282Z"
}
```

## Introduction

Manage your Workiom directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Workiom with

- [OpenAI Agents SDK](https://composio.dev/toolkits/workiom/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/workiom/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/workiom/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/workiom/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/workiom/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/workiom/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/workiom/framework/cli)
- [Google ADK](https://composio.dev/toolkits/workiom/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/workiom/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/workiom/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/workiom/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/workiom/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/workiom/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Workiom to Claude Code

### Connecting Workiom to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

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

The Workiom MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Workiom account. It provides structured and secure access to your Workiom workspace, so your agent can perform actions like listing your databases, creating new workflow records, and retrieving business data automatically.
- List and explore Workiom databases: Instantly fetch and review all lists in your workspace, making it easy to discover and reference your business data structures.
- Automate record creation: Direct your agent to add new records to any list, capturing details like text, numbers, dates, and static fields for streamlined workflows and reduced manual entry.
- Retrieve and filter records: Effortlessly pull relevant records from specific lists, with support for filtering, sorting, and pagination to quickly surface the data you need.
- Workspace structure insights: Get field definitions and metadata for lists, so your agent can understand data models and populate records accurately.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `WORKIOM_CREATE_RECORD` | Create record | Creates a new record in a specified Workiom list. This tool creates a record with basic field types like text, numbers, dates, and static list items. The record data should be provided as a JSON object where each key is a field ID and the value matches the expected data type for that field. |
| `WORKIOM_GET_ALL_LISTS` | Get all lists | Get all lists from a Workiom app. This action fetches all lists within a specific Workiom app. Lists are containers for records (similar to database tables) and are the fundamental data structure in Workiom. Each list has a unique ID and contains views for displaying data. Use this action to discover available lists before performing operations like creating records (which require a list ID). |
| `WORKIOM_GET_RECORDS` | Get records | Retrieves records from a specified Workiom list. Use this action to fetch data from a Workiom list. The list_id is required and can be obtained from the WORKIOM_GET_ALL_LISTS action. Each record contains field values keyed by numeric field IDs. Features: - Pagination: Use max_result_count and skip_count to paginate through large datasets - Sorting: Sort by any field using 'FIELD_ID ASC' or 'FIELD_ID DESC' format - Filtering: Apply conditions using filter operators (Contains, Is, Greater, etc.) Note: Field IDs are numeric (e.g., 5037173) and can be found in list metadata. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Workiom MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Workiom account. It provides structured and secure access so Claude can perform Workiom operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Workiom account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["workiom"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http workiom-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['workiom'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http workiom-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Workiom MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (workiom-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http workiom-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Workiom MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your workiom-composio entry in the list
- This confirms that Claude Code can now access Workiom tools
If everything is wired up, you should see your workiom-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Workiom

The first time you try to use Workiom tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Workiom
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Workiom authorization flow
- Return to the terminal and start using Workiom through Claude Code
Once authenticated, you can ask Claude Code to perform Workiom operations in natural language. For example:
- "List all active projects in our workspace"
- "Create a new client record in CRM list"
- "Fetch overdue tasks from the Tasks list"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["workiom"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http workiom-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['workiom'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http workiom-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Workiom with Claude Code using Composio's MCP server. Now you can interact with Workiom directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Workiom operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Workiom operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Workiom MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/workiom/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/workiom/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/workiom/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/workiom/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/workiom/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/workiom/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/workiom/framework/cli)
- [Google ADK](https://composio.dev/toolkits/workiom/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/workiom/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/workiom/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/workiom/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/workiom/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/workiom/framework/crew-ai)

## Related Toolkits

- [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations.
- [Basin](https://composio.dev/toolkits/basin) - Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code.
- [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications.
- [Conveyor](https://composio.dev/toolkits/conveyor) - Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.
- [Crowdin](https://composio.dev/toolkits/crowdin) - Crowdin is a localization management platform that streamlines translation workflows and collaboration. It helps teams centralize multilingual content, boost productivity, and automate translation processes.
- [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights.
- [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way.
- [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease.
- [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration.
- [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease.
- [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease.
- [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services.
- [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows.
- [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses.
- [Hyperbrowser](https://composio.dev/toolkits/hyperbrowser) - Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale.
- [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals.
- [Leverly](https://composio.dev/toolkits/leverly) - Leverly is a workflow automation platform that connects and coordinates actions across your apps. It streamlines repetitive processes so your business runs smoother, faster, and with fewer manual steps.
- [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination.
- [Make](https://composio.dev/toolkits/make) - Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code.
- [Ntfy](https://composio.dev/toolkits/ntfy) - Ntfy is a notification service to send push messages to phones or desktops. Instantly deliver alerts and updates to users, devices, or teams.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Workiom MCP?

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

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code 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 Workiom tools.

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

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)