ClickMeeting MCP integration for AI agents.
Connect AI agents to ClickMeeting through 19 structured actions, including get conference, create conference, delete conference, and generate access tokens.…
- ACTION CONTRACTS
- 19
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ClickMeeting integration exposes
The ClickMeeting Agent App exposes 19 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent get details for a clickmeeting room, create a clickmeeting meeting or webinar room, and delete a clickmeeting room. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ClickMeeting account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ClickMeeting capabilities.
Showing 12 of 19 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_conferenceREADGet details for a ClickMeeting room.
INPUTS: roomId
create_conferenceWRITECreate a ClickMeeting meeting or webinar room.
INPUTS: name / roomType / permanentRoom / accessType / customRoomUrlName
delete_conferenceHIGH IMPACTDelete a ClickMeeting room.
INPUTS: roomId
generate_access_tokensREVIEWGenerate access tokens for a token-protected ClickMeeting room.
INPUTS: roomId / howMany
get_sessionREADGet details for a ClickMeeting room session.
INPUTS: roomId / sessionId
list_access_tokensREADList generated access tokens for a ClickMeeting room.
INPUTS: roomId
list_all_recordingsREADList all ClickMeeting recordings for the connected account.
list_chatsREADList ClickMeeting chat archives available for download.
list_conference_recordingsREADList recordings for a ClickMeeting room.
INPUTS: roomId
list_conferencesREADList active or inactive ClickMeeting rooms.
INPUTS: status / page
list_phone_gatewaysREADList ClickMeeting phone gateway numbers.
list_registrationsREADList registrations for a ClickMeeting room by registration status.
INPUTS: roomId / status
INPUT CONTRACTS
Know what the action needs before it runs.
get_conference
roomIdOPTIONAL- The ClickMeeting room identifier.
create_conference
nameREQUIRED- The room name visible to ClickMeeting attendees.
roomTypeREQUIRED- The ClickMeeting room type.
permanentRoomREQUIRED- Whether to create a permanent room instead of a one-time scheduled room.
accessTypeREQUIRED- The ClickMeeting room access type: 1 for open access, 2 for password access, or 3 for token access.
customRoomUrlNameOPTIONAL- The custom room URL slug to use instead of one derived from name.
delete_conference
roomIdOPTIONAL- The ClickMeeting room identifier.
generate_access_tokens
roomIdOPTIONAL- The ClickMeeting room identifier.
howManyOPTIONAL- The number of access tokens to generate, up to 1000.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Conference
Get details for a ClickMeeting room. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_conferenceControl Create Conference
Create a ClickMeeting meeting or webinar room. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_conferenceVerify with Get Session
Get details for a ClickMeeting room session. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_sessionSAFETY BOUNDARY
Operate ClickMeeting with explicit limits
- Authorize ClickMeeting with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_conference` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ClickMeeting rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ClickMeeting task completed successfully.
CONNECTION MODEL
API key
ClickMeeting API key sent in the X-Api-Key header. Generate or view it in ClickMeeting account settings: https://account-panel.clickmeeting.com/account/details#api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 13
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ClickMeeting.