# How to integrate Chmeetings MCP with Autogen

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

## Introduction

This guide walks you through connecting Chmeetings to AutoGen 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 AutoGen 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)
- [LlamaIndex](https://composio.dev/toolkits/chmeetings/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/chmeetings/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the required dependencies for Autogen and Composio
- Initialize Composio and create a Tool Router session for Chmeetings
- Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
- Configure an Autogen AssistantAgent that can call Chmeetings tools
- Run a live chat loop where you ask the agent to perform Chmeetings operations

## What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.
Key features include:
- Multi-Agent Systems: Build collaborative agent workflows
- MCP Workbench: Native support for Model Context Protocol tools
- Streaming HTTP: Connect to external services through streamable HTTP
- AssistantAgent: Pre-built agent class for tool-using assistants

## 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 agents and assistants directly to Chmeetings. Instead of manually wiring Chmeetings APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely.
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

You will need:
- A Composio API key
- An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
- A Chmeetings account you can connect to Composio
- Some basic familiarity with Autogen and Python async

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

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

Install Composio, Autogen extensions, and dotenv.
What's happening:
- composio connects your agent to Chmeetings via MCP
- autogen-agentchat provides the AssistantAgent class
- autogen-ext-openai provides the OpenAI model client
- autogen-ext-tools provides MCP workbench support
```bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools
```

### 3. Set up environment variables

Create a .env file in your project folder.
What's happening:
- COMPOSIO_API_KEY is required to talk to Composio
- OPENAI_API_KEY is used by Autogen's OpenAI client
- USER_ID is how Composio identifies which user's Chmeetings connections to use
```bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com
```

### 4. Import dependencies and create Tool Router session

What's happening:
- load_dotenv() reads your .env file
- Composio(api_key=...) initializes the SDK
- create(...) creates a Tool Router session that exposes Chmeetings tools
- session.mcp.url is the MCP endpoint that Autogen will connect to
```python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Chmeetings session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["chmeetings"]
    )
    url = session.mcp.url
```

### 5. Configure MCP parameters for Autogen

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.
What's happening:
- url points to the Tool Router MCP endpoint from Composio
- timeout is the HTTP timeout for requests
- sse_read_timeout controls how long to wait when streaming responses
- terminate_on_close=True cleans up the MCP server process when the workbench is closed
```python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)
```

### 6. Create the model client and agent

What's happening:
- OpenAIChatCompletionClient wraps the OpenAI model for Autogen
- McpWorkbench connects the agent to the MCP tools
- AssistantAgent is configured with the Chmeetings tools from the workbench
```python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Chmeetings assistant agent with MCP tools
    agent = AssistantAgent(
        name="chmeetings_assistant",
        description="An AI assistant that helps with Chmeetings operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )
```

### 7. Run the interactive chat loop

What's happening:
- The script prompts you in a loop with You:
- Autogen passes your input to the model, which decides which Chmeetings tools to call via MCP
- agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
- Typing exit, quit, or bye ends the loop
```python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Chmeetings related question or task to the agent.\n")

# Conversation loop
while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Chmeetings session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["chmeetings"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Chmeetings assistant agent with MCP tools
        agent = AssistantAgent(
            name="chmeetings_assistant",
            description="An AI assistant that helps with Chmeetings operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Chmeetings related question or task to the agent.\n")

        # Conversation loop
        while True:
            user_input = input("You: ").strip()

            if user_input.lower() in ['exit', 'quit', 'bye']:
                print("\nGoodbye!")
                break

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

## Conclusion

You now have an Autogen assistant wired into Chmeetings through Composio's Tool Router and MCP. From here you can:
- Add more toolkits to the toolkits list, for example notion or hubspot
- Refine the agent description to point it at specific workflows
- Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Chmeetings, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

## 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)
- [LlamaIndex](https://composio.dev/toolkits/chmeetings/framework/llama-index)
- [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 Autogen?

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