Issue an API key
Issue an API key from the admin dashboard.
See the API key guide as well.
Call the REST API
Call the standard REST endpoints.
REST is for listing, retrieving, registering, and managing tools. Tool execution is done
via MCP JSON-RPC
tools/call (POST /mcp). See the MCP SDK examples below.MCP SDK integration (Node.js)
To integrate programmatically, use the official MCP SDK.
Install
client.js
BYOAPI — register your own API (coming soon)
Any API with an OpenAPI spec can be registered as a Bridger tool. (coming soon)
See the BYOAPI concept doc for the full flow.
Register an API
Either
spec_url (remote spec) or spec_raw (inline spec string) plus name is required.
Registration is processed asynchronously and the response returns a job_id.
Check progress with GET /api/v1/register/:id/status.API reference summary
| Method | Path | Description |
|---|---|---|
GET | /api/v1/tools | List registered tools |
GET | /api/v1/tools/:toolId | Get a single tool |
POST | /api/v1/register | BYOAPI registration ({spec_url|spec_raw, name, auth, visibility}) |
GET | /api/v1/register/:id/status | BYOAPI registration job status |
GET | /registry/servers | Preset server (MCP group) catalog |
GET | /registry/tools | Flattened tool list |
GET | /mcp/sse | MCP SSE event stream |
POST | /mcp | JSON-RPC (tools/list, tools/call) — tool execution |