Exemplar
Book a demo
HomeMarshal PlatformFeature

Tools & MCP

Marshal · Platform tools, MCP, and connectors

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

Marshal · Tools & MCP

How Tools & MCP works

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

Agents discover tools and connectors (sky rails); invocations hit MCP/A2A with org credentials and policy (orange rails).

Connector catalog

54 connectors on one MCP endpoint

Enable a connector once—Tools & MCP publishes it as governed tools for agents, Cursor, Claude, and your frameworks

GitHubGitHub
GitLabGitLab
BitbucketBitbucket
JenkinsJenkins
CircleCICircleCI
Azure DevOpsAzure DevOps
GitHub WorkflowsGitHub Workflows
GitLab PipelinesGitLab Pipelines
TerraformTerraform
PulumiPulumi
Terraform CloudTerraform Cloud
AWSAWS
GCPGCP
AzureAzure
KubernetesKubernetes
Red Hat OpenShiftRed Hat OpenShift
ArgoCDArgoCD
PrometheusPrometheus
GrafanaGrafana
DatadogDatadog
New RelicNew Relic
DynatraceDynatrace
SentrySentry
StatuspageStatuspage
PagerDutyPagerDuty
OpsGenieOpsGenie
ServiceNowServiceNow
JiraJira
incident.ioincident.io
SnykSnyk
TrivyTrivy
SonarQubeSonarQube
CheckmarxCheckmarx
StackHawkStackHawk
WizWiz
CodecovCodecov
JFrogJFrog
SBOMSBOM
LaunchDarklyLaunchDarkly
SplitSplit
AWS CostAWS Cost
KubeCostKubeCost
OpenCostOpenCost
Azure ADAzure AD
Google WorkspaceGoogle Workspace
OktaOkta
OneLoginOneLogin
JumpCloudJumpCloud
SlackSlack
LinearLinear
NotionNotion
ConfluenceConfluence
GitHub CopilotGitHub Copilot
MCP ServerMCP Server

Browse the full integrations catalog

Why it matters

Built for production agents—not prompt playgrounds

How this harness capability fits the Exemplar platform: one identity, one policy layer, and one audit trail across console, MCP, and SDK.

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 (opens in a new tab)

Get started

Put Tools & MCP to work with the rest of Marshal—or talk to us about your agent stack.

Book a demoBack to MarshalTalk to founder

From the blog

Related posts on exemplar.dev.