Apifox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFOX_AUTH | Yes | Apifox authentication token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_api_endpoint_infoA | 获取apifox的接口定义信息，数据符合OpenAPI 3.1规范。遇到例如：https://app.apifox.com/link/project/{projectId}/apis/api-{endpointId}的链接，请解析出projectId和endpointId，并调用本工具获取接口定义信息。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion with other tools. The tool's purpose is clearly defined and distinct by default.
With a single tool, naming consistency is inherently perfect. The name 'get_api_endpoint_info' follows a clear verb_noun pattern and accurately describes its function.
The server has only one tool, which is on the thin side for a typical API integration. While the tool is not trivial, a more comprehensive set (e.g., listing projects or endpoints) would be expected for this domain.
The tool provides a single operation without supporting tools for discovery or listing of projects/endpoints. Agents must already know the projectId and endpointId, which creates a significant gap for autonomous workflows.