# How to integrate Chmeetings MCP with LlamaIndex

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

## Introduction

This guide walks you through connecting Chmeetings to LlamaIndex using the Composio tool router. By the end, you'll have a working Chmeetings agent that can list upcoming church events this month, add new member to youth group, record a donation from a churchgoer through natural language commands.
This guide will help you understand how to give your LlamaIndex agent real control over a Chmeetings account through Composio's Chmeetings MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Chmeetings with

- [OpenAI Agents SDK](https://composio.dev/toolkits/chmeetings/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/chmeetings/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/chmeetings/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/chmeetings/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/chmeetings/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/chmeetings/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/chmeetings/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/chmeetings/framework/cli)
- [Google ADK](https://composio.dev/toolkits/chmeetings/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/chmeetings/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/chmeetings/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/chmeetings/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/chmeetings/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 Chmeetings
- Connect LlamaIndex to the Chmeetings MCP server
- Build a Chmeetings-powered agent using LlamaIndex
- Interact with Chmeetings 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 Chmeetings MCP server, and what's possible with it?

The Chmeetings MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Chmeetings account. It provides structured and secure access to your church management system, so your agent can help you manage events, engage members, track donations, coordinate volunteers, and oversee groups on your behalf.
- Event planning and scheduling: Empower your agent to create, update, and manage church events, including setting dates, venues, and attendee lists.
- Member engagement and communication: Let your agent access member directories, send announcements, and track participation to boost overall community involvement.
- Donation management and reporting: Easily have your agent track contributions, generate donation reports, and assist with financial record-keeping.
- Volunteer coordination: Allow your agent to organize volunteer opportunities, assign roles, and monitor participation for various church activities.
- Group and ministry oversight: Ask your agent to manage groups or ministries, enroll members, and keep information up-to-date for effective administration.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CHMEETINGS_ATTENDEE_CREATE` | Invite Meeting Attendee | Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins. |
| `CHMEETINGS_ATTENDEE_GET` | Get Attendee Details | Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile. |
| `CHMEETINGS_CREATE_MEETING` | ChMeetings: Create Meeting | Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API. |
| `CHMEETINGS_CREATE_ORGANIZATION` | ChMeetings: Create Organization | Tool to create a new organization. |
| `CHMEETINGS_CREATE_REMINDER` | ChMeetings: Create Reminder | Tool to create/schedule a reminder for a meeting in ChMeetings. |
| `CHMEETINGS_DELETE_MEETING_ATTENDEE` | Delete Meeting Attendee | Tool to remove an attendee from a meeting. Use after confirming attendee details. |
| `CHMEETINGS_LIST_MEETING_ATTENDEES` | List Meeting Attendees | Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting. |
| `CHMEETINGS_MEETINGS_DELETE` | ChMeetings: Delete Meeting | Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting. |
| `CHMEETINGS_MEETINGS_GET` | ChMeetings: Get Meeting | Tool to retrieve a specific meeting's details by ID. |
| `CHMEETINGS_MEETINGS_UPDATE` | ChMeetings: Update Meeting | Tool to update meeting details. Use when modifying an existing meeting; call after retrieving meeting ID. |
| `CHMEETINGS_NOTIFICATIONS_SEND` | ChMeetings: Send Notification | Tool to attempt sending a notification. |
| `CHMEETINGS_ORGANIZATION_GET` | ChMeetings: Get Organization | Tool to get details of a specific organization. Use when you have confirmed the organization ID and need full organization data. |
| `CHMEETINGS_ORGANIZATIONS_DELETE` | ChMeetings: Delete Organization | Tool to delete an existing organization. Use when you have confirmed the organization ID to permanently remove the organization. |
| `CHMEETINGS_ORGANIZATIONS_LIST` | ChMeetings: List Organizations | Tool to list all organizations. Use when you need to retrieve organization data; no parameters required. |
| `CHMEETINGS_ORGANIZATION_UPDATE` | ChMeetings: Update Organization | Tool to update an organization's information. Use when modifying an existing organization; call after retrieving organization ID. |
| `CHMEETINGS_PEOPLE_DELETE` | ChMeetings: Delete Person | Tool to delete a person record. Use after confirming the person ID you wish to remove. |
| `CHMEETINGS_PEOPLE_LIST` | ChMeetings: List People | Tool to retrieve list of People records from ChMeetings. Use when syncing people data; rate limit 100 requests per 20 seconds. |
| `CHMEETINGS_PEOPLE_UPDATE` | ChMeetings: Update Person | Tool to update an existing person's information in ChMeetings. Use when modifying person details; call after retrieving person ID via CHMEETINGS_PEOPLE_LIST or CHMEETINGS_PEOPLE_GET. Supported update fields (use snake_case): - Personal: first_name, last_name, middle_name, nick_name, native_name, email, mobile, telephone, birth_date - Demographics: gender (Male/Female/Unknown), social_status (Single/Married/etc.) - Professional: job_title, work_place, qualification, education_level, school - Religious: church, baptism_date, baptism_location, is_deacon, rank, bishop_donor - Communication: do_not_text, do_not_email (boolean) - Address: address object with country, state, city, etc. |
| `CHMEETINGS_PERSON_CREATE` | ChMeetings: Create Person | Tool to create a new person record in ChMeetings People directory. Use when you need to add a person before tracking interactions. Required fields: first_name, last_name |
| `CHMEETINGS_PERSON_GET` | ChMeetings: Get Person | Tool to retrieve a specific person's details by ID. Use when you have a person ID and need their full record. |
| `CHMEETINGS_REMINDER_DELETE` | ChMeetings: Delete Reminder | Tool to cancel a scheduled reminder. Use when you have the reminder ID and want to stop it before execution. |
| `CHMEETINGS_REMINDER_GET` | ChMeetings: Get Reminder | Tool to retrieve details of a specific reminder. Use when you have the reminder ID and need its full information. |
| `CHMEETINGS_REMINDERS_LIST` | ChMeetings: List Reminders | Tool to list reminders from ChMeetings. Use when you need to retrieve reminder records; rate limit applies. |
| `CHMEETINGS_REMINDER_UPDATE` | ChMeetings: Update Reminder | Tool to update an existing reminder. Use when adjusting scheduled reminders after creation. |
| `CHMEETINGS_SETTINGS_GET` | ChMeetings: Get Settings | Tool to retrieve account configuration settings. Returns the available lookup values for genders, social statuses, grade levels, and family roles used throughout ChMeetings. Use when you need to know what options are available for creating or updating people and families. |
| `CHMEETINGS_SETTINGS_UPDATE` | ChMeetings: Update Settings | Tool to update account settings. Use when updating account-level preferences after authentication. |
| `CHMEETINGS_UPDATE_ATTENDEE_ROLE` | Update attendee role | Tool to update the role of an attendee. Use when you need to change an existing attendee's role after creation. |
| `CHMEETINGS_USER_PROFILE_GET` | ChMeetings: Get User Profile | Tool to retrieve current user's profile information. Use when you need to get the authenticated user's profile details. |

## Supported Triggers

None listed.

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

The Chmeetings MCP server is an implementation of the Model Context Protocol that connects your AI agent to Chmeetings. It provides structured and secure access so your agent can perform Chmeetings 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 Chmeetings account and project
- Basic familiarity with async Python/Typescript

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

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 Chmeetings 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, chmeetings)
- 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 Chmeetings 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=["chmeetings"],
    )

    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 Chmeetings actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Chmeetings 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: ["chmeetings"],
    },
  );

  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 Chmeetings 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 Chmeetings
```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 Chmeetings, 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=["chmeetings"],
    )

    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 Chmeetings actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Chmeetings 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: ["chmeetings"],
    },
  );

  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 Chmeetings 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 Chmeetings to LlamaIndex through Composio's Tool Router MCP layer.
Key takeaways:
- Tool Router dynamically exposes Chmeetings 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 Chmeetings MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/chmeetings/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/chmeetings/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/chmeetings/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/chmeetings/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/chmeetings/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/chmeetings/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/chmeetings/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/chmeetings/framework/cli)
- [Google ADK](https://composio.dev/toolkits/chmeetings/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/chmeetings/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/chmeetings/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/chmeetings/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/chmeetings/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.
- [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.
- [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.
- [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.
- [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.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management.

## Frequently Asked Questions

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

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

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

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

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