How to connect Chmeetings to Hermes Agent
Connect Chmeetings to Hermes with ClawLink: paste your Chmeetings key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine.
ChmeetingsAPI KEYMCPCHMeetings is a comprehensive church management platform offering event planning, member engagement tracking, donation management, volunteer coordination, and communication tools for faith-based organizations and religious communities.. Once connected, Hermes Agent can read and act on Chmeetings from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Chmeetings access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Chmeetings setup: pair once in the browser and your always-on Hermes agent can act on Chmeetings for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Chmeetings.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Chmeetings
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Chmeetings?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Chmeetings in the ClawLink dashboard — paste your Chmeetings API key once.
Verify the connection by asking Hermes:
Use Chmeetings to attendee get and walk me through the result in plain English.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Chmeetings is connected in the dashboard, that agent calls the same 28 Chmeetings tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Chmeetings MCP for Hermes
Looking for a Chmeetings MCP server for Hermes Agent? ClawLink connects Chmeetings to Hermes Agent and exposes 28 Chmeetings tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Chmeetings integration works the same way.
What the Hermes Agent Chmeetings integration can do
28 Chmeetings tools are ready for Hermes Agent once the account is connected. The 23 below are the ones people reach for most; your agent can call all 28.
23 of 28 Chmeetings tools for Hermes
| Tool | What it does |
|---|---|
Attendee get chmeetings_attendee_get | Retrieve details for a specific attendee |
List meeting attendees chmeetings_list_meeting_attendees | List attendees of a meeting |
Meetings get chmeetings_meetings_get | Retrieve a specific meeting's details by ID |
Organization get chmeetings_organization_get | Get details of a specific organization |
Organizations list chmeetings_organizations_list | List all organizations |
People list chmeetings_people_list | Retrieve list of People records from ChMeetings |
Person get chmeetings_person_get | Retrieve a specific person's details by ID |
Reminder get chmeetings_reminder_get | Retrieve details of a specific reminder |
Reminders list chmeetings_reminders_list | List reminders from ChMeetings |
Settings get chmeetings_settings_get | Retrieve account configuration settings |
User profile get chmeetings_user_profile_get | Retrieve current user's profile information |
Attendee create chmeetings_attendee_create | Invite a new attendee to a specified meeting |
Create meeting chmeetings_create_meeting | Create a new meeting in ChMeetings |
Create organization chmeetings_create_organization | Create a new organization |
Create reminder chmeetings_create_reminder | Create/schedule a reminder for a meeting in ChMeetings |
Meetings update chmeetings_meetings_update | Update meeting details |
Notifications send chmeetings_notifications_send | Attempt sending a notification |
Organization update chmeetings_organization_update | Update an organization's information |
People update chmeetings_people_update | Update an existing person's information in ChMeetings |
Person create chmeetings_person_create | Create a new person record in ChMeetings People directory |
Reminder update chmeetings_reminder_update | Update an existing reminder |
Settings update chmeetings_settings_update | Update account settings |
Update attendee role chmeetings_update_attendee_role | Update the role of an attendee |
Try it: find the Chmeetings tool you need
Browse the 23 Chmeetings tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Chmeetings to attendee get and walk me through the result in plain English.
List the relevant items in Chmeetings, group them by priority, and recommend what Hermes should do next.
Use Chmeetings to meetings get and walk me through the result in plain English.
Use Chmeetings to organization get and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Chmeetings working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Chmeetings API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Chmeetings account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Chmeetings. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Chmeetings actions to the runtime in a format your agent can reliably use. | 28 tools for Chmeetings are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Chmeetings to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Chmeetings in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the Chmeetings key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Chmeetings
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Chmeetings from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Chmeetings tools
Chmeetings tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Chmeetings call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Chmeetings returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Chmeetings has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Chmeetings integration?
Yes. ClawLink is the fastest way to connect Hermes to Chmeetings: link your Chmeetings account once in the browser and Hermes Agent can call the Chmeetings API through 28 ready-made tools — no custom code or token handling.
How do I connect Chmeetings to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Chmeetings in the dashboard and Hermes can use it from the next message — no config files, and the Chmeetings key you paste is stored server-side instead of in your environment.
How long does it take to connect Chmeetings to Hermes Agent?
About two minutes. Sign in, click Connect next to Chmeetings in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Chmeetings up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Chmeetings working from chat.
Hermes paired but still can't use Chmeetings
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
