# How to integrate Helpwise MCP with Claude Agent SDK

```json
{
  "title": "How to integrate Helpwise MCP with Claude Agent SDK",
  "toolkit": "Helpwise",
  "toolkit_slug": "helpwise",
  "framework": "Claude Agent SDK",
  "framework_slug": "claude-agents-sdk",
  "url": "https://composio.dev/toolkits/helpwise/framework/claude-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/helpwise/framework/claude-agents-sdk.md",
  "updated_at": "2026-05-12T10:14:48.193Z"
}
```

## Introduction

This guide walks you through connecting Helpwise to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Helpwise agent that can add note to open conversation with client, delete outdated contact from contact list, create new team for support agents through natural language commands.
This guide will help you understand how to give your Claude Agent SDK agent real control over a Helpwise account through Composio's Helpwise MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Helpwise with

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

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

The Helpwise MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Helpwise account. It provides structured and secure access to your customer communication tools, so your agent can create conversations, manage notes, upload attachments, delete messages, and organize your Helpwise workspace on your behalf.
- Attachment management and uploads: Easily upload files as attachments to conversations and retrieve attachment metadata for streamlined file sharing.
- Conversation note automation: Let your agent add or remove notes to specific conversations, making it easy to document context or follow up actions.
- Mailbox and conversation cleanup: Direct your agent to delete entire conversations, mailboxes, or individual messages for efficient workspace management.
- Contact and signature management: Seamlessly delete contacts and email signatures, keeping your Helpwise account up to date and clutter-free.
- Webhook and team setup: Have your agent create new webhooks for event notifications or set up Helpwise teams to organize your users for better collaboration.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `HELPWISE_CREATE_ATTACHMENT` | Create attachment | Tool to upload a new attachment. Use when you need to send a file to Helpwise and receive its attachment metadata. |
| `HELPWISE_CREATE_NOTE` | Add note to conversation | Tool to add a note to a conversation. Use after obtaining the conversation_id to provide context. |
| `HELPWISE_CREATE_TEAM` | Create Helpwise Team | Creates a new team in Helpwise to group users for collaboration and assignment purposes. Use this tool when you need to: - Create a new team with a unique name - Optionally add a description for the team - Optionally assign initial members by their user IDs IMPORTANT: Team creation via API is not available in the current Helpwise API. All tested endpoints (/api/v1/teams, /dev-apis/teams, /api/v1/team, /dev-apis/team) return 404. Team management appears to be limited to the Helpwise web interface. If you need to create teams, please: 1. Use the Helpwise web interface at https://app.helpwise.io 2. Contact Helpwise support at dev@helpwise.io to request API endpoint availability This action is implemented speculatively for future API support and follows standard patterns used in other Helpwise actions. |
| `HELPWISE_CREATE_WEBHOOK` | Create Helpwise Webhook | Creates a new webhook subscription in Helpwise to receive real-time event notifications. Use this action to programmatically subscribe to Helpwise events like conversation creation, message replies, conversation assignments, status changes, and tag applications. Webhooks deliver JSON payloads to your specified callback URL when subscribed events occur. IMPORTANT: Helpwise webhook management is primarily done through the UI at: Settings > Automation > Integrations > Webhooks (https://app.helpwise.io/settings/integrations) This action attempts to use programmatic API endpoints, but if they're unavailable in your Helpwise plan or environment, you'll need to create webhooks manually via the UI. |
| `HELPWISE_DELETE_CONTACT` | Delete Contact | Deletes a contact from Helpwise by its unique identifier (ID). Use this action when you need to permanently remove a contact from your Helpwise account. Returns an empty response (HTTP 204 No Content) on successful deletion. Note: This action is idempotent - deleting a non-existent contact will return an appropriate error. |
| `HELPWISE_DELETE_CONVERSATION` | Delete Helpwise Conversation | Attempts to delete a conversation by ID from Helpwise. Note: The Helpwise API may not support conversation deletion via the REST API. If deletion is not supported, this action will return an error indicating that the endpoint was not found or the method is not allowed. Use this action when you need to attempt to permanently remove a conversation by its ID. |
| `HELPWISE_DELETE_MAILBOX` | Delete Mailbox | Tool to delete a mailbox by its unique identifier. NOTE: As of 2026, the Helpwise API may not support mailbox deletion via API. This action attempts deletion but will fail if the endpoint is not available (405 Method Not Allowed). Consider managing mailboxes through the Helpwise web interface if API deletion is unsupported. |
| `HELPWISE_DELETE_MESSAGE` | Delete Helpwise Message | Attempts to delete a message from Helpwise. Note: The Helpwise API may not support message deletion via the REST API. If deletion is not supported, this action will return an error indicating that the DELETE method is not allowed (HTTP 405). Use this action when you need to attempt to permanently remove a message by its ID. |
| `HELPWISE_DELETE_NOTE` | Delete Helpwise Note | Tool to delete a note from a conversation. Use when you need to permanently remove a note by its ID from a specific conversation after confirming the IDs. |
| `HELPWISE_DELETE_SIGNATURE` | Delete Email Signature | Deletes an email signature from Helpwise. Email signatures are text/HTML templates that automatically append to outgoing emails from specific mailboxes or users. This action permanently removes the signature identified by the signature_id. Returns an empty response on successful deletion (204 No Content). |
| `HELPWISE_DELETE_TAG` | Delete Tag | Permanently deletes a tag from Helpwise. This action removes the tag from all conversations where it was applied and cannot be undone. Use this when you need to permanently remove a tag that is no longer needed. Note: Deleting a tag will automatically remove it from all existing conversations that use this tag. |
| `HELPWISE_DELETE_TEAM` | Delete Team | Tool to delete a team. Use when you need to remove an existing team by its unique identifier after confirming the ID and dependencies. |
| `HELPWISE_DELETE_TEMPLATE` | Delete Template | Deletes a Helpwise email template (saved reply) by its ID. Returns empty response on success (HTTP 204). Use this tool when you need to permanently remove a template that is no longer needed. Ensure the template_id is valid before deletion - this operation cannot be undone. Common responses: - Success (204): Template deleted successfully - Not Found (404): Template ID does not exist or was already deleted - Forbidden (403): No permission to delete this template |
| `HELPWISE_DELETE_WEBHOOK` | Delete Helpwise Webhook | Delete a Helpwise webhook by its ID. Use this tool when you need to permanently remove a webhook configuration. Returns an empty response on successful deletion (HTTP 204 No Content). |
| `HELPWISE_GET_ATTACHMENT` | Get Attachment | Retrieves a specific attachment by its unique identifier. Use this after obtaining an attachment ID from conversations, messages, or attachment listings to get detailed attachment metadata including download URL, file name, content type, and timestamps. |
| `HELPWISE_GET_ATTACHMENTS` | Get Conversation Attachments | Retrieves attachments from messages in a specific conversation. **Important**: Helpwise does not provide a dedicated attachments endpoint. This action retrieves attachments by fetching messages from the conversation and extracting attachment information from them. A conversation_id is required to use this action. Use this when you need to: - Get all file attachments from a specific conversation - Access attachment metadata (filename, URL, size, content type) - Download files shared in customer support conversations **Note**: This action retrieves attachments through the messages endpoint, as Helpwise embeds attachment data within message objects rather than providing a standalone attachments resource. |
| `HELPWISE_GET_CONTACT` | Get Helpwise Contact | Retrieves detailed information for a specific contact by ID. Use this when you need to fetch complete contact details including name, email, phone, company, and timestamps for a known contact ID. |
| `HELPWISE_GET_CONVERSATION` | Get Conversation | Retrieves complete details of a specific conversation by ID from Helpwise. Returns the conversation metadata including subject, status, participants, and timestamps. Use this action when you need to view or analyze a specific conversation's details. Example use cases: - Checking the status of a support ticket conversation - Viewing conversation participants and assignees - Retrieving conversation metadata for reporting |
| `HELPWISE_GET_CONVERSATIONS` | Get Conversations | Tool to retrieve a list of conversations. Use when you need to list and paginate support conversations for display or analysis. |
| `HELPWISE_GET_CUSTOM_FIELD` | Get Helpwise Custom Field | Retrieves details of a specific custom field by its ID. Use this when you need to fetch custom field properties such as name, description, value, associated inboxes, and creator information. |
| `HELPWISE_GET_MAILBOX` | Get Helpwise Mailbox | Tool to retrieve details of a specific mailbox by its ID. Use when you know the mailbox ID and need full mailbox information. |
| `HELPWISE_GET_MAILBOXES` | Get Helpwise Mailboxes | Tool to retrieve mailboxes. Use when you need to list and paginate mailboxes after authenticating. |
| `HELPWISE_GET_NOTE` | Get Conversation Note | Tool to retrieve details of a specific note. Use when you know the conversation and note IDs and need full note information. |
| `HELPWISE_GET_NOTES` | Get Conversation Notes | Retrieves all notes associated with a specific conversation. Notes are internal comments or annotations that team members add to conversations for collaboration and context. |
| `HELPWISE_GET_TAG` | Get Helpwise Tag | Retrieves detailed information about a specific tag in Helpwise. Use this action when you need to: - Get the full properties of a tag including its name, color, and timestamps - Verify that a tag exists before performing operations on it - Retrieve tag details for display or processing Tags in Helpwise are labels that can be applied to conversations for organization and filtering. |
| `HELPWISE_GET_TEAM` | Get Helpwise Team | Retrieves details of a specific Helpwise team by its ID. Note: Team endpoints may not be available in all Helpwise API plans. If this action returns a 404 error, teams may need to be managed through the Helpwise web interface. Use this tool when you have a valid team_id and need to fetch team details such as name and timestamps. |
| `HELPWISE_GET_TEAMS` | Get Helpwise Teams | Tool to retrieve Helpwise teams. Use when you need to list and paginate all teams for assignment or management. |
| `HELPWISE_GET_TEMPLATES` | Get Helpwise WhatsApp Templates | Tool to retrieve Helpwise WhatsApp message templates. Use when you need to list WhatsApp templates for a mailbox or account. |
| `HELPWISE_GET_USERS` | Get Helpwise Users | Tool to retrieve Helpwise users list. Use when you need to fetch and paginate agents for assignment. |
| `HELPWISE_GET_WEBHOOK` | Get Helpwise Webhook | Retrieve detailed configuration for a specific Helpwise webhook by its ID. Use this action when you: - Need to inspect the configuration of an existing webhook - Want to verify webhook settings (URL, events, active status) - Need to check webhook creation/update timestamps Prerequisites: You must have a valid webhook ID, which can be obtained from the 'Get Webhooks' action or when creating a webhook. |
| `HELPWISE_GET_WEBHOOKS` | Get Helpwise Webhooks | Tool to retrieve Helpwise webhooks. Use when you need to list and paginate all webhook configurations. |
| `HELPWISE_SEARCH_CONTACTS` | Search Helpwise Contacts | Tool to search contacts by term with pagination. Use when you need to find contacts by name, email, phone, or other contact attributes. |
| `HELPWISE_UPDATE_CONTACT` | Update Helpwise Contact | Tool to update an existing Helpwise contact. Use when you need to modify contact details or custom attributes. |
| `HELPWISE_UPDATE_MAILBOX` | Update Mailbox | Updates an existing Helpwise mailbox. Use this action to modify mailbox settings such as display name, email address, team assignment, email signature, or default status. At least one field must be provided for update. Obtain the mailbox_id from the Get Mailboxes action. |
| `HELPWISE_UPDATE_MESSAGE` | Update Helpwise Message | Tool to update an existing message. Use when you need to modify message content by its ID. |
| `HELPWISE_UPDATE_TAG` | Update Helpwise Tag | Updates an existing tag's name and/or color in Helpwise. Use this action when you need to rename a tag or change its visual appearance. You must have the tag's ID before calling this action - obtain it using HELPWISE_GET_TAG or from the Helpwise UI. |
| `HELPWISE_UPDATE_TEMPLATE` | Update Helpwise Template | Updates an existing Helpwise email template by modifying its name, subject, and/or HTML content. Use this action when you need to: - Change the display name of a template - Update the subject line (including placeholders) - Modify the HTML content/body of the template Prerequisites: - You must have the template_id (obtain via Get Templates action or Helpwise UI) - At least one field (name, subject, or html) must be provided for update Note: This action performs a partial update - only provided fields will be modified. |

## Supported Triggers

None listed.

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

The Helpwise MCP server is an implementation of the Model Context Protocol that connects your AI agent to Helpwise. It provides structured and secure access so your agent can perform Helpwise operations on your behalf through a secure, permission-based interface.
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:
- Composio API Key and Claude/Anthropic API Key
- Primary know-how of Claude Agents SDK
- A Helpwise account
- Some knowledge of Python

### 1. Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
- Go to the [Anthropic Console](https://console.anthropic.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-anthropic claude-agent-sdk python-dotenv
```

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

### 3. Set up environment variables

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
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here
```

### 4. Import dependencies

No description provided.
```python
import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
```

```typescript
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();
```

### 5. Create a Composio instance and Tool Router session

No description provided.
```python
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 Helpwise
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["helpwise"]
    )

    url = mcp_server.mcp.url

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

```typescript
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 Helpwise
  const session = await composio.create(USER_ID, {
    toolkits: ['helpwise'],
  });
  const mcpUrl = session?.mcp.url;
```

### 6. Configure Claude Agent with MCP

No description provided.
```python
# 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 Helpwise tools via Composio.",
    max_turns=10
)
```

```typescript
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 Helpwise tools via Composio.',
  maxTurns: 10,
};
```

### 7. Create client and start chat loop

No description provided.
```python
# 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()
```

```typescript
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?');
}
```

### 8. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
```

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

## Complete Code

```python
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 Helpwise
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["helpwise"]
    )

    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 Helpwise 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())
```

```typescript
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: ['helpwise']
  });
  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 Helpwise 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 Helpwise 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 Helpwise MCP Agent with another framework

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

## Related Toolkits

- [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools.
- [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations.
- [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates.
- [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates.
- [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations.
- [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code.
- [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding.
- [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls.
- [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.
- [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates.
- [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality.
- [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster.
- [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.
- [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support.
- [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach.
- [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback.

## Frequently Asked Questions

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

With a standalone Helpwise MCP server, the agents and LLMs can only access a fixed set of Helpwise tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Helpwise 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 Helpwise tools.

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

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

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