Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Search 600,000+ real app screens, user flows and website sections.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Mobbin MCP server connects Mobbin's library of real product screenshots to Claude, ChatGPT and any MCP-compatible agent. Three search tools return UI screens, multi-step user flows and website sections as images with metadata. It is read-only, needs a paid Mobbin plan, and each search spends AI Credits from your balance.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
openid. Nothing at the OAuth grant separates one operation from another. This matters less on a read-only server than it would elsewhere, but it means consent cannot constrain a surface that later grows.has_mcp_app: true and Mobbin documents an inline interactive gallery. Its bundle sits behind authentication, we did not authenticate, and no tool audit covers what a widget does on a user's click. Treat it as unknown.url_expires_at timestamp, so a stored link goes dead. Combined with the terms' prohibition on building a standalone content repository from retrieved content, caching results is discouraged both technically and contractually.Retry-After.ios and web. Android is not among them.help.mobbin.com returned a Cloudflare challenge to our client on 2026-08-23, though its robots.txt permits access. That is bot-blocking rather than a policy signal, but it means any troubleshooting content there is not reflected here.No. All three tools are searches, and Mobbin describes them as read-only in its own agent-plugin README. Anthropic's directory entry says the connector cannot create, change, or delete anything in your Mobbin account. Nothing in the surface writes a collection, a comment, or an account setting. It does spend AI Credits, which is the one balance a search moves.
No. Mobbin's documentation states the MCP server is available on Pro, Team, and Enterprise plans, and its marketing page says Pro and Team. Pro is 10 US dollars per month at the time of checking. A free account can browse the Mobbin website but cannot connect the MCP server, so the connector is gated behind a paid subscription.
Yes, and that is the design. Mobbin's documentation states the server returns screen images inline for AI consumption in its tool responses. Those images are screenshots of other companies' apps. Every search therefore pulls third-party visual content into your conversation, where the model reads it directly rather than following a link.
Mobbin permits personal or internal business use and integration into your own products. Its terms separately warrant that you will not use automated AI tools to create derivative works of platform materials, or to train, test, index, benchmark, or improve any generative AI or machine-learning model. We report Mobbin's stated position and do not interpret it.
Not Mobbin, by its own statement. Mobbin's terms say the platform contains screenshots relating to third parties' application interfaces, that those materials may be copyright or trademark protected by their respective owners, and that Mobbin does not claim ownership of any features within them. Citations and images may be published elsewhere only in limited extent and only with credit.
They spend AI Credits. Mobbin's terms state API and MCP usage is governed by a credit-based system, that each interaction consumes credits, and that an AI-enhanced search costs more than a basic one. Credits are non-refundable and expire per plan. Mobbin publishes no per-search rate on its pricing page, so the cost of a session is not predictable in advance.
Only identity. Mobbin's resource descriptor declared a single supported scope, openid, when checked on 2026-08-23, and its authorization server adds only profile, email, phone and offline_access. None of those names a Mobbin object or verb, so the consent screen offers no way to narrow what the connector reaches beyond signing you in.
Yes. Mobbin documents 60 requests per 60 seconds per user for MCP, against 60 per 60 seconds per workspace for its REST API. Exceeding the limit returns HTTP 429 with a Retry-After header naming the seconds to wait. Mobbin recommends respecting that header and backing off exponentially with jitter.
llms-full.txt corpus at ) · retrieved 2026-08-23screens_search parameters and response schema (retrieved 2026-08-23) · retrieved 2026-08-23mobbin-usage rules file (retrieved 2026-08-23). Packaging and configuration only; it contains no server source, so no source-level verification was possible. · retrieved 2026-08-23com.mobbin/mobbin v1.0.1 (retrieved 2026-08-23) · retrieved 2026-08-23docs.mobbin.com/robots.txt served Content-Signal: ai-train=yes, search=yes, ai-input=yes, expressly permitting the synthesis on this page; mobbin.com/robots.txt allows all agents but sets Disallow: / for GPTBot (both retrieved 2026-08-23) · retrieved 2026-08-23https://api.mobbin.com/mcp returned HTTP 401 with www-authenticate: Bearer resource_metadata="https://api.mobbin.com/.well-known/oauth-protected-resource/mcp"; that RFC 9728 descriptor returned scopes_supported: ["openid"] while sibling well-known paths returned distinct 404s; the named authorization server metadata was read at https://ujasntkfphywizsdaapi.supabase.co/auth/v1/.well-known/oauth-authorization-server (2026-08-23) · retrieved 2026-08-23Connect Mobbin once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.