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 |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kirti676/api_tester_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server