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.
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.
- 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.
An Apifox access token, supplied as APIFOX_ACCESS_TOKEN, and the projectId of the project you want the access check to run against.
One command plus a key — npm install -g apifox-mcp-pro, then supply credentials