Apifox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_apifox_project_id_and_api_id_from_urlC | Get the project ID and API ID of Apifox from the URL. |
| get_apifox_api_infoC | Get the info of Apifox API. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves general API information, while the other extracts specific IDs from a URL. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming, making them predictable and easy to understand.
With only two tools, the server feels thin and under-scoped for an Apifox integration, lacking essential operations like creating, updating, or listing APIs, which limits its utility.
The toolset is severely incomplete for API management; it only provides retrieval and ID extraction, missing core CRUD operations (e.g., create_api, update_api, list_apis) and other typical API lifecycle functions.