Skip to main content
pepline ships a hosted MCP server. Point any MCP-aware assistant at it, sign in, and every capability of the API becomes tools in your chat: knowledge, catalog, flows, conversations, going live.

​
Connect

  1. In your assistant, add a custom connector (sometimes called a custom MCP server) with the URL above.
  2. Your assistant registers itself and opens Sign in with pepline in a browser.
  3. Pick the organization(s) this connection may act on — one connection can cover several — and approve.
No API key to paste; the connection acts as you, on the organizations you picked.

​
Where to add it

​
Scopes

  • Organizations — the connection acts on the orgs you picked at consent. With several, tools take an organization argument to say which one a call targets.
  • Operator — platform admins only: one connection across every organization.

​
Managing connections

Live connections appear in Settings → API → Connected apps, per organization they cover. Revoking disconnects the assistant on its next request; reconnect by signing in again.

​
Using an API key instead

For scripts and servers, the same endpoint accepts your secret API key as a Bearer token — no OAuth flow:

​
Troubleshooting

  • 401 after working fine — the connection was revoked or the org paused; sign in again.
  • Missing or outdated tools — clients cache the tool list at connect time; disconnect and reconnect.
  • organization_required errors — the connection covers several orgs; pass the organization argument the error names.