Import an OpenAPI document as a tool set
Parses an OpenAPI 3.0 or 3.1 document (JSON or YAML, sent in the body; it is never fetched from a URL) and stores its supported operations as tools an agent can call. Operations that cannot be called faithfully are listed in skipped_operations; selecting one with operations rejects the import instead. Credentials are never part of the document: reference a credential vault server registered for the API’s base URL.
Authorizations
Gateway auth: send Authorization: Bearer <mka1-api-key>. For multi-user server-side integrations, you can also send X-On-Behalf-Of: <external-user-id>.
Headers
Optional external end-user identifier forwarded by the API gateway.
Body
The OpenAPI 3.0 or 3.1 document, as an object or as JSON or YAML text (at most 4 MiB).
1Label for the tool set. Defaults to a slug of the document's info.title.
^[a-zA-Z0-9_-]{1,64}$The API's public base URL. Defaults to the document's first server, with variables set to their defaults.
2048operationIds to import. Defaults to every supported operation (at most 128).
1 - 128 elements1 - 64Credential vault server, registered for the API's base URL, whose credential authenticates every call.
Credential of mcp_server_id to use. Defaults to the server's newest active credential at run time.
Response
OpenAPI tool set
agent.openapi_tool_set The document's info.title.
The document's info.version.
The normalized tool definition an agent run sends. It holds credential references, never credential values.
Operations of the document that were not imported, and why.
What the document's security schemes expect the vault credential to send.