Sidetracker for AI agents
Sidetracker is a cookie-free web analytics platform tracking visitors, sales funnels, and customer journeys without relying on cookies. Site owners use it for privacy-friendly traffic and lead tracking. 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 Sidetracker.
Check details on a tracked list
Pull the details of a specific visitor or lead list before deciding how to segment it.
Review all lists before exporting
List every tracked list on the account as a read-only check before pulling data out.
Generate a QR code for a campaign
Create a QR code tied to a tracked link for use in a print or offline campaign.
3 Sidetracker actions, graded by risk.
Every Sidetracker action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- sidetracker.get_listsGet Lists
- sidetracker.get_list_detailsGet List Details
write
1Create and change things. Allow, or ask the user first.
- sidetracker.generate_qrcodeGenerate QR Code
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Sidetracker in three steps.
- 01Your users connect SidetrackerThey add their Sidetracker api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “generate QR Code” can wait for the user to approve.
- 03Any agent can actYour agent calls Sidetracker through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('sidetracker', { read: 'allow', write: 'ask', // generate_qrcode destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Sidetracker connects.
Users add their Sidetracker 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 Sidetracker 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 Sidetracker from any agent.
Sidetracker and Arc0, answered.
Can I use Sidetracker with Claude, ChatGPT or Cursor?
Yes. Connect Sidetracker 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 Sidetracker actions you allow.
How do users connect Sidetracker?
Users add their Sidetracker 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 Sidetracker actions can my agent take?
3 in total: 2 read, 1 write and 0 destructive, such as “generate QR Code”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Sidetracker?
Yes. Allow read actions and deny writes in the Sidetracker policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Sidetracker too?
Yes. The same Sidetracker connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Sidetracker into your agent.
Your users connect Sidetracker once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan