Connect clients

Point MCP clients and agent frameworks at the same governed endpoint. Replace the URL with your deployment’s MCP URL (shown in Tools & MCP) and use an org API key from Account Settings.

Default production endpoint: https://production-api.exemplar.dev/mcp.

Cursor / Claude Code (HTTP MCP)

{
  "mcpServers": {
    "exemplar-mcp": {
      "transport": "http",
      "url": "https://production-api.exemplar.dev/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Python SDK (any framework)

pip install exemplar-harness-sdk
export EXEMPLAR_API_KEY="eis_your_org_api_key"

from exemplar_harness import Harness
 
harness = Harness.from_env()
tools = harness.tools()  # uses EXEMPLAR_MCP_URL or {base}/mcp
mcp_url = tools.mcp_url

Framework extras load MCP tool adapters—for example:

pip install "exemplar-harness-sdk[langchain]"
# or [agno], [google-adk], …

from exemplar_harness import Harness
 
harness = Harness.from_env()
toolkit = harness.tools()
mcp = toolkit.for_provider("langchain")  # or "agno", …
mcp_tools = await mcp.get_tools()
# memory_tool, skills_tool, pagerduty_tool, …

See SDK client usage and the live demos in exemplar-harness-sdk  (examples/live/agno_demo.py, and so on).

Mixed MCP + A2A

Typical pattern for an orchestrator:

1. Load unified MCP tools for broad, efficient action access.
2. Optionally wrap a connector’s A2A endpoint as a single “ask specialist” tool for multi-step vendor reasoning.

Auth headers for A2A calls: x-api-key, plus org / user headers as required by your deployment. Card and A2A URLs for each slug are listed under Tools & MCP → Agents.

Per-spec MCP servers

After API → Tools import, you can point a client at:

• {agent_base}/mcp — all platform + custom tools
• {agent_base}/mcp/{slug} — only that API’s tools

Use the narrower server when you want a smaller, safer tool catalog for a specialized agent.

Related

• Getting started
• Platform tools
• Harness SDK
• DevX Assist Copilot — MCP connect patterns in the IDE