Passport MCP — for builders

#What's a Passport?

Every ONBF user carries an {ONBF} Passport — their identity, wallet and chat history (with memory, connected tools & files coming next), all in one place. It's how an agent can act *on a user's behalf* ("{ONBF}" reads aloud as *on behalf*) without you ever building sign-in, accounts or connectors yourself.

When a user opens your agent they already arrive *known*: a verified identity, a prepaid wallet to pay you, and — with their consent — the context your agent needs to be useful from the first message. The Passport MCP is your read-only window into the parts of that Passport a user has granted you.

#Overview

The Passport MCP is a standard MCP server at https://onbf.ai/api/mcp speaking the Streamable HTTP transport (protocol revision 2025-03-26). You authenticate with a bearer token; the server advertises only the tools your token is entitled to.

#The session token

As a builder you almost never deal with tokens by hand. Every run ONBF dispatches to your webhook carries a session token (onbf_sess_…) in its mcp block — that's your key to the Passport for the duration of that run.

• Per-run & time-limited — it's minted for a single run and bound to one {user, conversation, project}. It stays valid only for that run's reply window (reply.expiresInSeconds), then expires.
• Zero setup — nothing for you or the user to configure; it's delivered to you in the agent.run.created payload.
• Conversation-aware — unlike a user's personal token, it can read the *current* conversation's history (the conversation:read scope) so your agent answers in context.

#Scopes

Tools declare the scopes they need; a connection sees a tool only when its token holds every required scope (so it's never advertised, not just denied at call time). The in-run session token holds all three:

#Tools

#Reading conversation history inside a run

When ONBF dispatches a run to your webhook, the payload includes an mcp block with the session token. Use it to read the current conversation so your reply stays in context — no PAT, no user setup required:

// When a run arrives, the payload includes an `mcp` block with a
// per-run session token (time-limited to the run's reply window). Use it to
// also read the CURRENT conversation's history — so your agent answers in
// context. No PAT, no user setup: it's delivered to you in the webhook.
if (event.mcp) {
  const res = await fetch(event.mcp.url, {
    method: "POST",
    headers: {
      "content-type": "application/json",
      "accept": "application/json, text/event-stream",
      "authorization": `Bearer ${event.mcp.token}`,
    },
    body: JSON.stringify({
      jsonrpc: "2.0",
      id: 1,
      method: "tools/call",
      params: { name: "get_conversation_history", arguments: {} },
    }),
  });
  const history = await res.json();
}