documentation
From an API to a governed MCP server in four minutes
Bridge reads your spec, proposes tools, and puts a policy engine in front of every call. This walkthrough covers the first server end to end.
1
Create a server from a source
In the console, choose New server and point Bridge at an OpenAPI document or a Postgres connection string. Bridge introspects it and proposes one tool per operation. Nothing is exposed yet.
consolecopy
New server name Northbeam Ads source OpenAPI · https://api.northbeam.io/openapi.json auth Bearer (stored encrypted, server side) → srv_8842f1 · 34 operations · 0 exposed
2
Expose the tools you mean to expose
Read operations are a safe starting set. Write operations should get a policy before they get traffic. Toggle each tool under Server → Tools.
consolecopy
Server → Tools list_campaigns read exposed get_campaign read exposed update_campaign_budget write exposed → 12 tools exposed
3
Attach a policy and dry-run it
Policies allow a call, hold it for review, or deny it. Dry-run replays your recent audit traffic against the draft so you see what would change before it goes live.
consolecopy
Access → Policies → operator-write dry-run against last 7 days → 1,204 calls · 1,190 allow · 12 review · 2 deny
4
Publish and issue a key
Publish takes effect on the next request. Issue a scoped API key and hand the endpoint to any MCP client.
consolecopy
Publish srv_8842f1 → live at https://api.kaiv.ai/api/bridge/mcp/northbeam-ads API keys → Issue key → kv_live_7Qm2… (shown once)
next