Platform tools
Every org MCP server exposes a flat catalog of unified tools. Clients discover them with MCP tools/list against {agent_base}/mcp.
Call shape
All unified tools share the same pattern:
{
"action": "list",
"params": {}
}Actions are tool-specific (for example list, get, create, query). The Tools & MCP gallery in the console shows each tool’s summary, full description, and action chips.
Categories
| Category | Examples | Role |
|---|---|---|
| Memory | memory_tool | Long-term org / user / session memory |
| Skills | skills_tool | Install and invoke registered skills |
| Prompts | prompt_tool | Resolve versioned prompt templates |
| Knowledge / RAG | documentation_tool | Query org documentation collections |
| Connector | pagerduty_tool, jira_tool, datadog_tool, aws_tool, … | Live actions on connected integrations |
Connector tools appear when the matching provider is connected and active. Core tools (memory_tool, skills_tool, prompt_tool, documentation_tool) are always part of the platform surface.
Efficiency & governance
- One connection — frameworks and IDEs load the catalog once instead of N vendor SDKs.
- Scoped credentials — connector secrets stay in the vault; agents never need raw keys in context.
- Shared policy — the same Harness gateway / guardrails and Relay MCP allowlists apply depending on the channel (production agents vs IDE coding agents).
- Live catalog — Tools & MCP refreshes from the org MCP server; the console falls back to a built-in list only if live discovery fails.
Pair platform tools with Memory, Skill management, and Prompt management so agents recall and act with the same registries operators edit in the console.
Related
- Getting started
- API → Tools — add custom OpenAPI tools to the same
/mcp - Connect clients
Last updated on