Instead of clicking through approval queues, coupon settings and door lists, you ask in plain words. "Which guests are still waiting on me?" "Make an early-bird coupon for 20% off." "Check in Maria Lopez." Your assistant reads your live EpochX data, shows you what it plans to change, and does it.
This post is the start guide: what the server can do, what you need, how to connect in four steps, and the guardrails that keep you in control. The full reference lives in our Help Center article, Agent Epoch MCP server.
What the EpochX MCP server is
MCP stands for Model Context Protocol. It is a shared standard that lets an AI app plug into other software, so the assistant can look things up and make changes there on your behalf.
The EpochX MCP server (you'll see it called Agent Epoch in the product) gives your assistant access to eight areas of EpochX: events, ticketing, guests, on-site check-in, emails, contacts, the site builder and reports. You connect it once per team, choose what it may touch, and then work from the chat window you already have open.
What you can ask it to do
You can build a full registration page without leaving Claude. Ask your assistant to create the event, and Epoch's site builder drafts the registration page, shows you a preview and publishes it when you say so.
A few prompts to try once you're connected:
- "Create a registration page for my [insert title] event on [insert date]."
- "Which guests are waiting for my approval?"
- "How many guests from each company are coming?"
- "Create a 20% off coupon for early birds."
- "Draft an email to my VIP group and show me before it goes out."
- "Check in Maria Lopez at the door."
Here is the full range, by area:
| Area | What your assistant can help with |
|---|---|
| Events | Find your events and save changes to event details and sessions as a site draft |
| Ticketing | List tiers, orders, coupons and access codes; check your Stripe connection; create, copy, edit or remove tiers, coupons and access codes; turn ticketing on or off |
| Guests | See who is waiting for approval; approve, decline or promote guests; invite contacts; import a guest list; manage groups |
| On-site check-in | See the door list and check-in counts; check guests in, add walk-ups, undo a check-in; create and edit staff links |
| Emails | Review built-in emails, edit their settings and text, send yourself a test copy, send emails to guests |
| Contacts | Look up contacts and CRM records, build contact groups, add CRM notes, pull contacts from your CRM, see CRM deal outcomes after an event |
| Site builder | Create an event with its site, ask Epoch's site builder to build or change your page, preview it and publish it |
| Reports | Guest counts by company, title or group, plus feedback results |
Before you start
You need four things in place:
- An Epoch account that signs in with Google or your company login. If Epoch says your account uses a password, sign in once with Google or your company login, then connect again.
- A team admin or organization admin role in the organization you want your assistant to work in.
- A plan that includes Connected agents. They come with the Starter plan and above.
- An AI app that can add a connector by link, such as Claude or ChatGPT.
Connect EpochX in four steps
Step 1. Copy your organization's link. In Epoch, open your team's Integrations page and go to the Connected agents section. Click Copy next to the link. If you have connected an app before, click Connect another app to show it. Every organization gets its own link, which looks like api.getepochx.com/mcp/o/ followed by your organization ID.
Step 2. Add it to your AI app. In Claude or ChatGPT, add a custom connector and paste the link.
Step 3. Sign in. Your AI app opens an Epoch sign-in window. Sign in with your Epoch account.
Step 4. Pick the team and set access. Ask your assistant anything. Its first reply includes a setup link. Back in Epoch, go to Integrations, then Connected agents, find your app (marked "Waiting to be set up") and click Use this team. Choose what the assistant may do, then click Save access. Your choices apply from the assistant's next request.
Tip
A good first prompt is "Which guests are waiting for my approval?" It only reads data, so it's an easy way to confirm the connection works.
For developers: Claude Code and other MCP clients
The server speaks MCP over Streamable HTTP (POST only, JSON responses, no streaming). Sign-in uses OAuth with dynamic client registration: your app discovers the sign-in server from the link and registers itself, so there is no API key or client ID to manage.
To add it to Claude Code:
claude mcp add --transport http epoch https://api.getepochx.com/mcp/o/<your-organization-id>
Then run /mcp to sign in. Any other app that supports remote MCP servers with OAuth sign-in can use the same link. Step 4 above still applies.
Decide what your assistant is allowed to do
Access is set per area. For each one you can tick Read, tick Write, or leave it at no access. Emails has an extra row, Send emails to guests, so drafting and sending stay separate decisions.
Read access is on for every area by default. Adjust each area, then click Save access. Your choices cover every app connected to that team, and you can update them any time with Change access.
Some permissions depend on others, and the settings screen tells you when that happens. A few to know up front:
- Saving event changes to the site draft also needs Write on Site builder.
- Creating or editing a ticket tier also needs Send emails to guests, because guests see ticket names.
- Asking Epoch's site builder to build a page also needs Write on Ticketing, Guests and Contacts, plus Send emails to guests. The site builder can create tickets, guests and contacts and email them.
- Publishing a site also needs Send emails to guests.
If you're new to working this way, a sensible pattern is to start with read access, get used to the answers, then switch on Write for the areas where you want the assistant to take action.
Guardrails that keep you in control
- It acts as you, on one team. Your assistant can only do what you can do in Epoch, on the team you picked. It can't see other organizations or teams.
- Big changes need a preview first. Emailing guests, changing many guests' status at once, importing a guest or group list, and publishing a site all require the assistant to show you a preview before it applies anything. Previews expire after 10 minutes. A publish that would remove guest data can only be confirmed by you, inside Epoch.
- Single guest decisions send your usual emails. Approving, declining or promoting one guest happens in one step and sends whatever email your event settings call for. To skip the email for one decision, use the event's Guests page in Epoch.
- Risky tools are flagged. Removing records, applying previewed changes, guest actions and undoing a check-in are marked as destructive, so your AI app can ask before running them. Turn on approvals in your AI app to use this.
- Guest text is treated as data. Names, answers and notes from guests reach your assistant as data, never as instructions. Take care when other connectors are active in the same chat.
- Logs record calls, not content. Epoch's server logs note which tool ran and whether it worked, not the data it read. Epoch also keeps a record of every change your assistant requests.
Limits worth knowing
- 120 requests per person and 600 per organization, every 10 minutes
- Lists return 25 rows per page
- Guest imports through your assistant can be up to 3 MB; import larger files on the event's Guests page
- One organization and one team per connection
How to disconnect
- One app: go to Integrations, then Connected agents, and click Revoke on the app. If it connects again, it waits for you to set it up and can't do anything until you do. To stop it for good, remove the connector in your AI app as well.
- Every app in your organization: an organization admin can switch off Allow connected agents in the same section. Switching it back on resumes each connection as it was.
- Role or team changes: if you lose your admin role on the team, or the team is archived, the app returns to "Waiting to be set up" and its access choices for that team are cleared.
Troubleshooting
| If you see | Do this |
|---|---|
| "This connection isn't set up yet" | Open Integrations in Epoch, click Use this team on the app and save access |
| "This Epoch account signs in with a password" | Sign in to Epoch once with Google or your company login, then connect again |
| "Connected agents need a team admin role" | Ask your Epoch admin to make you a team admin |
| "Connected agents come with Epoch's Starter plan and above" | Ask your Epoch admin to upgrade your plan |
| "Your organization has switched off connected agents" | Ask your Epoch admin to switch them on in Integrations |
| "Your agent is asking Epoch for too much at once" | Wait the number of seconds shown, then try again |
| Your app shows "reconnected" in Epoch | Click Use this team to carry on |
Get started
If you're already on EpochX Starter or above, open Integrations, copy your link and ask your assistant about your next guest list.
New to EpochX? Start free or talk to us about Connected agents for your team. For setup questions, email support@epochapp.com or read the Help Center guide.
