# How to integrate Clientary MCP with Claude Code

```json
{
  "title": "How to integrate Clientary MCP with Claude Code",
  "toolkit": "Clientary",
  "toolkit_slug": "clientary",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/clientary/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/clientary/framework/claude-code.md",
  "updated_at": "2026-03-29T06:27:37.976Z"
}
```

## Introduction

Manage your Clientary 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 Clientary with

- [ChatGPT](https://composio.dev/toolkits/clientary/framework/chatgpt)
- [Antigravity](https://composio.dev/toolkits/clientary/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/clientary/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/clientary/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/clientary/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/clientary/framework/codex)
- [Cursor](https://composio.dev/toolkits/clientary/framework/cursor)
- [VS Code](https://composio.dev/toolkits/clientary/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/clientary/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/clientary/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/clientary/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/clientary/framework/cli)
- [Google ADK](https://composio.dev/toolkits/clientary/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/clientary/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/clientary/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/clientary/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/clientary/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/clientary/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 Clientary to Claude Code

### Connecting Clientary 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 Clientary MCP server, and what's possible with it?

The Clientary MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Clientary account. It provides structured and secure access so your agent can perform Clientary operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CLIENTARY_CREATE_CLIENT` | Create Client | Tool to create a new client record in Clientary. Use when you need to add a new client to the system with company details and contact information. |
| `CLIENTARY_CREATE_CONTACT` | Create Contact | Tool to create a new contact within a specified client. Use when you need to add a contact to a client account with name and email as required fields. |
| `CLIENTARY_CREATE_EXPENSE` | Create Expense | Tool to create a new expense record in Clientary to track expenditures within your account. Use when you need to record expenses, optionally assigning them to specific clients or projects. Requires an amount field. |
| `CLIENTARY_CREATE_LEAD` | Create Lead | Tool to create a new lead record in Clientary. Use when you need to add a new lead to the system with company details and contact information. |
| `CLIENTARY_CREATE_PROJECT` | Create Project | Tool to create a new project in Clientary with name and rate. Use when you need to set up a new project for tracking time, expenses, or managing client work. |
| `CLIENTARY_CREATE_TASK` | Create Task | Tool to create a new task in Clientary. Use when you need to create a task with a title, optionally associating it with a project and assignee. |
| `CLIENTARY_DELETE_CLIENT` | Delete Client | Tool to remove a client and all associated projects, invoices, estimates, and contacts. Use when you need to permanently delete a client from Clientary. WARNING: Deletions are permanent and not reversible. |
| `CLIENTARY_DELETE_LEAD` | Delete Lead | Tool to permanently delete a lead and all associated Estimates and Contacts. Use when you need to remove a lead that is no longer needed. Warning: This action is irreversible. |
| `CLIENTARY_DELETE_PAYMENT` | Delete Payment | Tool to remove an existing payment from an invoice. Use when you need to permanently delete a payment record. WARNING: Deletions are permanent and not reversible. |
| `CLIENTARY_DELETE_PAYMENT_PROFILE` | Delete Payment Profile | Tool to remove a specific payment profile from a client's account. Use when you need to delete a payment profile. Note: Client must have an active payment integration with Stripe to manage payment profiles. |
| `CLIENTARY_DELETE_RECURRING_SCHEDULE` | Delete Recurring Schedule | Tool to remove a recurring schedule by its identifier. Use when you need to permanently delete a recurring schedule from Clientary. Once deleted, the recurring schedule will no longer generate periodic invoices. |
| `CLIENTARY_GET_CLIENT` | Get Client | Tool to fetch details for a specific client using its ID. Use when you need to retrieve complete information about a client from Clientary. |
| `CLIENTARY_GET_CONTACT` | Get Contact | Tool to retrieve a single contact by its ID. Use when you need to fetch detailed information about a specific contact from Clientary. |
| `CLIENTARY_GET_ESTIMATE` | Get Estimate | Tool to retrieve details for a single estimate by ID. Use when you need to obtain comprehensive estimate information including line items, tax details, and financial data. |
| `CLIENTARY_GET_EXPENSE` | Get Expense | Tool to retrieve details for a single expense record in Clientary. Use when you need to get specific information about an expense by its unique identifier. |
| `CLIENTARY_GET_HOUR_ENTRY` | Get Hour Entry | Tool to obtain details about a specific time entry in Clientary. Use when you need to retrieve information about a logged hour entry by its unique identifier. |
| `CLIENTARY_GET_INVOICE` | Get Invoice | Tool to retrieve detailed information for a specific invoice by ID. Use when you need to fetch invoice details including line items, payments, tax information, and current status. |
| `CLIENTARY_GET_LEAD` | Get Lead | Tool to retrieve a single lead by its ID. Use when you need to fetch detailed information about a specific lead from Clientary. |
| `CLIENTARY_GET_PROJECT` | Get Project | Tool to retrieve a single project by its identifier. Use when you need to fetch detailed information about a specific project in Clientary. |
| `CLIENTARY_GET_STAFF` | Get Staff | Tool to retrieve a single staff member by their ID. Use when you need to fetch detailed information about a specific staff member from Clientary. |
| `CLIENTARY_GET_TASK` | Get Task | Tool to retrieve a specific task by its ID. Use when you need to fetch detailed information about a task from Clientary. |
| `CLIENTARY_LIST_CLIENT_CONTACTS` | List Client Contacts | Tool to retrieve all contacts for a specific client with pagination support. Use when you need to fetch the list of contacts associated with a particular client in Clientary. |
| `CLIENTARY_LIST_CLIENT_EXPENSES` | List Client Expenses | Tool to retrieve all expenses for a specific client within an optional date range. Use when you need to fetch expense records associated with a particular client from Clientary. |
| `CLIENTARY_LIST_CLIENT_INVOICES` | List Client Invoices | Tool to retrieve all invoices for a specific client with pagination support (30 results per page). Use when you need to fetch invoices associated with a particular client from Clientary. |
| `CLIENTARY_LIST_CLIENT_PROJECTS` | List Client Projects | Tool to retrieve all projects associated with a specific client with pagination support (10 results per page). Use when you need to fetch projects for a particular client from Clientary. |
| `CLIENTARY_LIST_CLIENTS` | List Clients | Tool to retrieve all clients with pagination support (10 results per page). Use when you need to fetch a list of clients from Clientary with optional filtering by modification date or custom sorting. |
| `CLIENTARY_LIST_EXPENSES` | List Expenses | Tool to retrieve expenses by date range (defaults to current fiscal year). Use when you need to fetch a list of expenses from Clientary with optional filtering by start and end dates. |
| `CLIENTARY_LIST_LEADS` | List Leads | Tool to retrieve all leads with pagination support. Use when you need to fetch a list of leads from Clientary with optional sorting by name or date. |
| `CLIENTARY_LIST_PAYMENTS` | List Payments | Tool to retrieve all payments with pagination support (30 results per page). Use when you need to fetch a list of payments from Clientary with optional pagination and custom sorting. |
| `CLIENTARY_LIST_PROJECT_ESTIMATES` | List Project Estimates | Tool to retrieve estimates scoped to a particular project with pagination support (30 results per page). Use when you need to fetch all estimates associated with a specific project. |
| `CLIENTARY_LIST_PROJECT_EXPENSES` | List Project Expenses | Tool to retrieve all expenses for a specific project within an optional date range. Use when you need to fetch expense records associated with a particular project from Clientary. |
| `CLIENTARY_LIST_PROJECT_HOURS` | List Project Hours | Tool to retrieve all time tracking entries logged against a specific project. Use when you need to fetch hour entries for a particular project, optionally filtering by billed or unbilled status. |
| `CLIENTARY_LIST_PROJECT_INVOICES` | List Project Invoices | Tool to retrieve all invoices linked to a specific project with pagination support (30 results per page). Use when you need to fetch invoices associated with a particular project from Clientary. |
| `CLIENTARY_LIST_PROJECTS` | List Projects | Tool to retrieve all projects with pagination support (10 results per page). Use when you need to fetch a list of projects from Clientary with optional filtering for closed projects. |
| `CLIENTARY_LIST_STAFF` | List Staff | Tool to retrieve all staff members for an account. Use when you need to fetch a complete list of staff members from Clientary. |
| `CLIENTARY_LIST_TASKS` | List Tasks | Tool to retrieve all tasks with pagination support (50 results per page). Use when you need to fetch a list of tasks from Clientary. |
| `CLIENTARY_SEND_INVOICE_MESSAGE` | Send Invoice Message | Tool to send an invoice message to recipients via email. Use when you need to email an invoice to clients with customizable subject, message content, and options to send a copy to yourself or attach a PDF. |
| `CLIENTARY_UPDATE_CLIENT` | Update Client | Tool to update an existing client record in Clientary with partial or complete field modifications. Use when you need to modify client details such as name, address, description, or custom fields. All fields except ID are optional. |
| `CLIENTARY_UPDATE_EXPENSE` | Update Expense | Tool to update an existing expense record in Clientary with partial or complete field modifications. Use when you need to modify expense details such as amount, description, client assignment, project assignment, or incurred date. All fields except ID are optional. |
| `CLIENTARY_UPDATE_HOUR_ENTRY` | Update Hour Entry | Tool to modify an existing time entry in Clientary with partial or complete field updates. Use when you need to update hours, title, date, description, rate, or billing status of a logged hour entry. |
| `CLIENTARY_UPDATE_PROJECT` | Update Project | Tool to update an existing project in Clientary with partial or complete field modifications. Use when you need to modify project details such as name, rate, description, budget, status, or other project attributes. All fields except ID are optional - only provided fields will be updated. |
| `CLIENTARY_UPDATE_TASK` | Update Task | Tool to update an existing task in Clientary with partial or complete field modifications. Use when you need to modify task details such as title, description, completion status, assignee, or due date. All fields except ID are optional. |

## Supported Triggers

None listed.

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

The Clientary 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 Clientary account. It provides structured and secure access so Claude can perform Clientary 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 Clientary 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=["clientary"],
)

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 clientary-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: ['clientary'],
});

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 clientary-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 Clientary 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 (clientary-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 clientary-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 Clientary MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your clientary-composio entry in the list
- This confirms that Claude Code can now access Clientary tools
If everything is wired up, you should see your clientary-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Clientary

The first time you try to use Clientary tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Clientary
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Clientary authorization flow
- Return to the terminal and start using Clientary through Claude Code
Once authenticated, you can ask Claude Code to perform Clientary operations in natural language. For example:
- "Create new invoice for a client"
- "List all active projects this month"
- "Send payment reminder to overdue clients"

## 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=["clientary"],
)

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 clientary-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: ['clientary'],
});

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 clientary-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Clientary with Claude Code using Composio's MCP server. Now you can interact with Clientary directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Clientary 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 Clientary 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 Clientary MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/clientary/framework/chatgpt)
- [Antigravity](https://composio.dev/toolkits/clientary/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/clientary/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/clientary/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/clientary/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/clientary/framework/codex)
- [Cursor](https://composio.dev/toolkits/clientary/framework/cursor)
- [VS Code](https://composio.dev/toolkits/clientary/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/clientary/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/clientary/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/clientary/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/clientary/framework/cli)
- [Google ADK](https://composio.dev/toolkits/clientary/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/clientary/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/clientary/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/clientary/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/clientary/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/clientary/framework/crew-ai)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place.
- [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently.
- [Stripe](https://composio.dev/toolkits/stripe) - Stripe is a global online payments platform offering APIs for managing payments, customers, and subscriptions. Trusted by businesses for secure, efficient, and scalable payment processing worldwide.
- [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [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.
- [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities.
- [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place.

## Frequently Asked Questions

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

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

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

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

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