Tools & MCP
Tools & MCP publishes connector and platform capabilities as governed MCP tools on one org endpoint. Credentials stay vaulted; calls share identity, policy, and audit.
Console: console.exemplar.dev → Marshal → Tools & MCP. Catalog: exemplar.dev/integrations .
Two jobs
| Job | Start here |
|---|---|
| IDE / MCP client — Cursor, Claude, Codex | Connect clients — copy config from Console |
| Agent framework / SDK — LangChain, Agno, ADK, … | Frameworks (SDK) — harness.tools() |
Govern which MCP tools IDE coding agents may call with Relay MCP control.
How it works
- Connect — Enable providers; credentials stay vaulted.
- Publish — Unified tools (
memory_tool,pagerduty_tool, …) appear on/mcp. - Consume — Point an MCP client or
harness.tools()at the endpoint shown in Console Connect. - Optional A2A — Hand a whole turn to a connector specialist when an orchestrator should delegate.
Default production MCP URL: https://production-api.exemplar.dev/mcp. Prefer the URL and headers copied from Console for your org.
Topics
Related
- Marshal — prompts, skills, memory beside the same tools
- AI Gateway — LLM routing
- Marshal SDK —
harness.tools() - Relay MCP control — IDE allow/deny for MCP tools
- Tokens — org API keys for MCP clients
Last updated on