How to integrate Chmeetings MCP with Codex

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Chmeetings logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Chmeetings MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Chmeetings with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Chmeetings MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

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 & Triggers

Tools
Invite Meeting AttendeeTool to invite a new attendee to a specified meeting.
Get Attendee DetailsTool to retrieve details for a specific attendee.
ChMeetings: Create MeetingTool to create a new meeting in ChMeetings.
ChMeetings: Create OrganizationTool to create a new organization.
ChMeetings: Create ReminderTool to create/schedule a reminder for a meeting in ChMeetings.
Delete Meeting AttendeeTool to remove an attendee from a meeting.
List Meeting AttendeesTool to list attendees of a meeting.
ChMeetings: Delete MeetingTool to delete an existing meeting.
ChMeetings: Get MeetingTool to retrieve a specific meeting's details by ID.
ChMeetings: Update MeetingTool to update meeting details.
ChMeetings: Send NotificationTool to attempt sending a notification.
ChMeetings: Get OrganizationTool to get details of a specific organization.
ChMeetings: Delete OrganizationTool to delete an existing organization.
ChMeetings: List OrganizationsTool to list all organizations.
ChMeetings: Update OrganizationTool to update an organization's information.
ChMeetings: Delete PersonTool to delete a person record.
ChMeetings: List PeopleTool to retrieve list of People records from ChMeetings.
ChMeetings: Update PersonTool to update an existing person's information in ChMeetings.
ChMeetings: Create PersonTool to create a new person record in ChMeetings People directory.
ChMeetings: Get PersonTool to retrieve a specific person's details by ID.
ChMeetings: Delete ReminderTool to cancel a scheduled reminder.
ChMeetings: Get ReminderTool to retrieve details of a specific reminder.
ChMeetings: List RemindersTool to list reminders from ChMeetings.
ChMeetings: Update ReminderTool to update an existing reminder.
ChMeetings: Get SettingsTool to retrieve account configuration settings.
ChMeetings: Update SettingsTool to update account settings.
Update attendee roleTool to update the role of an attendee.
ChMeetings: Get User ProfileTool to retrieve current user's profile information.

Conclusion

You've successfully integrated Chmeetings with Codex using Composio's MCP server. Now you can interact with Chmeetings directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Chmeetings operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Chmeetings operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Chmeetings MCP Agent with another framework

FAQ

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 Codex?

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.