Custom MCP servers & APIs

When the product you need isn't in the directory, the Connections tab has a "Something we don't list yet" path with two options.

Connect an MCP server

Give it a name, the server URL, and an auth header. OpenAgent speaks the MCP protocol as a client: it initializes, lists the server's tools, and folds them into the back office's toolset. Tools the server marks read-only run freely; the rest pause for approval like any write.

Name:    Internal ops server
URL:     https://mcp.yourcompany.com/mcp
Header:  Authorization: Bearer <token>
→ its tools appear in back-office runs alongside the directory's

Connect a raw API

For a plain HTTP API: name it, set the base URL and auth header, and the back office gets a request action for it — fenced to that host. The AI can compose calls against your API, and only your API; the credential can't be steered anywhere else.

The other direction

This page is about plugging other systems into OpenAgent. For pointing an external AI at OpenAgent itself — Claude or Cursor running your whole front office — see the hosted MCP server.