When a system has no Clarion integration and no MCP server, a custom toolset closes the gap. Give Clarion the API’s base URL and its documentation, and it infers the tools — which you then review before any agent sees them.
This is different from a custom MCP server. Use custom MCP when the vendor already ships an MCP server. Use a custom toolset when they don’t. Create one
- In Clarion, open Integrations → Custom toolsets and click Add.
- Give it a name — this becomes the tool namespace agents see.
- Enter the API’s base URL.
- Configure authentication:
- Provide documentation — paste text, link a URL, or upload a file.
- Click Scan. Clarion reads the docs and proposes a list of tools.
Credentials are encrypted at rest and attached to the request outside the sandbox, so an agent never sees the key it is authenticating with.
Review before enabling
The inferred tool list is a proposal, not a live surface. Every tool is disabled until you enable it, and only enabled tools are exposed to agents. Review each one’s name, description, and parameters before turning it on — the description is what an agent reasons about when deciding to call it.
Enable the narrowest set that does the job, and be deliberate about anything that writes. A tool an agent can call is a tool an agent can be talked into calling.
Rescans
Clarion hashes the normalized documentation. Rescanning after an unchanged doc is a no-op; when the docs change, you get a fresh proposal to review rather than silent drift in what your agents can do.
Use in skills
Once enabled, a custom toolset’s tools appear in the skill editor’s tool picker like any other integration’s, and can be embedded in skill content.
Delete
Delete the toolset from Integrations → Custom toolsets. Stored credentials are removed, and skills referencing its tools surface them as missing. 
