Mobbin MCP connector for AI agents

CALL ANY TOOL

3 tools covering search.

mobbinmcp_search_flows

Search mobbin for multi-step user flows (e.g. onboarding, ch

Search mobbin for multi-step user flows (e.g. onboarding, checkout) using natural language. returns flow screens with inline images.

Parameters

Name

Type

Required

Description

platform

string

Required

Platform to filter results by.

query

string

Required

Natural language query to search for user flows.

image_format

string

Optional

Format for the returned flow screen images.

limit

integer

Optional

Maximum number of results to return.

page

integer

Optional

Page number for pagination.

mobbinmcp_search_screens

Search mobbin for ui screens using natural language. returns

mobbinmcp_search_sections

Search mobbin for website sections (e.g. about, pricing, foo

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mobbinmcp")

mcp = MultiServerMCPClient({
    "mobbinmcp": {
        "url": "https://mcp.scalekit.com/mobbinmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mobbinmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/mobbinmcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mobbinmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/mobbinmcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mobbinmcp")
# Connect to MCP at https://mcp.scalekit.com/mobbinmcp
# Pass: Authorization: Bearer + token

Try these prompts

Copy any prompt into your agent. Each maps directly to a Mobbin tool. Click to copy, paste into your agent, done.

Get started

Copy the prompt

Copied

What can I do with Mobbin MCP?

Copy the prompt

Copied

Show me all available tools in Mobbin MCP.

SEE HOW AUTH WORKS

Your users connect once. Their Mobbin credentials stay vaulted, every call is scope-checked, and every action is logged.

1

Authorize

Your user connects

Mobbin MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

Mobbin MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

Mobbin MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

Mobbin MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Mobbin as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Mobbin OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Mobbin?
Yes. Pass a tool name filter to listScopedTools so the design agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Mobbin.

What happens when a user revokes Mobbin access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Whose Mobbin subscription do design searches use?
The authorizing user's. Screen, flow, and section searches run with that user's Mobbin plan, so Pro library access stays licensed per designer.

Mobbin MCP

Mobbin MCP tools for AI agents