Mobbin for AI agents
Mobbin is a design inspiration library of app screens and user flows that designers search for reference patterns when starting a new project. 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 Mobbin.
Search for a UI pattern
Search screens for a specific pattern, like onboarding flows, to reference in a design.
Find flows from a similar app
Search flows from apps in a given category to compare approaches, read-only.
Pull sections for a design review
Search sections matching a component type to gather references for a critique.
3 Mobbin actions, graded by risk.
Every Mobbin action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- mobbin.search_flowsSearch flows
- mobbin.search_screensSearch screens
- mobbin.search_sectionsSearch sections
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.
Mobbin in three steps.
- 01Your users connect MobbinThey sign in to Mobbin on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Mobbin through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('mobbin', { 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 Mobbin connects.
Mobbin runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Mobbin through the same endpoint, policies and audit log as every other app.
The same Mobbin 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
- OAuth 2.0 (MCP)
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Mobbin from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Mobbin and Arc0, answered.
Can I use Mobbin with Claude, ChatGPT or Cursor?
Yes. Connect Mobbin 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 Mobbin actions you allow.
How do users connect Mobbin?
Mobbin runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Mobbin through the same endpoint, policies and audit log as every other app.
Which Mobbin actions can my agent take?
3 in total: 3 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Mobbin?
Yes. Allow read actions and deny writes in the Mobbin policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Mobbin too?
Yes. The same Mobbin connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Mobbin into your agent.
Your users connect Mobbin 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