apifox_api_info
Returns the usage notes and limits for Apifox's open API.
LABSCO SUMMARY
Every call here reads: either what the token reaches, or what Apifox states it permits — none of them creates or edits an Apifox project.
apifox_check_access and apifox_check_project_access are the operational pair, answering whether the token you configured actually reaches the project you are about to work on. apifox_api_info, apifox_project_info, apifox_folder_info, apifox_environment_info, apifox_schema_info, apifox_test_info and apifox_import_export_info return Apifox's own notes on what is permitted in each area. That makes it a preflight for an Apifox integration rather than the thing that carries the integration out.
What it is
An Apifox server built around what the configured token can reach, and what Apifox's open API allows for folders, environments, data models, test cases and import/export.
What you get
- Access checked against the token you configured: apifox_check_access reports what the current token is permitted to reach, and apifox_check_project_access answers the same for one named projectId.
- Scope stated before you build against it: apifox_api_info returns the usage notes and limits for Apifox's open API, and apifox_project_info returns what this server covers and the limits it works under.
- Per-feature limits, one call each: apifox_folder_info for folder management, apifox_environment_info for environment management, apifox_schema_info for data-model management, apifox_test_info for test-case management, and apifox_import_export_info for import and export.
Requirements
An Apifox access token, supplied as APIFOX_ACCESS_TOKEN, and the projectId of the project you want the access check to run against.
Setup effort
One command plus a key — npm install -g apifox-mcp-pro, then supply credentials
USE CASES
01
Confirming a token reaches the project before you automate against it
Check the token's reach, then check it specifically against the project you intend to touch, and read what this server itself covers.
02
Working out which parts of Apifox you can automate at all
Read the open API's stated scope and then the per-area limits, so the plan matches what is actually permitted.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
apifox_check_access
Checks what the currently configured access token is permitted to reach.
apifox_check_project_access
Checks the access rights held over a named projectId.
apifox_environment_info
Returns the limits that apply to environment management.
apifox_folder_info
Returns the limits that apply to folder management.
apifox_import_export_info
Returns notes on what the import and export features cover.
apifox_project_info
Returns a description of what this Apifox MCP server can do and the limits it operates under.
apifox_schema_info
Returns the limits that apply to data-model management.
apifox_test_info
Returns the limits that apply to test-case management.
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected. Seven tools only explain what the Apifox API cannot do; only apifox_check_access and apifox_check_project_access make real calls. There is no create, update or delete support.
Requires
- npx on PATH
- APIFOX_ACCESS_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g apifox-mcp-proMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"apifox-mcp-pro": {
"command": "npx",
"args": [
"apifox-mcp-pro"
],
"env": {
"APIFOX_ACCESS_TOKEN": "<YOUR_APIFOX_ACCESS_TOKEN>"
}
}
}
}Cursor — auto setup, Claude Desktop — auto setup
TERMINAL
apifox-mcp-pro setup --both
