Use CALIBER
MCP servers
The practical path for connecting CALIBER to MCP servers, verifying discovered tools, and governing remote tool use.
Use this page when the practical question is how to connect CALIBER to an MCP server, verify the discovered tools, and govern what remote tools may do.
At a glance
| Task | Start here | Deep reference |
|---|---|---|
| register or configure a server | define connection and transport details | MCP architecture |
| verify tool discovery | inspect the discovered inventory | MCP architecture |
| govern remote actions | apply approval and policy boundaries | Trust and governance |
| use MCP tools in assistant or workflows | wire them into the target surface | Aria assistant, Workflows |
1. What MCP adds to CALIBER
MCP lets CALIBER connect to externally hosted tool surfaces without baking each integration directly into the core product. That increases power, but it also raises the need for connection tests, inventories, and policy enforcement.
2. Common tasks
| You want to... | Read this next |
|---|---|
| connect a new MCP server | MCP architecture |
| confirm the right tools are visible | MCP architecture |
| allow only a narrow capability such as issue creation | Trust and governance |
| debug an agentic flow using MCP tools | Developer troubleshooting |
3. Common failure modes
| Symptom | First thing to check |
|---|---|
| The server connects but tools do not appear | discovery or transport mismatch |
| Tools appear but cannot run | policy, approval, or secret-source configuration |
| The same tool behaves differently across environments | endpoint, credentials, or server version drift |