debug_file_system
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
LABSCO SUMMARY
Specification in, runnable test project out.
The chain is the product: the spec drives scenarios, scenarios drive code in the framework you actually use, and the scaffolding tool leaves behind a project that runs on its own afterwards. Note the licence terms in the README — personal use and contributions are free, while commercial use or redistribution needs the author's permission.
What it is
An API testing server for QA work: ingest a specification, generate scenarios, turn them into executable tests, run them, and read the report.
What you get
- ingest_spec loads an OpenAPI or Swagger document, a Postman collection or a GraphQL schema, and takes your preferred language and framework at the same time
- It analyses the specification on ingest and tells you which environment values it is going to need
- set_env_vars supplies the base URL and credentials — bearer token, API key, basic auth, or your own named values
- generate_scenarios produces test scenarios, including negative cases and edge cases unless you turn them off
- generate_test_cases turns those into executable code in your chosen combination: TypeScript with Playwright or Supertest, JavaScript with Jest or Cypress, Python with pytest or requests
- get_supported_languages lists the available language and framework pairings
- run_api_tests executes them with a concurrency limit; run_load_tests runs a load profile with a user count, ramp-up and duration
- generate_project_files scaffolds a complete runnable project with dependencies, configuration, tests and a README
- get_session_status reports progress, and get_workspace_info and debug_file_system show where generated files land
- Reports come back as HTML through MCP resources, and two prompts cover writing a test plan and analysing failures
Requirements
Node.js to run it through npx, and Python as well: the npx launcher starts the project's Python server and installs its Python dependencies with pip on first run. Credentials for the API under test are supplied through the environment tool rather than the specification. Generated files are written into your workspace.
Setup effort
One command — npx @kirti676/api-tester-mcp@latest
USE CASES
01
Getting test coverage on an API you just inherited
Load its specification, generate the scenarios, and turn them into code in the framework your team already uses.
02
Checking the failure paths, not just the happy one
Keep negative cases and edge cases in the generated set, then run them and read what broke.
03
Handing the team a project they can keep
Check which language and framework pairings exist, then scaffold a full project with dependencies and configuration.
04
Seeing how the API behaves under load
Run the same test cases as a load profile with a user count, ramp-up and duration you choose.
05
Wiring up authentication once
Set the base URL and the credential the specification asked for, and every generated test picks it up.
06
Working out where the output went
Check the workspace the server resolved, the file-system diagnostics, and how far the current session has got.
11 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
generate_project_files
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.
generate_scenarios
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_cases
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.
get_session_status
Get current session status and information with progress details.
Returns: Dictionary with current session information including progress
get_supported_languages
Get list of supported programming languages and testing frameworks.
Returns: Dictionary with supported language/framework combinations and their descriptions
get_workspace_info
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.
ingest_spec
Ingest an API specification (OpenAPI/Swagger or Postman collection) from a file. Automatically analyzes the specification and suggests required environment variables.
run_api_tests
Execute API tests and generate results.
run_load_tests
Execute load tests with specified parameters.
set_env_vars
Set environment variables for authentication and configuration.
This function automatically analyzes the API specification to provide proper validation and context about required/suggested variables.
BEFORE YOU INSTALL
What to know first
Tools you get
11 tools when we connected. Workflow examples in the documentation call get_env_var_suggestions and get_generated_tests, which the server does not expose.
Requires
- npx on PATH
- Node.js 14 or higher
- Python 3.8 or higher on PATH as python — the npx launcher starts a Python server and installs its Python dependencies with pip on first run
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 11 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @kirti676/api-tester-mcp@latestMCP Clients
Claude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"api-tester": {
"command": "npx",
"args": [
"@kirti676/api-tester-mcp@latest"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"api-tester": {
"command": "npx",
"args": [
"@kirti676/api-tester-mcp@latest"
]
}
}
}
