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
Your HeySummit plan must include API access.
You need an AI client or developer tool that supports remote MCP servers over Streamable HTTP.
If you use your HeySummit API token, you must be the event owner or a staff user who can open Event Setup > API Settings.
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. This first release uses assisted OAuth setup for clients that ask for their own client ID and client secret. Contact HeySummit support and tell us which AI client you are connecting, together with the callback or redirect URL shown by that client.
For developer tools that support custom headers, open Event Setup > API Settings, copy your API token, and send it as Authorization: Token YOUR_API_TOKEN. Treat this token like a password and only add it to a client you trust.
What your assistant can do
The first MCP release can read your events, setup status, talks, speakers, categories, tickets, coupons, sponsors, attendees, and attendee schedules. With the appropriate permissions, it can also help create or update event basics, talks, speakers, categories, sponsors, attendees, coupons, ticket assignments, and schedule relationships.
How changes stay safe
Write actions return a preview by default, so you can review the proposed change before anything is saved.
The assistant must make a second confirmed request before HeySummit applies a change.
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.
Current limits
This first version does not configure payment providers, send emails, publish an event, change domains or branding, or perform general data imports. Setup-plan application is currently limited to supported event content such as categories, speakers, talks, and speaker-to-talk links, although other individual MCP tools can manage additional event records.
Troubleshooting
Your client asks for a client ID or client secret: contact HeySummit support with the client name and its callback or redirect URL.
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 that your HeySummit plan includes API access and that the connection has the scopes needed for the requested read, write, or destructive action.
A new tool is missing: refresh the server's tools in your AI client or disconnect and reconnect it.
Developers who want to use HeySummit's REST API directly can use the HeySummit API v2 documentation.