mcp-api-tester
by TinyMurky
mcp-api-tester provides tools and interfaces for LLMs to perform automated API testing. It enables LLMs to read API documentation, test endpoints, and identify potential issues quickly.
Last updated: N/A
What is mcp-api-tester?
mcp-api-tester is a collection of tools and interfaces designed to enable Large Language Models (LLMs) to perform automated API testing. It includes core tools for basic testing and advanced tools for enhanced functionality like response validation, logging, and environment management.
How to use mcp-api-tester?
To use mcp-api-tester, first integrate the minimal viable tools (listAllAPIFromDocument, getSingleAPIDetail, and callNetHTTP) into your system. Then, connect your LLM to these tools, allowing it to list endpoints, retrieve API details, generate test scenarios, and execute them. Finally, add validation, logging, and environment management tools for more comprehensive testing.
Key features of mcp-api-tester
List all APIs from documentation
Retrieve detailed API documentation
Send HTTP requests and receive results
Validate responses against schema
Log test results
Manage test environments
Use cases of mcp-api-tester
Automated API testing by LLMs
Regression testing
Fuzz testing
Security testing
FAQ from mcp-api-tester
What are the minimal viable tools?
What are the minimal viable tools?
The minimal viable tools are listAllAPIFromDocument, getSingleAPIDetail, and callNetHTTP.
What does listAllAPIFromDocument do?
What does listAllAPIFromDocument do?
It lists all available APIs (name, URL, HTTP method, etc.) from the documentation.
What does getSingleAPIDetail do?
What does getSingleAPIDetail do?
It retrieves detailed documentation of a specific API by name or path, such as request parameters and response structure.
What does callNetHTTP do?
What does callNetHTTP do?
It allows the LLM to send real HTTP requests and receive results (status code, headers, body).
Is this a replacement for traditional testing?
Is this a replacement for traditional testing?
No, while the LLM can quickly produce boundary and abnormal test cases, traditional unit tests remain essential for thorough coverage.