HeySummit's Model Context Protocol (MCP) server gives compatible AI assistants a secure way to work with your events. Once connected, an assistant can answer questions about your event, identify setup gaps, draft an event setup plan, and help you preview or apply supported changes.
Before you connect
You need an active paid HeySummit plan.
You need an AI client or developer tool that supports remote MCP servers over Streamable HTTP.
You need access to the events you want the assistant to use. API keys and OAuth connections cannot exceed your existing HeySummit permissions.
Connection details
Server name: HeySummit
Server URL: https://api.heysummit.com/mcp/
Transport: Streamable HTTP
Authentication: OAuth 2.0, or an API token when your client supports a custom Authorization header
Choose OAuth when your client offers it. Add the HeySummit server URL and leave the OAuth Client ID and Client Secret fields blank. Compatible clients, including Claude and Perplexity, register automatically and then take you through HeySummit sign-in and authorization. You do not need to send HeySummit the client's callback or redirect URL.
Choose what the assistant can access
When approving a new OAuth connection, use Choose event access to select specific events or all current and future events you can access. Review the permissions shown before authorizing the client. Existing OAuth grants keep their previous event access.
Read, write and destructive actions need the corresponding connection permissions and your existing HeySummit permissions.
If a client does not request a specific scope, check the permissions displayed on the consent screen. Do not assume that signing in limits the assistant to read-only access.
To create new events, the connection needs all-event access and event-write permission.
Connect with an API key
For developer tools that support custom headers, open API keys in your account dashboard and create a separate named key. Choose its events and permissions, copy the one-time secret securely, and send it as Authorization: Token YOUR_API_KEY. Treat the secret like a password and only add it to a client you trust. Restricted keys work with API v2 event endpoints and MCP; preserve your existing unrestricted token for legacy API, Zapier and account-wide webhook integrations.
See Manage API keys and integration access for setup, rotation and troubleshooting.
What your assistant can do
MCP can read event setup status, content, attendee records and supported Page Builder data. With the appropriate permissions, it can also help change event basics, talks, speakers, categories, sponsors, attendees, tickets, coupons, registration settings, schedule relationships and supported Page Builder content. Check the tools and their descriptions in your connected client for the operations available to that connection.
Publish, unpublish or change an event timezone
Use the separate Publish Event, Unpublish Event and Update Event Timezone tools in your connected AI client. General event updates do not change publication status or timezone. These actions need event-write permission and access to the event.
Publish Event checks the same account requirements as publishing in the dashboard. Publishing may notify eligible brand subscribers. Review the event, requirements and intended launch before confirming.
Unpublish Event hides the event from attendees while keeping its content and registration history.
Update Event Timezone accepts an IANA timezone such as America/Vancouver. It changes the saved event timezone and refreshes local labels and timezone-dependent settings. Existing sessions keep their actual scheduled instants; this does not move the schedule forward or backward.
Ask for a preview first, review the result, and explicitly confirm before applying it. Developers should leave confirm_apply false for previews and set it to true only after confirmation.
These tools are available through external MCP clients. HeySummit's built-in assistant does not currently apply these publication and timezone changes.
How changes stay safe
Change tools offer previews by default so you can review supported changes before they are saved.
Review the preview and explicitly confirm the intended change before asking your assistant to apply it. Applying a change requires a confirmed request; do not treat a successful connection as approval to change your event.
Delete actions require an additional destructive-action permission and explicit confirmation.
Your AI client may add its own approval step as well. Always check the event and resource named in a preview before approving it.
Example prompts
List my HeySummit events and show which setup tasks are incomplete.
Show the talks, speakers, and tickets for my upcoming event.
Draft a setup plan for my event, but do not apply anything yet.
Preview adding a new speaker and attaching them to a talk.
Preview creating a coupon for my event.
Preview publishing my event and show any requirements that prevent publication.
Preview changing my event timezone to America/Vancouver without moving its sessions.
Preview adding a pre-recorded session using this YouTube video URL: [paste the source URL].
Current limits
Available tools depend on their supported operations and your connection permissions. Complete tasks without a supported tool in the HeySummit dashboard. Setup-plan application automatically handles categories, speakers, talks and speaker-to-talk links; other plan items can remain manual or deferred. Individual MCP tools can manage additional records and Page Builder content outside that setup-plan flow.
Troubleshooting
Your client shows optional client ID or client secret fields: leave both fields blank so the client can register automatically.
Automatic registration fails: remove the existing HeySummit connection and add it again using only the server URL. If it still fails, contact HeySummit support with the client name and the exact error shown.
Authentication fails: reconnect the OAuth account, or check that a custom header uses the word Token rather than Bearer.
You receive a permission error: check your active paid plan, your own event permissions, the connection's allowed events and the permissions needed for the requested action. For an OAuth connection, reconnect if you need to approve different access.
A new tool is missing: refresh the server's tools in your AI client or disconnect and reconnect it.