# How to integrate Agencyzoom MCP with LlamaIndex

```json
{
  "title": "How to integrate Agencyzoom MCP with LlamaIndex",
  "toolkit": "Agencyzoom",
  "toolkit_slug": "agencyzoom",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/agencyzoom/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/agencyzoom/framework/llama-index.md",
  "updated_at": "2026-05-12T10:00:22.481Z"
}
```

## Introduction

This guide walks you through connecting Agencyzoom to LlamaIndex using the Composio tool router. By the end, you'll have a working Agencyzoom agent that can add a note to a specific customer profile, batch create five new insurance leads, change the status of a lead to won through natural language commands.
This guide will help you understand how to give your LlamaIndex agent real control over a Agencyzoom account through Composio's Agencyzoom MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Agencyzoom with

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

## TL;DR

Here's what you'll learn:
- Set your OpenAI and Composio API keys
- Install LlamaIndex and Composio packages
- Create a Composio Tool Router session for Agencyzoom
- Connect LlamaIndex to the Agencyzoom MCP server
- Build a Agencyzoom-powered agent using LlamaIndex
- Interact with Agencyzoom through natural language

## What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.
Key features include:
- ReAct Agent: Reasoning and acting pattern for tool-using agents
- MCP Tools: Native support for Model Context Protocol
- Context Management: Maintain conversation context across interactions
- Async Support: Built for async/await patterns

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

The Agencyzoom MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Agencyzoom account. It provides structured and secure access to your agency's sales and client management data, so your agent can create leads, manage tasks, update opportunities, take notes, and analyze performance automatically on your behalf.
- Batch contact and lead creation: Quickly add multiple new contacts or leads to your Agencyzoom CRM in a single step to keep your pipeline growing efficiently.
- Automated task management: Let your agent mark tasks as completed or delete batches of tasks, helping your team stay organized and focused on priorities.
- Lead status and opportunity updates: Easily update a lead's lifecycle status or add new sales opportunities, enabling your sales process to move forward without manual intervention.
- Intelligent note-taking: Add detailed notes to customer profiles or leads automatically, ensuring important context is always captured and accessible.
- Opportunity driver management: Create and associate driver records with opportunities to maintain complete and compliant records for insurance sales workflows.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `AGENCYZOOM_AUTHENTICATE_FOR_JWTVIA_V4_SSO` | Authenticate for JWT via V4 SSO | Completes AgencyZoom V4 Single Sign-On (SSO) authentication by exchanging an OAuth2 authorization code for a JWT token. Prerequisites: First call get_auth_url_for_v4sso to obtain the authentication URL, then redirect the user to that URL for login. After successful authentication through Vertafore's OAuth provider, the callback will include a 'code' parameter. Use that code with this action to obtain the JWT token for API access. Note: This is typically used during initial authentication setup. The code is single-use, time-limited, and must match the PKCE challenge from the original auth request. |
| `AGENCYZOOM_BATCH_CREATE_CONTACT` | Batch create contacts | Creates 1 to 5 new contacts in AgencyZoom in a single batch API call. |
| `AGENCYZOOM_BATCH_CREATE_LEAD` | Batch create leads | Creates up to 5 new leads in AgencyZoom; all referenced entity IDs (e.g., pipeline, user, custom field names) must exist, and organization `name` is required if `isBusiness` is true. |
| `AGENCYZOOM_BATCH_DELETE_TASK` | Batch delete tasks | Deletes multiple AgencyZoom tasks in a batch; task deletion is permanent and the response indicates overall batch success, not individual task status. |
| `AGENCYZOOM_CHANGE_STATUS_FOR_LEAD` | Change lead status | Updates a lead's lifecycle status (e.g., Active, Won, Lost, X-Dated) and can optionally manage its workflow, pipeline, stage, source, or associated tags. |
| `AGENCYZOOM_COMPLETE_TASK` | Mark task as completed | Marks an existing and accessible task in AgencyZoom as 'completed'; this action does not return the full updated task object. |
| `AGENCYZOOM_CREATE_A_CUSTOMER_NOTE` | Create a customer note | Adds a new note to an existing customer's profile using their ID; cannot be used to edit or retrieve existing notes. |
| `AGENCYZOOM_CREATE_A_DRIVER_FOR_AN_OPPORTUNITY` | Create a driver for an opportunity | Creates a new driver record associated with an existing AgencyZoom opportunity using its ID; requires firstName and lastName, with optional fields for additional driver details. |
| `AGENCYZOOM_CREATE_A_LEAD_NOTE` | Create a lead note | Adds a new note to an existing lead in AgencyZoom, identified by `leadId`. |
| `AGENCYZOOM_CREATE_A_LEAD_OPPORTUNITY` | Create a lead opportunity | Adds a new sales opportunity to an existing lead in AgencyZoom, requiring a valid `leadId`, `carrierId`, `productLineId`, and that custom field names match existing definitions in AgencyZoom. |
| `AGENCYZOOM_CREATE_A_LEAD_QUOTE` | Create a lead quote | Creates a new insurance quote for an existing lead in AgencyZoom, using valid carrier and product line IDs, to track a proposal; this action does not bind policies or process payments. |
| `AGENCYZOOM_CREATE_AN_OPPORTUNITY` | Create an opportunity | Creates a new lead opportunity in AgencyZoom; this action cannot update existing opportunities. |
| `AGENCYZOOM_CREATE_A_VEHICLE_FOR_AN_OPPORTUNITY` | Create a vehicle for an opportunity | Adds a new vehicle record to a specified opportunity; `opportunityId` must refer to a valid, existing opportunity. |
| `AGENCYZOOM_CREATE_BIZ_LEAD` | Create business lead | Creates or updates a business lead in AgencyZoom using detailed personal and company information, for B2B sales and marketing lead management. |
| `AGENCYZOOM_CREATE_LEAD` | Create lead | Creates a new lead or updates an existing one in AgencyZoom; ensure `pipelineId`, `stageId`, `leadSourceId`, and `assignTo` reference valid, existing entities. |
| `AGENCYZOOM_CREATE_TASK` | Create task post endpoint | Creates a new task in AgencyZoom; ensure `assigneeId`, `customerId`, or `leadId` are valid existing entities if provided, and use `contactEmail`, `customerId`, or `leadId` to link the task to a contact. |
| `AGENCYZOOM_DELETE_A_CUSTOMER` | Delete a customer | Irreversibly deletes a customer and all associated data in AgencyZoom using their `customerId`; useful for offboarding or data privacy compliance. |
| `AGENCYZOOM_DELETE_A_CUSTOMER_FILE` | Delete customer file | Permanently deletes a specific file, identified by `fileId`, associated with a customer, identified by `customerId`. |
| `AGENCYZOOM_DELETE_A_CUSTOMER_POLICY` | Delete a customer policy | Permanently deletes a specific policy associated with a customer, for instance, if it's cancelled or inactive; this action is irreversible and requires caution. |
| `AGENCYZOOM_DELETE_A_DRIVER` | Delete an opportunity driver by ID | Permanently deletes an existing driver record (a person associated with an insurance opportunity) from AgencyZoom using its unique `driverId`; this action is irreversible. |
| `AGENCYZOOM_DELETE_A_LEAD_FILE` | Delete file from lead | Deletes a specific file (identified by `fileId`) associated with an existing lead (identified by `leadId`); this operation is irreversible. |
| `AGENCYZOOM_DELETE_A_LEAD_OPPORTUNITY` | Delete a lead opportunity | Permanently deletes an existing opportunity (by `opportunityId`) associated with an existing lead (by `leadId`) when it's irrelevant, closed, or erroneous; the lead itself remains. |
| `AGENCYZOOM_DELETE_A_LEAD_QUOTE` | Delete a lead quote | Deletes a specific quote from a lead, requiring that the lead and quote exist and are associated. |
| `AGENCYZOOM_DELETE_AN_OPPORTUNITY` | Delete an opportunity | Permanently deletes a specific opportunity by its unique ID; this action is irreversible and requires a valid, existing `opportunityId`. |
| `AGENCYZOOM_DELETE_A_TASK` | Delete a task | Permanently and irreversibly deletes an existing task, identified by its `taskId`. |
| `AGENCYZOOM_DELETE_A_VEHICLE` | Delete a vehicle | Permanently deletes a vehicle record by its `vehicleId`, which must correspond to an existing vehicle in the AgencyZoom system. |
| `AGENCYZOOM_DELETE_MESSAGE` | Delete thread message | Deletes a specific message from an email thread within AgencyZoom. Requires the message ID to identify which message to remove. Returns the updated thread information with the remaining messages after deletion. |
| `AGENCYZOOM_DELETE_THREAD` | Delete email thread | Permanently deletes a specific email thread from the AgencyZoom system, identified by its `threadId` (expected by the endpoint), provided the thread exists. |
| `AGENCYZOOM_GET_A_LIST_OF_ASSIGN_GROUPS` | Get a list of assign groups | Retrieves all assign groups configured in AgencyZoom, used for categorizing or assigning items to specific teams or units. |
| `AGENCYZOOM_GET_A_LIST_OF_CARRIERS` | Get a list of carriers | Retrieves all insurance carriers from AgencyZoom, typically used for populating selection lists or synchronizing carrier data; does not return detailed policy or coverage information. |
| `AGENCYZOOM_GET_A_LIST_OF_CSRS` | Get a list of CSRs | Fetches all Customer Service Representatives (CSRs), including their ID and name, returning an empty list if none are configured. |
| `AGENCYZOOM_GET_A_LIST_OF_CUSTOM_FIELDS` | Get a list of custom fields | Retrieves metadata for all configured custom field definitions, not the specific values entered for individual records. |
| `AGENCYZOOM_GET_A_LIST_OF_DRIVERS_FOR_AN_OPPORTUNITY` | Get a list of drivers for an opportunity | Retrieves a list of drivers (individuals), including their personal details, licensing information, and relationship status, associated with a specific, existing `opportunityId` in AgencyZoom. |
| `AGENCYZOOM_GET_A_LIST_OF_EMPLOYEES` | Get a list of employees | Retrieves a complete list of all employees for the authenticated agency; returns an empty list if no employees are configured. |
| `AGENCYZOOM_GET_A_LIST_OF_LEAD_SOURCE_CATEGORIES` | Get lead source categories | Retrieves a comprehensive list of all predefined lead source categories from AgencyZoom, used to classify lead origins. |
| `AGENCYZOOM_GET_A_LIST_OF_LEAD_SOURCES` | Get lead sources | Fetches a list of all lead sources configured in AgencyZoom, including their ID, name, sales exclusion status, and category ID. |
| `AGENCYZOOM_GET_A_LIST_OF_LIFE_PROFESSIONALS` | Get a list of life professionals | Retrieves a list of life insurance professionals, including only their contact and status information (excluding sales or customer data), from the AgencyZoom platform. |
| `AGENCYZOOM_GET_A_LIST_OF_LOCATIONS` | Get a list of locations | Retrieves all agency locations or branches from AgencyZoom; filtering options are not available. |
| `AGENCYZOOM_GET_A_LIST_OF_LOSS_REASONS` | Get loss reasons | Retrieves all predefined loss reasons (e.g., 'Lost to competitor', 'Premium too high') available in AgencyZoom. These reasons can be used when marking leads as lost or for reporting purposes. No parameters required - returns complete list. |
| `AGENCYZOOM_GET_A_LIST_OF_PIPELINES` | Get a list of pipelines | Retrieves all pipelines and their stages from AgencyZoom to understand workflow structures; this is a read-only operation and does not return individual items (like leads or tasks) within these pipelines. |
| `AGENCYZOOM_GET_A_LIST_OF_PRODUCER` | Get a list of producers | Retrieves a list of all producers from AgencyZoom, typically related to text thread functionalities. |
| `AGENCYZOOM_GET_A_LIST_OF_PRODUCT_LINES_POLICY_TYPES` | Get product lines and policy types | Fetches all product lines and policy types from AgencyZoom, each detailed with its ID, name, and product category ID. |
| `AGENCYZOOM_GET_A_LIST_OF_RECYCLE_EVENTS` | Get a list of recycle events | Retrieves the available recycle event types and any existing X-Date information for a specified lead in AgencyZoom. Returns a list of recycle event categories that can be used to trigger follow-ups (e.g., 'X-Date', 'Accident Falls Off', 'Prior Insurance Fulfilled'). |
| `AGENCYZOOM_GET_A_LIST_OF_VEHICLES_FOR_AN_OPPORTUNITY` | Retrieve vehicles for opportunity | Retrieves all vehicles associated with an existing opportunity, using its unique opportunityId. |
| `AGENCYZOOM_GET_AMS_POLICIES_FOR_A_CUSTOMER` | Get AMS policies for a customer | Retrieves a customer's synchronized Agency Management System (AMS) policy data (typically a single policy); requires an active AMS integration, may return empty/default values if data is missing. |
| `AGENCYZOOM_GET_AUTH_URL_FOR_V4_SSO` | Get auth URL for V4 SSO | Retrieves a fresh authentication URL for AgencyZoom's V4 Single Sign-On (SSO) process; call before each SSO attempt as the URL may change and should not be cached. |
| `AGENCYZOOM_GET_DEPARTMENTS_GROUPS` | Get departments groups | Fetches department and group information for an agency, optionally filtered by a specific `agencyNumber`, to analyze its organizational structure. |
| `AGENCYZOOM_GET_LEAD_FILES` | Get lead files | Retrieves metadata (id, title, MIME type, size, dates, creator info) for files attached to leads in AgencyZoom. Optionally filter by `leadId` to get files for a specific lead, or omit to retrieve files across all leads. Returns file metadata only, not the actual file content. |
| `AGENCYZOOM_GET_LEAD_NOTES` | Retrieve notes for specific lead | Fetches the complete history of notes for a specific lead by `leadId` (which must exist), useful for reviewing context for communications or follow-ups; this is a read-only operation. |
| `AGENCYZOOM_GET_LEAD_QUOTES` | Get lead quotes | Retrieves all insurance quotes (active and inactive) for a specific lead ID, useful for reviewing or tracking quote history. |
| `AGENCYZOOM_GET_LEAD_TASKS` | Get lead tasks | Retrieves all tasks for a specific lead, identified by its `leadId`, to review its activity history or manage follow-ups. |
| `AGENCYZOOM_GET_LIST_OF_END_STAGES` | Get list of end stages | Fetches a list of all defined end stages, representing final steps in processes like lead conversion or policy closure. |
| `AGENCYZOOM_GET_POLICIES_FOR_A_CUSTOMER` | Get policies for a customer | Retrieves from AgencyZoom all insurance policies for an existing customer (identified by `customerId`), including policy details like type, carrier, premium, effective dates, and assigned agents. Excludes premium payment history or claims information. |
| `AGENCYZOOM_GET_THE_CUSTOMER_DETAILS` | Get the customer details | Fetches comprehensive details for a specific customer, including personal information, policies, notes, tasks, files, and custom fields, using their unique customer ID. |
| `AGENCYZOOM_GET_THE_CUSTOMER_TASKS` | Get the customer tasks | Fetches all tasks (read-only task data) for a customer by `customerId` to review their activities, follow-ups, and action items; the `customerId` must be valid. |
| `AGENCYZOOM_GET_THE_DRIVER_DETAILS` | Get the driver details | Retrieves detailed information for a specific, existing driver (by `driverId`) associated with an AgencyZoom opportunity. |
| `AGENCYZOOM_GET_THE_LEAD_DETAILS` | Get the lead details | Retrieves comprehensive details for a specific lead in AgencyZoom by its unique `leadId` (which must correspond to an existing lead), including contact information, status, associated opportunities, quotes/policies, custom fields, and interaction history. |
| `AGENCYZOOM_GET_THE_OPPORTUNITIES_FOR_A_LEAD` | Get the opportunities for a lead | Retrieves all sales opportunities and their details for a specified, existing `leadId` in AgencyZoom. |
| `AGENCYZOOM_GET_THE_OPPORTUNITY_DETAILS` | Get the opportunity details | Fetches comprehensive details for an existing opportunity using its unique `opportunityId`. |
| `AGENCYZOOM_GET_THE_TASK_DETAILS` | Get the task details | Retrieves comprehensive details for a specific task using its unique `taskId`, which must correspond to an existing task in AgencyZoom. |
| `AGENCYZOOM_GET_THE_VEHICLE_DETAILS` | Get the vehicle details | Retrieves detailed information for a specific vehicle, often associated with an AgencyZoom opportunity, using its unique vehicleId. |
| `AGENCYZOOM_GET_THREAD_DETAILS` | Get thread details | Searches and retrieves detailed information for email threads in AgencyZoom; no explicit search criteria are passed in this request. |
| `AGENCYZOOM_LINK_A_DRIVER_TO_OPPORTUNITY` | Link a driver to opportunity | Assigns or reassigns an existing driver to an existing opportunity. |
| `AGENCYZOOM_LINK_A_VEHICLE_TO_OPPORTUNITY` | Link vehicle to opportunity | Links an existing vehicle to an existing sales opportunity in AgencyZoom using their respective IDs, typically for managing auto insurance policies or related services. |
| `AGENCYZOOM_LIST_PRODUCT_CATEGORIES` | List Product Categories | Retrieves a complete, unfiltered list of all product categories (ID and name) from AgencyZoom, useful for understanding product organization or populating UI elements. |
| `AGENCYZOOM_LOG_THE_USER_IN` | Log the user in | Authenticates an existing AgencyZoom user using their email (as username) and password to obtain a JWT for API access; this action does not support new user creation. |
| `AGENCYZOOM_LOG_THE_USER_OUT` | Log the user out | Use this action to log the current user out of AgencyZoom by invalidating their active session token. |
| `AGENCYZOOM_MARK_THREAD_AS_UNREAD_API_ENDPOINT` | Mark thread as unread | Marks a text thread in AgencyZoom as read or unread using its `threadId`; this action does not modify message content and the specified `threadId` must refer to an existing thread. |
| `AGENCYZOOM_MOVE_LEAD_TO_SOLD` | Move lead to sold | Marks an existing lead as sold by its `leadId` and records product details; `productLineId`, `premium`, `effectiveDate`, and `soldDate` are operationally required for each sold product, despite schema flexibility. |
| `AGENCYZOOM_REMOVE_TEXT_THREAD_ENDPOINT` | Remove text thread | Call this action to permanently delete an SMS/text message thread in AgencyZoom; the target thread is identified by its `threadId`. Note: This operation is idempotent - deleting a non-existent thread will return success. |
| `AGENCYZOOM_REOPEN_A_TASK` | Reopen a task | Reopens an existing AgencyZoom task that is currently 'completed' or 'closed', allowing it to be reactivated with optional comments. |
| `AGENCYZOOM_SEARCH_BUSINESS_CLASSIFICATIONS` | Search business classifications | Retrieves a comprehensive list of all available business classifications from AgencyZoom, each including an ID, code, and description. |
| `AGENCYZOOM_SEARCH_CUSTOMERS` | Search customers | Searches for customers in AgencyZoom using criteria like contact information, policy details, or custom fields, with options for filtering, sorting, and pagination. |
| `AGENCYZOOM_SEARCH_EMAIL_THREADS` | Search email threads | Retrieves a list of email thread metadata from AgencyZoom, suitable for an overview when no specific filtering, sorting, or pagination is needed, as results are subject to default server-side limits and ordering. |
| `AGENCYZOOM_SEARCH_LEADS` | Search leads | Retrieves AgencyZoom leads, using filters, pagination, and sorting options sent in the POST body, as the request schema itself is empty. |
| `AGENCYZOOM_SEARCH_LEADS_COUNT` | Search leads count | Retrieves a summary of lead counts categorized by workflow stage from AgencyZoom; this action does not support filtering and returns aggregate counts rather than individual lead details. |
| `AGENCYZOOM_SEARCH_LIFE_AND_HEALTH_LEADS` | Search life and health leads | Searches for life and health insurance leads by providing filter criteria (matching AlrLead fields) in the request body; an empty request may retrieve all leads or a default set. |
| `AGENCYZOOM_SEARCH_SMS_THREADS` | Search SMS threads | Searches and retrieves SMS threads from AgencyZoom, with search parameters, filters, sorting, and pagination typically provided in the request body of this POST operation. |
| `AGENCYZOOM_SEARCH_TASKS` | Search and list tasks | Searches and lists tasks, supporting pagination and accepting filter criteria in the POST request body despite an empty request schema. |
| `AGENCYZOOM_SERVICE_TICKET_LIST` | List service tickets | Retrieves a paginated list of service tickets from AgencyZoom. Supports filtering by: - Status (0=removed, 1=active, 2=completed) - Priority ID and Category ID Returns service ticket details including subject, description, dates, assignment information, and workflow stage. Results are paginated with default page size of 20 tickets per page. |
| `AGENCYZOOM_TEXT_DETAIL_THREAD` | Get SMS thread messages | Retrieves detailed messages for a specific SMS/text thread by its thread ID. Returns all messages in the thread with their content, attachments, sender/recipient information, and metadata. The thread ID can be obtained from the search_sms_threads action. |
| `AGENCYZOOM_UNLINK_A_DRIVER_FROM_OPPORTUNITY` | Unlink driver from opportunity | Unlinks a currently associated driver from an AgencyZoom opportunity, used when the driver is no longer relevant, for policy or data updates, potentially impacting the opportunity's status or associated policy details. |
| `AGENCYZOOM_UNLINK_A_VEHICLE_FROM_OPPORTUNITY` | Unlink vehicle from opportunity | Unlinks a specific, existing vehicle from a specific, existing opportunity using their respective IDs, removing only the association and not the records themselves. |
| `AGENCYZOOM_UNREAD_THREAD` | Update email thread read status | Updates the read or unread status of a specific email thread within AgencyZoom. |
| `AGENCYZOOM_UPDATE_A_DRIVER_S_DETAILS` | Update a driver's details | Updates an existing driver's details in AgencyZoom, requiring `driverId` in the path and `firstName` and `lastName` in the request. |
| `AGENCYZOOM_UPDATE_A_LEAD_FILE_NAME` | Rename lead file | Updates a lead's file name to `newFileName`; requires `fileId` of the target file, which must be associated with both the `leadId` (path parameter) and the provided `customerReferralId`. |
| `AGENCYZOOM_UPDATE_A_LEAD_OPPORTUNITY` | Update a lead opportunity | Updates an existing opportunity's details (carrier, product line, premium, items, custom fields) for a specific lead; `leadId`, opportunity `id`, `carrierId`, and `productLineId` must refer to existing entities. |
| `AGENCYZOOM_UPDATE_A_LEAD_QUOTE` | Update lead quote data | Updates an existing quote for a specified lead in AgencyZoom when its details require revision, ensuring the provided `leadId` (path parameter), quote `id` (body parameter), `carrierId`, and `productLineId` are valid and correspond to existing entities. |
| `AGENCYZOOM_UPDATE_AN_OPPORTUNITY` | Update an opportunity | Updates an existing opportunity with the provided details; ensure any custom field names are predefined in AgencyZoom configuration. |
| `AGENCYZOOM_UPDATE_A_POLICY` | Update policy by id | Updates an existing insurance policy for the given `policyId`; monetary values must be in cents and dates in YYYY-MM-DD format. |
| `AGENCYZOOM_UPDATE_A_VEHICLE_S_DETAILS` | Update a vehicle's details | Updates details for an existing vehicle within an opportunity; this action cannot be used to create new vehicle records. |
| `AGENCYZOOM_UPDATE_BUSINESS_LEAD` | Update business lead | Updates an existing business lead in AgencyZoom. Requires leadId (path parameter) plus core business information fields: firstname, email, name (business name), pipelineId, stageId, leadSourceId, assignTo (producer ID), and country. All other fields are optional and will only update if provided. |
| `AGENCYZOOM_UPDATE_CUSTOMER` | Update customer info using id | Updates an existing customer's information in AgencyZoom using their unique customerId. |
| `AGENCYZOOM_UPDATE_LEAD` | Update lead | Updates an existing lead's information in AgencyZoom using the `leadId`; ensure the `leadId` corresponds to an existing lead in AgencyZoom. |
| `AGENCYZOOM_UPDATE_LEAD_STATUS_BY_ID` | Update lead status by id | Updates a lead's status (0=ACTIVE, 2=WON, 3=LOST, 5=XDATED) by `leadId`, optionally setting workflow, stage, date, loss reason, X-date type, source, recycle stage/pipeline, or tags; requires `date` and `xDateType` for status 5 (XDATED), and `lossReasonId` for status 3 (LOST). |
| `AGENCYZOOM_UPDATE_MY_PROFILE` | Update my profile | Updates the profile information (first name, last name, email, and optional phone) for the currently authenticated user in AgencyZoom; the provided email address must be unique within the system. |
| `AGENCYZOOM_UPDATE_TAGS_FOR_A_POLICY` | Add tags to a policy | Adds new comma-separated `tagNames` to a policy, requiring `tagNames` and identification by either `policyId` or `amsPolicyId`; if `amsPolicyId` is provided, `policyId` is ignored, and existing tags are not affected. |
| `AGENCYZOOM_UPDATE_TASK` | Update task | Modifies an existing AgencyZoom task (which must be valid and identified by `taskId` in the path) with new attributes from the request body, which must also contain `taskId`. |
| `AGENCYZOOM_V4_SSO_LOG_THE_USER_IN` | Log user in via SSO | Logs a user into the AgencyZoom platform via Single Sign-On (SSO). Returns JWT on success or error details on authentication failure. |

## Supported Triggers

None listed.

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

The Agencyzoom MCP server is an implementation of the Model Context Protocol that connects your AI agent to Agencyzoom. It provides structured and secure access so your agent can perform Agencyzoom 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 you begin, make sure you have:
- Python 3.8/Node 16 or higher installed
- A Composio account with the API key
- An OpenAI API key
- A Agencyzoom account and project
- Basic familiarity with async Python/Typescript

### 1. Getting API Keys for OpenAI, Composio, and Agencyzoom

No description provided.

### 2. Installing dependencies

No description provided.
```python
pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv
```

```typescript
npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv
```

### 3. Set environment variables

Create a .env file in your project root:
These credentials will be used to:
- Authenticate with OpenAI's GPT-5 model
- Connect to Composio's Tool Router
- Identify your Composio user session for Agencyzoom access
```bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id
```

### 4. Import modules

No description provided.
```python
import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();
```

### 5. Load environment variables and initialize Composio

No description provided.
```python
OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_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")
```

```typescript
const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");
```

### 6. Create a Tool Router session and build the agent function

What's happening here:
- We create a Composio client using your API key and configure it with the LlamaIndex provider
- We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, agencyzoom)
- The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
- LlamaIndex will connect to this endpoint to dynamically discover and use the available Agencyzoom tools.
- The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
```python
async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["agencyzoom"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Agencyzoom actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Agencyzoom actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)
```

```typescript
async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

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

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["agencyzoom"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Agencyzoom actions." ,
    llm,
    tools,
  });

  return agent;
}
```

### 7. Create an interactive chat loop

No description provided.
```python
async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")
```

```typescript
async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}
```

### 8. Define the main entry point

What's happening here:
- We're orchestrating the entire application flow
- The agent gets built with proper error handling
- Then we kick off the interactive chat loop so you can start talking to Agencyzoom
```python
async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")
```

```typescript
async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();
```

### 9. Run the agent

When prompted, authenticate and authorise your agent with Agencyzoom, then start asking questions.
```bash
python llamaindex_agent.py
```

```typescript
npx ts-node llamaindex-agent.ts
```

## Complete Code

```python
import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

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

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["agencyzoom"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Agencyzoom actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Agencyzoom actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

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

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["agencyzoom"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Agencyzoom actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();
```

## Conclusion

You've successfully connected Agencyzoom to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Agencyzoom tools through an MCP endpoint
- LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
- The agent becomes more capable without increasing prompt size
- Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

## How to build Agencyzoom MCP Agent with another framework

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

## Related Toolkits

- [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.
- [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.
- [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.
- [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.
- [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.
- [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.
- [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources.
- [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations.
- [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface.
- [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently.
- [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place.
- [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.
- [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools.
- [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data.
- [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place.
- [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process.
- [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools.
- [Firmao](https://composio.dev/toolkits/firmao) - Firmao is a business information platform offering company, industry, and market data. Use it to quickly research firms and gain competitive market insights.

## Frequently Asked Questions

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

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

### Can I use Tool Router MCP with LlamaIndex?

Yes, you can. LlamaIndex 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 Agencyzoom tools.

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

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

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