Sympla for AI agents

Sympla is an event management platform for in-person and online events, handling ticket sales, registrations, and digital content broadcasting. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

SchedulingAPI keyMCP + RESTsympla.com.br
AUDIT LOG · SYMPLAPOLICY: acme-support
09:41:07 · claude · u_8f2read
sympla.list_events
List Events✓ allowed · 212ms
EVERY SYMPLA CALL, ON THE RECORD
01 · USE CASES

What agents do in Sympla.

01

List upcoming events

Pull the list of events on the account so an organizer can check what is coming up this month.

02

Check registration counts per event

List events to review registration numbers before deciding whether to open more tickets.

03

Confirm event details before promotion

List an event's details as a read-only check before an agent drafts promotional messaging for it.

02 · ACTIONS

1 Sympla actions, graded by risk.

Every Sympla action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

1

Look things up. Allowed by default.

  • sympla.list_events
    List Events

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Sympla in three steps.

  1. 01Your users connect SymplaThey add their Sympla api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Sympla through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('sympla', {
  read: 'allow',
  write: 'ask',        
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Sympla connects.

Users add their Sympla api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Sympla connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Sympla from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Sympla and Arc0, answered.

Q01

Can I use Sympla with Claude, ChatGPT or Cursor?

Yes. Connect Sympla to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Sympla actions you allow.

Q02

How do users connect Sympla?

Users add their Sympla api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Sympla actions can my agent take?

1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Sympla?

Yes. Allow read actions and deny writes in the Sympla policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Sympla too?

Yes. The same Sympla connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Sympla into your agent.

Your users connect Sympla once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan