Popupsmart for AI agents
Popupsmart is a no-code popup builder for collecting website leads through targeted on-site campaigns. Marketing teams use it to grow email lists without a developer. 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 Popupsmart.
Export leads from a campaign
Pull the list of leads collected by a connected popup campaign into another system.
Check lead volume read-only
Review how many leads a campaign has collected before deciding to run it longer.
Sync new leads to a CRM
Pull newly captured leads so they can be added to a sales follow-up list.
1 Popupsmart actions, graded by risk.
Every Popupsmart 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.
- popupsmart.list_leadsList Leads
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Popupsmart in three steps.
- 01Your users connect PopupsmartThey add their Popupsmart api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Popupsmart through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('popupsmart', { 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
How Popupsmart connects.
Users add their Popupsmart 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 Popupsmart 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 Popupsmart from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Popupsmart and Arc0, answered.
Can I use Popupsmart with Claude, ChatGPT or Cursor?
Yes. Connect Popupsmart 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 Popupsmart actions you allow.
How do users connect Popupsmart?
Users add their Popupsmart 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 Popupsmart 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.
Can I make my agent read-only in Popupsmart?
Yes. Allow read actions and deny writes in the Popupsmart policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Popupsmart too?
Yes. The same Popupsmart connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Popupsmart into your agent.
Your users connect Popupsmart 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