API → Tools
API → Tools lets you import an OpenAPI / Swagger spec and expose selected operations as MCP tools—without writing a custom MCP server. Tools land on the unified org /mcp endpoint and on a dedicated per-spec server at /mcp/{slug}.
This is the builder flow owned by Tools & MCP in the console (Agent Harness → Tools & MCP → API → Tools).
Provide a spec
Paste or upload OpenAPI / Swagger (JSON or YAML), or supply a public specUrl (server-side fetch; private/loopback hosts are blocked).
Pick operations
For paste/upload, the console parses the spec in the browser. Select the operations to publish (All / Reads only / None shortcuts). Only the filtered paths/methods are submitted—credentials never need to live in the agent prompt.
Import
On success, operations become tools (names from operationId, or method_path fallback). The Tools gallery and hero counts refresh immediately.
Attach credentials (optional)
Vault API credentials for the spec so the agent service can authenticate at call time. Agents never see raw keys.
Endpoints after import
| Surface | URL | Use when |
|---|---|---|
| All tools | {agent_base}/mcp | One client connection to platform + custom tools |
| This API only | {agent_base}/mcp/{slug} | Isolate a single imported API for a client or agent |
Copy the IDE MCP snippet from the Live stage, or scroll to Connect clients for full framework guides.
Operation caps and feature flags apply on the integration service (for example max operations per import). Prefer selecting only the ops your agents need—smaller catalogs are faster for models to choose from and safer under governance.
Related
- Platform tools
- Connect clients
- Gateway — governed routing for tool traffic