makecallable_>

/ 02 · docs

OpenAPI import

MakeCallable turns OpenAPI operations into MCP tools. You paste JSON once; agents get tools without a rewrite.

What you need

  • OpenAPI 3.x JSON (not YAML yet)
  • Paths with operationIds when you can — clearer tool names
  • Request parameters and JSON body schemas for the actions agents should call
  • Optional securitySchemes so we know how your API expects auth

What you don’t have to change

  • You don’t rebuild the API as “MCP-native”
  • You don’t learn the MCP protocol before shipping
  • You don’t maintain a second agent-only surface
  • You don’t strip existing human REST clients

Keep the product API. Expose the operations that matter. Measure what agents actually call.

What gets mapped

On import we read:

  • path / query / header parameters
  • request body schemas
  • security schemes (for upstream mapping)
  • operation summaries → tool descriptions

Tools appear on the project immediately. Re-import after you change the spec.

Tips for cleaner tools

  • Prefer clear operationIds (search_jobs, not get_v1_items_itemId)
  • Describe required fields tightly — agents follow schemas
  • Omit internal-only or destructive ops you don’t want agents to see
  • Use one base server URL that matches the project’s upstream host

Limits

Early seats have per-user caps on projects, tools, and call volume. If import fails or tools look empty, see Troubleshooting.

Next: Upstream auth & base URL