# How to integrate Helpwise MCP with Google ADK

```json
{
  "title": "How to integrate Helpwise MCP with Google ADK",
  "toolkit": "Helpwise",
  "toolkit_slug": "helpwise",
  "framework": "Google ADK",
  "framework_slug": "google-adk",
  "url": "https://composio.dev/toolkits/helpwise/framework/google-adk",
  "markdown_url": "https://composio.dev/toolkits/helpwise/framework/google-adk.md",
  "updated_at": "2026-05-12T10:14:48.193Z"
}
```

## Introduction

This guide walks you through connecting Helpwise to Google ADK 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 Google ADK 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 Agent SDK](https://composio.dev/toolkits/helpwise/framework/claude-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)
- [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 a Helpwise account set up and connected to Composio
- Install the Google ADK and Composio packages
- Create a Composio Tool Router session for Helpwise
- Build an agent that connects to Helpwise through MCP
- Interact with Helpwise using natural language

## What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.
Key features include:
- Gemini Integration: Native support for Google's Gemini models
- MCP Toolset: Built-in support for Model Context Protocol tools
- Streamable HTTP: Connect to external services through streamable HTTP
- CLI and Web UI: Run agents via command line or web interface

## 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:
- A Google API key for Gemini models
- A Composio account and API key
- Python 3.9 or later installed
- Basic familiarity with Python

### 1. Getting API Keys for Google and Composio

Google API Key
- Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key.
- Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
- Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

### 2. Install dependencies

Inside your virtual environment, install the required packages.
What's happening:
- google-adk is Google's Agents Development Kit
- composio connects your agent to Helpwise via MCP
- python-dotenv loads environment variables
```bash
pip install google-adk composio python-dotenv
```

### 3. Set up ADK project

Set up a new Google ADK project.
What's happening:
- This creates an agent folder with a root agent file and .env file
```bash
adk create my_agent
```

### 4. Set environment variables

Save all your credentials in the .env file.
What's happening:
- GOOGLE_API_KEY authenticates with Google's Gemini models
- COMPOSIO_API_KEY authenticates with Composio
- COMPOSIO_USER_ID identifies the user for session management
```bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email
```

### 5. Import modules and validate environment

What's happening:
- os reads environment variables
- Composio is the main Composio SDK client
- GoogleProvider declares that you are using Google ADK as the agent runtime
- Agent is the Google ADK LLM agent class
- McpToolset lets the ADK agent call MCP tools over HTTP
```python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
```

### 6. Create Composio client and Tool Router session

What's happening:
- Authenticates to Composio with your API key
- Declares Google ADK as the provider
- Spins up a short-lived MCP endpoint for your user and selected toolkit
- Stores the MCP HTTP URL for the ADK MCP integration
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["helpwise"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
```

### 7. Set up the McpToolset and create the Agent

What's happening:
- Connects the ADK agent to the Composio MCP endpoint through McpToolset
- Uses Gemini as the model powering the agent
- Lists exact tool names in instruction to reduce misnamed tool calls
```python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Helpwise operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

### 8. Run the agent

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.
What's happening:
- adk run runs the agent in CLI mode
- adk web . opens a web UI for interactive testing
```bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
```

## Complete Code

```python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["helpwise"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Helpwise operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

## Conclusion

You've successfully integrated Helpwise with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Helpwise using natural language commands.
Key takeaways:
- The Tool Router approach dynamically routes requests to the appropriate Helpwise tools
- Environment variables keep your credentials secure and separate from code
- Clear agent instructions reduce tool calling errors
- The ADK web UI provides an interactive interface for testing and development
You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

## How to build Helpwise MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/helpwise/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/helpwise/framework/claude-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)
- [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 Google ADK?

Yes, you can. Google ADK 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)