MCP integrations
Governed MCP client/server without leaking unconstrained authority.
Carina includes a governed MCP manager (go/mcp) and server surface (go/mcpserver). External tools still pass capability policy.
Client mode
Section titled “Client mode”Register MCP servers in config; their tools appear inside the session subject to the active profile. Agent actions:
`{"tool":"mcp", ...}``{"tool":"mcp_find", ...}`Inventory (operator)
Section titled “Inventory (operator)”mcp.inventory returns public MCP server names, tool names, prompt counts, and connection health.
/mcp verbosecan show public tool descriptions- Process commands, arguments, environment variables, input schemas, and private managed servers are never returned
Server mode
Section titled “Server mode”Expose a curated tool set to external MCP hosts. Prefer least privilege — do not re-export the full local kernel.
Plugin model (WASM)
Section titled “Plugin model (WASM)”WASM plugins (carina-plugin-runtime) start with zero permissions and declare capabilities in manifests. Related: plugin.inspect, plugin.run (optional signature_base64).
Source of truth
Section titled “Source of truth”- Manager:
go/mcp· server surface:go/mcpserver - Operator inventory:
mcp.inventory(public names/health only) - Plugins:
carina-plugin-runtime·docs/plugin-model.md - Related: Tools overview · Policy · JSON-RPC
- Method catalog — filter MCP / plugin methods
- Local deploy — config layout for MCP servers
Was this page helpful?
What went wrong?
Thanks for the feedback.
One vote per page is recorded during this session.