ToolPlexerIntegrations Overview
Add ToolPlexer capabilities to your product.
Bring ToolPlexer's capability marketplace into your product. Choose the model that matches your users, billing, and control requirements.
ToolPlexer ships three first-party surfaces: the HTTP API, hosted MCP, and the CLI. The direct, user-owned, and proxy pages below describe ways to compose those surfaces into your product. ToolPlexer does not currently provide a managed customer proxy or a public OAuth application flow.
Integration methods
Use ToolPlexer directly
Call the API server-to-server as an internal building block. Your users never see ToolPlexer or handle a ToolPlexer key.
When to use direct access · Set up direct access
Hosted MCP
Connect user-owned agents to ToolPlexer through the hosted Streamable HTTP MCP endpoint. This is the fastest path when your users already work in Claude, Codex, Cursor, or another MCP client.
See Set up MCP.
User-owned access
Let users bring their own ToolPlexer workspace and key. ToolPlexer currently uses dashboard API keys; keep user credentials in your backend and call the API on behalf of the signed-in user.
When to use user-owned access · Set up user-owned access
Build a proxy
Put your own backend in front of ToolPlexer when you need custom billing, validation, allowlists, response shaping, or audit logging.
When to use a proxy · Set up a proxy
Choosing a model
| Requirement | Recommended model |
|---|---|
| ToolPlexer is invisible infrastructure inside your product | Direct access |
| Users already have an agent and want a ready-made connection | Hosted MCP |
| Each user owns their workspace and spend | User-owned access |
| You control billing, policy, and the exposed catalog | Proxy |
Security boundary
Never put a ToolPlexer key in browser code, a mobile bundle, a public prompt, or source control. Keep credentials server-side and expose only the capabilities your product intends to support.