Exceptionless for AI agents
Exceptionless is an error and event tracking tool that ingests application events using a project-bound API key, used by developers monitoring application health in production. 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.
What agents do in Exceptionless.
Submit an application event
Submit an event when an application error occurs so the team can see it in the dashboard.
Check client configuration
Get a client's configuration to confirm which settings a project is currently using.
Read-only session checks
Keep session heartbeat and configuration checks read-only, since they only report status.
4 Exceptionless actions, graded by risk.
Every Exceptionless action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- exceptionless.get_client_configurationGet Client Configuration
write
2Create and change things. Allow, or ask the user first.
- exceptionless.submit_eventSubmit Event
- exceptionless.submit_session_heartbeatSubmit Session Heartbeat
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- exceptionless.close_sessionClose Session
Exceptionless in three steps.
- 01Your users connect ExceptionlessThey add their Exceptionless api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “submit Event” can wait for the user, and “close Session” can be denied outright.
- 03Any agent can actYour agent calls Exceptionless through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('exceptionless', { read: 'allow', write: 'ask', // submit_event destructive: 'deny', // close_session }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Exceptionless connects.
Users add their Exceptionless 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 Exceptionless 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
Use Exceptionless from any agent.
Exceptionless and Arc0, answered.
Can I use Exceptionless with Claude, ChatGPT or Cursor?
Yes. Connect Exceptionless 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 Exceptionless actions you allow.
How do users connect Exceptionless?
Users add their Exceptionless 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.
Which Exceptionless actions can my agent take?
4 in total: 1 read, 2 write and 1 destructive, such as “submit Event”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Exceptionless?
Yes. Actions like “close Session” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Exceptionless too?
Yes. The same Exceptionless connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Exceptionless into your agent.
Your users connect Exceptionless once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan