Read conferences, registrants, attendees and recordings; register and cancel people in BigMarker. For event and marketing teams that host webinars on BigMarker. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"bigmarker": {
"url": "https://bigmarker.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"bigmarker": {
"type": "http",
"url": "https://bigmarker.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Read the summary of a conference with the attendees and the no-shows.
bigmarker_get_event_summary bigmarker_list_attendees bigmarker_list_no_shows
Search the conferences and open one to read the details and the presenters.
bigmarker_search_conferences bigmarker_get_conference bigmarker_list_presenters
Read the recording status of a conference and list who watched it.
bigmarker_get_recording bigmarker_list_recording_views
List the conferences of a channel with their stats.
bigmarker_list_channels bigmarker_list_channel_conferences
Register a person for a conference, or cancel a registration.
Changes data · bigmarker_list_registrations bigmarker_register_user bigmarker_cancel_registration
The login page asks for your BigMarker API key.
Find it in BigMarker → Settings → API keys. If the page shows no key, ask BigMarker support ([email protected]) to enable API access. Your key is used only to call the API on your behalf and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your BigMarker API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the BigMarker connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
bigmarker_list_conferences | read | List conferences List webinars and events from all channels the key can reach. Filter by type (future, past, happening_now ...), title text and a time range. Default type is future. API: GET /conferences/. |
bigmarker_get_conference | read | Get a conference Get one webinar or event by id: title, address, purpose, schedule and settings. API: GET /conferences/{id}. |
bigmarker_search_conferences | read | Search conferences Search conferences across all channels by title, a time range or a list of ids. Read-only. API: POST /conferences/search. |
bigmarker_list_channels | read | List channels List all channels (id, url, name, overview) the key can access. API: GET /channels/. |
bigmarker_get_channel | read | Get a channel Get one channel by id: url, name, overview and description. API: GET /channels/{id}. |
bigmarker_list_channel_conferences | read | List channel conferences with stats List the conferences of one channel with registration and attendance totals (registrations, live attendees, on-demand viewers). API: GET /channels/{channel_url}/conferences/stats. |
bigmarker_list_registrations | read | List registrants of a conference List the people registered for a conference: name, email, personal enter URL and certificate state. Use include_all_status to also see canceled or pending ones. Personal data. API: GET /conferences/registrations/{id}. |
bigmarker_list_attendees | read | List attendees of a conference List who attended a conference live, with enter and leave times, duration, chat, Q&A and poll counts. Personal data. API: GET /conferences/{id}/attendees. |
bigmarker_list_no_shows | read | List no-shows of a conference List registrants who did not attend the conference, with registration date, country and traffic source. Personal data. API: GET /reporting/conferences/no_shows/{id}. |
bigmarker_get_event_summary | read | Get a conference summary Get the summary report of a conference: total live minutes watched, creator and creation date. API: GET /reporting/conferences/event_summary/{id}. |
bigmarker_list_presenters | read | List presenters of a conference List the presenters of a conference: name, email, display settings and page URL. API: GET /conferences/{id}/presenters. |
bigmarker_get_recording | read | Get recording status Get the recording status of a conference. API: GET /conferences/{id}/recording. |
bigmarker_list_recording_views | read | List recording views List the on-demand views of a conference recording: registrant id, time and minutes watched. API: GET /conferences/{id}/recording_views. |
bigmarker_register_user | write | Register a person for a conference WRITE: register a person for a conference. BigMarker may send the person a confirmation email. Returns the personal URL the person uses to enter. API: PUT /conferences/register. |
bigmarker_cancel_registration | write | Cancel a registration WRITE: cancel the registration of one person for a conference. Returns the registration id and its new status. API: POST /conferences/cancel_registration. |
bigmarker_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
bigmarker_request_feature | Request a missing feature Tell usefulapi that the user needs something the BigMarker tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
bigmarker_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on BigMarker (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
bigmarker_cancel_subscription | Cancel the Pro subscription Cancel the caller's BigMarker Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run bigmarker_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this BigMarker server only. Subscribe with bigmarker_upgrade (it returns a Stripe Checkout link). Cancel any time with bigmarker_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running bigmarker_upgrade before then undoes the cancel. Or write to [email protected].
Review the results of a conference. Find upcoming conferences. Check recording views. Compare the conferences of a channel. Register a person for a conference. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by BigMarker. The server calls the BigMarker API with your own BigMarker access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your BigMarker API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your BigMarker API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the BigMarker API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in BigMarker.
Yes, if you approve it. 2 of the 15 BigMarker tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this BigMarker server only. Cancel any time: Pro then runs to the end of the paid period. Run bigmarker_usage_status to see how many calls you used.
Ask the AI to run bigmarker_upgrade: it returns a Stripe Checkout link. To cancel, run bigmarker_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with bigmarker_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.