Mobbin MCP server icon

Mobbin

by Mobbin

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Data & Research3 tools

Search 600,000+ real app screens, user flows and website sections from an AI agent. Three read-only search tools, confirmed by Mobbin's own docs. Requires a paid Pro, Team or Enterprise plan, and each search spends AI Credits.

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.

Connect Mobbin via MCP

https://api.mobbin.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Mobbin Tools & Capabilities (3)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • A paid plan is mandatory. Mobbin's documentation restricts the MCP server to Pro, Team and Enterprise plans. A free Mobbin account cannot connect at all. We did not test what a free account sees on attempting to authorize, so the exact failure mode is unknown to us; Mobbin's REST documentation returns HTTP 403 with the message "Team or Enterprise plan required" for the plan-gated API, which is the closest documented analogue.
  • Every search spends AI Credits, and no rate is published. Mobbin's terms confirm the metering and that AI-enhanced searches cost more, but neither the pricing page nor the documentation states how many credits any call consumes, or how many a plan includes. The cost of a session cannot be worked out in advance from published sources.
  • Nothing in the surface can read the credit balance. All three tools search. There is no accounting tool, so an agent cannot check the cost before spending, and cannot report what it spent afterwards.
  • No application scopes exist. The resource descriptor declares only 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.
  • We could not read tool schemas, annotations, resources or prompts. The endpoint returned 401 to an anonymous request. Parameter detail on this page comes from Mobbin's REST OpenAPI specification for the equivalent search, which is a sibling of the MCP tools rather than the tools themselves.
  • The MCP app widget is unaudited. The directory records 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.
  • The licence is stricter than the product's framing suggests. Mobbin's terms prohibit using automated AI tools to create derivative works of platform materials or to train, benchmark or index a model on them, except as expressly permitted or with written consent — while Mobbin's own marketing shows design generation from retrieved screens. We report both and resolve neither.
  • Image URLs expire. Mobbin's REST schema gives every image an 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.
  • Rate limited to 60 requests per 60 seconds per user, returning HTTP 429 with Retry-After.
  • Coverage is iOS and web. Mobbin's REST schema enumerates exactly two platform values, ios and web. Android is not among them.
  • Mobbin's help centre could not be read. 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.

Frequently asked questions

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.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Data & Research
Developer
Mobbin
Tools
3
Domain
api.mobbin.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.