# How to connect Chmeetings to OpenClaw (paste one key, 28 tools) > Connect Chmeetings to OpenClaw with ClawLink: paste your Chmeetings key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/chmeetings The usual route to Chmeetings access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Chmeetings setup: install one ClawHub skill, connect Chmeetings in the browser, and OpenClaw can call real Chmeetings actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Chmeetings. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Chmeetings** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect chmeetings # connect Chmeetings (browser OAuth) npx -y @useclawlink/cli actions chmeetings # list available actions npx -y @useclawlink/cli run chmeetings --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Chmeetings in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Chmeetings API key once. Verify the connection by asking OpenClaw: > Use Chmeetings to attendee get and walk me through the result in plain English. ### Using a different agent? The OpenClaw 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Chmeetings MCP for OpenClaw Looking for a Chmeetings MCP server for OpenClaw? ClawLink connects Chmeetings to OpenClaw and exposes 28 Chmeetings tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Chmeetings integration](https://claw-link.dev/hermes/chmeetings) works the same way. ## What the OpenClaw Chmeetings integration can do 28 Chmeetings tools are ready for OpenClaw 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 OpenClaw | 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 | ## Example prompts **Attendee Get** > Use Chmeetings to attendee get and walk me through the result in plain English. **List Meeting Attendees** > List the relevant items in Chmeetings, group them by priority, and recommend what OpenClaw should do next. **Meetings Get** > Use Chmeetings to meetings get and walk me through the result in plain English. **Organization Get** > 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 OpenClaw. 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Chmeetings skill but can't call the tools The ClawHub skill teaches OpenClaw about Chmeetings, but the calls run through the ClawLink plugin and your connected account. Make sure Chmeetings is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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. ### Is there a OpenClaw Chmeetings integration? Yes. ClawLink is the fastest way to connect OpenClaw to Chmeetings: link your Chmeetings account once in the browser and OpenClaw can call the Chmeetings API through 28 ready-made tools — no custom code or token handling. ### How do I add Chmeetings to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Chmeetings skill from ClawHub, then you click Connect in the dashboard to authorize Chmeetings. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Chmeetings in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Chmeetings working from chat. ### OpenClaw installed the Chmeetings skill but can't call the tools The ClawHub skill teaches OpenClaw about Chmeetings, but the calls run through the ClawLink plugin and your connected account. Make sure Chmeetings is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect Cal.com](https://claw-link.dev/openclaw/cal) — Schedule and manage bookings through Cal.com - [OpenClaw Bookingmood integration](https://claw-link.dev/openclaw/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website. - [Eventbrite tools](https://claw-link.dev/openclaw/eventbrite) — Create and manage events, tickets, and attendees