Log in
DocsAny MCP client (URL and token)

Any MCP client (URL and token)

Any client that can call a remote MCP server over HTTP can use 0bridge. Level: bearer token. Last checked 2026-10-01.

Last updated

Open in ClaudeOpen in ChatGPT

With a sign-in#

If the client supports OAuth for MCP servers, give it the URL. It registers itself, opens a 0bridge page, and you click Allow.

https://0bridge.dev/mcp

With a token#

If the client takes a URL and a header, or only a token, mint an app token and send it as a bearer token.

  1. Open the dashboard → Settings → Devices → New app token.
  2. Name it after the client. Pick what it may do: all tools or read-only tools, whether it may see history, and whether it may control agents. The defaults are your services' tools, no history, no agent control, valid for 90 days. Confirm it's you when asked.
  3. Copy the token. It is shown once.
  4. Send it on every request:
Authorization: Bearer <your token>

What a token can't do#

  • Create other tokens, or change your vault. Only the dashboard, with you signed in, does that.
  • Anything outside its scope. A read-only token sees only tools marked as read-only; a token with no history scope never sees the history tools.
  • Work after it expires. App tokens last at most a year, 90 days by default.

Revoke it#

Settings → Devices lists every token with its scope and expiry; revoke one there and it stops at once, and any live agent connection on it is closed.

A project's own endpoint#

A repo has its own endpoint, https://0bridge.dev/mcp/p/<id>, with a token that opens only that project. 0b project link sets it up: Projects.

PreviousPerplexity