API Tester 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ingest_specA | Ingest an API specification (OpenAPI/Swagger or Postman collection) from a file. Automatically analyzes the specification and suggests required environment variables. |
| set_env_varsB | Set environment variables for authentication and configuration. This function automatically analyzes the API specification to provide proper validation and context about required/suggested variables. |
| generate_scenariosB | Generate test scenarios from the ingested API specification. NOTE: This function automatically saves the generated scenarios to both the output directory and the current workspace for easy access. |
| generate_test_casesA | Generate executable test cases from scenarios using the language and framework specified in ingest_spec. NOTE: This function automatically saves the generated test cases to both the output directory and the current workspace for easy access. |
| run_api_testsC | Execute API tests and generate results. |
| run_load_testsC | Execute load tests with specified parameters. |
| get_supported_languagesB | Get list of supported programming languages and testing frameworks. Returns: Dictionary with supported language/framework combinations and their descriptions |
| generate_project_filesB | Generate complete project files using the language and framework specified in ingest_spec. Automatically reuses test cases and parameters from the current session if available. |
| get_workspace_infoA | Get information about the current workspace directory and file generation locations. Returns: Dictionary with workspace information including current directory and whether it was set from an ingested API specification file. |
| debug_file_systemA | Get comprehensive workspace information and file system diagnostics. Shows where files will be saved without creating directories. Returns: Dictionary with workspace information and file system diagnostic details |
| get_session_statusB | Get current session status and information with progress details. Returns: Dictionary with current session information including progress |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_api_test_plan | Generate a comprehensive API test plan template. |
| analyze_test_failures | Analyze test failure patterns and suggest improvements. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_reports | List all available test reports. Returns: Resource containing a list of available reports |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but debug_file_system and get_workspace_info both provide workspace information, which could cause minor confusion. The descriptions help differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., generate_scenarios, run_api_tests). No mixed conventions or ambiguous verbs.
11 tools is appropriate for an API testing server. Each tool serves a clear purpose in the workflow without being excessive or insufficient.
The tool set covers the core API testing workflow: ingestion, setup, scenario/test generation, execution, and diagnostics. Minor gaps include inability to view generated content directly or delete resources, but these are not critical.