Connect clients
Point MCP clients at the org endpoint. Prefer the URL and headers shown in console Marshal → Tools & MCP → Connect. Use an org API key from Tokens.
Default production endpoint: https://production-api.exemplar.dev/mcp.
For IDE agents that should know Marshal and Relay workflows: Install IDE agent skills.
Cursor / Claude Code (HTTP MCP)
{
"mcpServers": {
"exemplar-mcp": {
"transport": "http",
"url": "https://production-api.exemplar.dev/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}For agent frameworks, use Frameworks with Marshal SDK (harness.tools()).
Per-spec MCP servers
After API → Tools import, Console lists:
/mcp— all platform + custom tools/mcp/{slug}— only that imported API
Use the narrower server when you want a smaller tool catalog for a specialized agent.
Optional A2A
Orchestrators can load MCP tools for discrete actions and optionally delegate a whole turn to a connector specialist. Card and A2A URLs are under Tools & MCP → A2A. Details: Connector agents.
Relay still governs which MCP tools IDE coding agents may call. Tools & MCP publishes the catalog; Relay MCP control is the allow/deny layer.