Getting started
Stand up governed tools for your agents in four steps.
Connect integrations
In the console, open Connectors and enable the providers your agents need (ticketing, observability, cloud, docs, and so on). A connector must be active with credentials before it appears as a *_tool or a specialist agent on Tools & MCP.
See the integrations catalog for coverage.
Get an org API key
Create a key in Account Settings — Tokens and API keys. Clients send it as x-api-key (never embed keys in prompts or agent context).
Open Tools & MCP
Go to Agent Harness → Tools & MCP. Confirm the hero shows a live endpoint and tool/agent counts. Browse the Tools gallery for what your org currently exposes.
Point a client
- IDE / MCP client — Cursor, Claude Code, Codex: paste the sample MCP config from Connect (see Connect clients).
- Agent framework — use the Harness SDK
harness.tools()adapters for LangChain, Agno, Google ADK, and related stacks.
Ask something that exercises a connector tool (for example list open incidents) and confirm the call succeeds under your org key.
Production MCP endpoint defaults to https://production-api.exemplar.dev/mcp. Dev and local hosts resolve to their matching agent-service bases. Override with EXEMPLAR_MCP_URL when using the SDK.
Next
- Platform tools — what ships on
/mcp - API → Tools — turn your OpenAPI into MCP tools
- Connect clients — IDE and framework snippets