mcp-api-toolkit
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_openapiB | Parse and validate an OpenAPI/Swagger specification from JSON/YAML string or URL. Returns detailed information about the API including endpoints, methods, and schemas. |
| list_endpointsA | Extract and list all API endpoints from a previously parsed OpenAPI specification. Returns all paths, methods, summaries, and operation IDs. |
| test_api_endpointB | Execute an API request and test an endpoint with optional validation. Returns response status, data, timing, and validation results. |
| generate_sdkC | Generate a client SDK in TypeScript, Python, JavaScript, or Go from an OpenAPI specification. Creates ready-to-use client libraries with type safety. |
| generate_mock_dataC | Generate mock data based on a JSON schema or OpenAPI schema definition. Useful for testing and development. |
| generate_api_docsB | Generate markdown documentation from an OpenAPI specification. Creates human-readable API documentation with examples. |
| validate_api_responseC | Validate an API response against an OpenAPI schema definition. Checks if the response matches the expected schema. |
| batch_test_endpointsB | Test multiple API endpoints from an OpenAPI spec in batch. Useful for smoke testing or API health checks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes: SDK generation, doc generation, validation, batch testing, parsing, listing, single endpoint testing, and mock data. However, test_api_endpoint and batch_test_endpoints overlap in testing functionality, and validate_api_response and test_api_endpoint both involve validation, which could cause slight confusion.
Tool names are mostly in snake_case with a verb_noun pattern (generate_sdk, generate_api_docs, validate_api_response, etc.). One deviation is parse_openapi (verb_noun but noun is OpenAPI rather than a typical object) and list_endpoints, but overall consistency is high.
With 8 tools, the count is well-scoped for an API toolkit. Each tool corresponds to a distinct, useful operation in the API development lifecycle, and there is no apparent redundancy.
The toolkit covers parsing, listing, testing (single and batch), validation, SDK generation, documentation, and mock data. It misses operations like comparing specs, transforming specs, or generating server stubs, but these are minor gaps for a client-side API toolkit.