Other MCP clients

Bridgable is a standard remote MCP server. Any client that supports the Model Context Protocol streamable-HTTP transport can connect — you just need the server URL and an OAuth round-trip.

The first-party guides cover Claude Code, Claude Desktop, Codex, and Cursor. Everything else (Continue, Windsurf, Zed, Cline, JetBrains AI Assistant, custom agents you've built yourself, etc.) uses the generic flow on this page.

What you need

Option 1 — CLI command (if your client supports one)

Most CLI-style agents have an mcp add subcommand. The pattern is usually:

<your-cli> mcp add bridgable --url https://mcp.bridgable.no/mcp

Examples:

# Codex (OpenAI)
codex mcp add bridgable --url https://mcp.bridgable.no/mcp

# Claude Code (alternative to the plugin marketplace)
claude mcp add bridgable --transport http --url https://mcp.bridgable.no/mcp

If your client supports mcp login or similar, run that next. Otherwise the OAuth browser flow triggers automatically on the first tool call.

Option 2 — Edit the config file directly

If your client uses a JSON config (Continue, Cline, Windsurf, Zed, custom apps), add this entry to its mcpServers block:

{
  "mcpServers": {
    "bridgable": {
      "type": "http",
      "url": "https://mcp.bridgable.no/mcp"
    }
  }
}

Some clients use slightly different keys — transport: "streamable-http", serverUrl, or a nested transport.type. Check your client's docs; the URL is the same.

Restart the client. On the first tool call, a browser tab opens for sign-in.

Authenticate

Whichever option you used:

1. The browser opens on bridgable.ai.
2. Sign in (or create an account — free tier is 50 queries / month).
3. Approve the connection.
4. The tab closes and your client is connected.

Verify

Ask your agent something OpenBridge-flavored:

> How do I use obc-slider in React?

It should call bridgable_query and return real component documentation. If the response is generic or it hallucinates props, the connection didn't take — check your client's MCP logs and re-run the OAuth flow.

Troubleshooting

"OAuth loop" or token expired. — Remove the bridgable MCP entry, restart the client, re-add, and sign in fresh.

"Tools not appearing." — Your client may need a restart after adding the server, and a few clients only show tools after the OAuth handshake completes. Trigger one tool call manually to force the flow.

Streamable-HTTP not supported. — Bridgable does not ship a local stdio server. If your client only supports stdio MCP servers, wrap the remote URL with a community adapter such as mcp-remote:

{
  "mcpServers": {
    "bridgable": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.bridgable.no/mcp"]
    }
  }
}

This proxies stdio ↔ streamable-HTTP locally so older clients can talk to the hosted server.

Want a first-party guide?

If you're using a client that isn't covered here and the generic flow is painful, open an issue at github.com/thomsoren/bridgable-plugin and we'll add a dedicated page.