Tools & MCP

Tools & MCP is the connector surface for harness agents — built-in platform tools, the Exemplar MCP endpoint, and connector A2A agent cards so agents can act on real systems with credentials you control

Exemplar

How this harness capability fits the Exemplar platform—governed agent operations, not a standalone prompt playground.

Why Exemplar

Without a shared tool plane, every agent team hand-wires Jira, PagerDuty, Datadog, and cloud APIs—different auth, no shared audit, token-heavy glue.

Exemplar publishes connectors as unified MCP tools on one governed endpoint, so frameworks and IDE clients share the same catalog, policy, and audit trail.

What Exemplar delivers

A flat catalog of unified tools with one { action, params } call shape—platform tools plus connector *_tool actions on {agent_base}/mcp.

A2A specialist agents per connector—agent cards and JSON-RPC endpoints orchestrators can hand a whole turn to.

How teams use it

Enable connectors; unified tools appear on the org MCP endpoint for Cursor, Claude, and harness.tools() without per-vendor SDKs.

Import your own OpenAPI specs to publish custom endpoints as MCP tools behind the same governance.

Capability checklist

Built-in platform tools—memory, skills, prompts, and documentation—on one org MCP endpoint

Connector tools published automatically for Cursor, Claude, and agent frameworks

Connector A2A agent cards for delegating whole turns to integration specialists

Credentials stay vaulted—agents get live actions without raw keys in context

Developer guide

Official documentation on docs.exemplar.dev for this capability.

Open developer guide

Contact sales

Harness Platform is scoped per deployment. Talk to us about this feature.