Summary
The definition arrives as OpenAPI 3.1, which is the shape the rest of your tooling already reads.
One tool doing one thing: a project and endpoint pair goes in and a specification fragment comes out, with nothing here that lists projects, searches endpoints or writes anything back into Apifox. What it removes is the transcription step, because the ids are parsed straight out of the link someone pasted into the conversation.
What it is
A single-tool Apifox reader: a project id and an endpoint id return that endpoint's definition conforming to OpenAPI 3.1.
What you get
- get_api_endpoint_info, which returns an Apifox endpoint definition in a form conforming to the OpenAPI 3.1 specification.
- The identifiers taken from the share link rather than looked up separately: the projectId and endpointId come out of an app.apifox.com endpoint URL.
Requirements
APIFOX_AUTH, and access to the Apifox project the endpoint belongs to.
Setup effort
One command plus a key — npx @juzi965/apifox-mcp-server, then supply credentials