Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
ClickMeeting (BYOK) icon

ClickMeeting (BYOK)

Read your ClickMeeting webinar and meeting rooms, sessions, attendees, registrations, recordings and chat logs with your own API key

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderClickMeetingunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which ClickMeeting webinar rooms are active?
Tools called
list_rooms
Show ClickMeeting room 2686
Tools called
get_room
When was ClickMeeting room 2686 used and how many people joined?
Tools called
list_sessions
Show session 65177 of ClickMeeting room 2686
Tools called
get_session
Who attended session 65177 of ClickMeeting room 2686?
Tools called
list_session_attendees
Who registered for ClickMeeting room 2686?
Tools called
list_registrations

About

ClickMeeting (BYOK) lets an AI assistant read your own ClickMeeting data through the ClickMeeting API with a key you supply (ClickMeeting API key). Read-only: 10 tools (list_rooms, get_room, list_sessions, get_session, list_session_attendees, list_registrations, list_session_registrations, list_all_recordings, list_room_recordings, list_chats). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.clickmeeting.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ClickMeeting. ClickMeeting and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the ClickMeeting API (api.clickmeeting.com) with a BYOK key; documentation: https://dev.clickmeeting.com/api-doc/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List roomsList meeting and webinar rooms by status with name, type, address, time zone and registration flag.
  • Get roomGet one room with name, type, status, address, time zone and registration flag.
  • List sessionsList the sessions (individual runs) of a room with start, end and visitor counts.
  • Get sessionGet one session of a room with start, end, visitor counts and the attendee list with join and leave times.
  • List session attendeesList who attended a session with nickname, role, rating, rating comment and email.
  • List registrationsList people registered for a room, all or only active ones, with email, nickname, registration time and session.
  • List session registrationsList people registered for one session of a room.
  • List all recordingsList the recordings across all rooms with name, room id, duration, start time and file size.
  • List room recordingsList the recordings of one room with duration, start time and file size.
  • List chatsList the saved chat logs of sessions with room name, date, time and session id.

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-clickmeeting.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 10 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-clickmeeting.connectorbay.com/mcp
RESTPOST https://byok-clickmeeting.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-clickmeeting.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your ClickMeeting API key in the X-Upstream-Key header (get one at dev.clickmeeting.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

ClickMeeting connector: questions and answers

What is the ClickMeeting connector?

ClickMeeting (BYOK) lets an AI assistant read your own ClickMeeting data through the ClickMeeting API with a key you supply (ClickMeeting API key). It is a hosted MCP server with 10 tools such as List rooms, Get room, List sessions, Get session, List session attendees, List registrations, published by Unify Dynamics LLC. It is independent and not affiliated with ClickMeeting.

How do I connect ClickMeeting to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-clickmeeting.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-clickmeeting.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-clickmeeting.json.

Do I need a ClickMeeting account or API key?

Yes: this is a bring-your-own-key connector. Create a ClickMeeting API key at https://dev.clickmeeting.com/api-guide/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is ClickMeeting read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the ClickMeeting connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

NocoDB Cloud (BYOK)

Read your NocoDB Cloud workspaces, bases, tables, views and table records with BYOK

Live · MCP + REST9 tools

noCRM (BYOK)

Read your noCRM sales leads, pipelines, steps, client folders, users, teams and follow-ups with your own API key

Live · MCP + REST12 tools

Notion (BYOK)

Read the Notion pages, databases, page content, comments and users shared with your integration with BYOK

Live · MCP + REST11 tools

Novu (BYOK)

Read your Novu workflows, topics, subscribers, notification events and integrations with BYOK key (US region)

Live · MCP + REST5 tools

Novu Environments (BYOK)

Read your Novu environments, workflow tags, environment variable names and inbound email domains with routes using your own secret key (US region)

Live · MCP + REST7 tools

Novu Layouts (BYOK)

Read your Novu email layouts, where each layout is used, and shared contexts with your own secret key (US region)

Live · MCP + REST5 tools

Documentation

Back to top

ClickMeeting (BYOK) — connector documentation

  • MCP endpoint: https://byok-clickmeeting.connectorbay.com/mcp
  • REST API: POST https://byok-clickmeeting.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-clickmeeting.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own ClickMeeting ClickMeeting API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-clickmeeting.connectorbay.com/health · Tool schemas: https://byok-clickmeeting.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-clickmeeting · agent@connectorbay.com

What ClickMeeting (BYOK) is for

ClickMeeting (BYOK) lets an AI assistant read your own ClickMeeting data through the ClickMeeting API with a key you supply (ClickMeeting API key). Read-only: 10 tools (list_rooms, get_room, list_sessions, get_session, list_session_attendees, list_registrations, list_session_registrations, list_all_recordings, list_room_recordings, list_chats). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.clickmeeting.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ClickMeeting. ClickMeeting and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which ClickMeeting webinar rooms are active?"
  • "Show ClickMeeting room 2686"
  • "When was ClickMeeting room 2686 used and how many people joined?"
  • "Show session 65177 of ClickMeeting room 2686"
  • "Who attended session 65177 of ClickMeeting room 2686?"
  • "Who registered for ClickMeeting room 2686?"

What it does

  • list_rooms: List meeting and webinar rooms by status with name, type, address, time zone and registration flag. Access PINs and role hashes are not returned. Inactive rooms are paged 250 at a time.
  • get_room: Get one room with name, type, status, address, time zone and registration flag.
  • list_sessions: List the sessions (individual runs) of a room with start, end and visitor counts.
  • get_session: Get one session of a room with start, end, visitor counts and the attendee list with join and leave times.
  • list_session_attendees: List who attended a session with nickname, role, rating, rating comment and email.
  • list_registrations: List people registered for a room, all or only active ones, with email, nickname, registration time and session.
  • list_session_registrations: List people registered for one session of a room.
  • list_all_recordings: List the recordings across all rooms with name, room id, duration, start time and file size. Download links are not returned.
  • list_room_recordings: List the recordings of one room with duration, start time and file size. Download links are not returned.
  • list_chats: List the saved chat logs of sessions with room name, date, time and session id.

BYOK key

You bring your own ClickMeeting ClickMeeting API key (https://dev.clickmeeting.com/api-guide/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.clickmeeting.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the ClickMeeting API (api.clickmeeting.com) with a BYOK key; documentation: https://dev.clickmeeting.com/api-doc/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ClickMeeting. ClickMeeting and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your ClickMeeting account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

ClickMeeting (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What ClickMeeting (BYOK) is. ClickMeeting (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own ClickMeeting data: Read your ClickMeeting webinar and meeting rooms, sessions, attendees, registrations, recordings and chat logs with your own API key. You bring your own ClickMeeting ClickMeeting API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one ClickMeeting call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.clickmeeting.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If ClickMeeting rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What ClickMeeting receives. The request we make on your behalf, including the key and the arguments, under ClickMeeting's own terms and privacy policy. ClickMeeting acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer ClickMeeting gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your ClickMeeting data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. ClickMeeting (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at ClickMeeting at any time to end all access.

Children. ClickMeeting (BYOK) is a general-audience service operated by the adult using the assistant, under ClickMeeting's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

ClickMeeting (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the ClickMeeting (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. ClickMeeting (BYOK) provides: Read your ClickMeeting webinar and meeting rooms, sessions, attendees, registrations, recordings and chat logs with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own ClickMeeting credentials and only access data you are allowed to access. ClickMeeting's terms apply to your use of ClickMeeting; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ClickMeeting. ClickMeeting and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data ClickMeeting returns, lightly trimmed; it may be incomplete, delayed or changed by ClickMeeting. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your ClickMeeting account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent ClickMeeting's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; ClickMeeting may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your ClickMeeting key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action ClickMeeting takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-clickmeeting

ClickMeeting (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. ClickMeeting (BYOK) never asks for them.

Get ClickMeeting (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own ClickMeeting ClickMeeting API key. Create one at https://dev.clickmeeting.com/api-guide/, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to ClickMeeting. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with ClickMeeting.