Tools
MCP servers and custom OpenAPI tools your Agents can call.
Studio → Settings → Tools connects external capabilities an Agent can call mid-run. There are two kinds, both bindable to an Agent the same way.
MCP servers
Connect an MCP server by name and URL, then pick how it authenticates:
dcr— Dynamic Client Registration; Elizon discovers and registers an OAuth client with the server automatically.oauth_manual— you supply a client ID and secret yourself.none— no auth.
You can also attach custom headers, each either a fixed value or a {{secret.KEY_NAME}} expression (see Secrets) — useful for an API key the server expects in a header rather than through OAuth. A connected server's tools are discovered automatically; Refresh re-syncs them if the server's tool list changes.
Custom (OpenAPI) tools
Give Elizon an OpenAPI/Swagger spec — paste it directly, or point at a URL and let Elizon fetch it — and every operation in it becomes a callable tool. Authentication is one of:
- None
- Header — Basic, Bearer, or a custom header
- Query parameter
Scope
Both kinds can be created at the organization level or scoped to one project.
Usage is metered per call
Every tool invocation — MCP or custom — is recorded as usage and counts toward a total
Budget (there's no tool-specific meter group to cap separately from
everything else). A tool an Agent calls heavily is worth keeping an eye on in the Usage & Cost
dashboard the same way token usage is.