Short answer: Generate an MCP server from your OpenAPI spec, run it locally, and add it to Cursor's MCP configuration. The agent then calls typed tools that trace to real operations, instead of working from endpoint notes you paste into the chat. The whole setup takes minutes and survives contract changes because the server regenerates on save.

Why the MCP route beats pasting notes

Pasting a curl command or a list of endpoints into the chat works for that one session and is forgotten the next. The agent re-derives the same facts, and if the notes are stale, the agent is confidently wrong. An MCP server is a maintained interface: the tools are always present, typed, and gated by the same permission prompt as any other tool.

The steps

Open the OpenAPI file in the studio and compile it into an MCP server. Each tool maps to an operation and its parameters.

Run the server over a local stdio or HTTP transport.…