generate_curl
Generate a ready-to-use cURL command for an API endpoint. Includes sample request body, auth headers, and path/query parameters. Copy-paste to terminal or import into Postman.
LABSCO SUMMARY
Schemas come back dereferenced, so a chain of $ref pointers is resolved before the model ever sees it.
That is the difference between a spec a model can answer questions from and one it has to chase through by hand. What it generates is built to be used rather than read: the cURL command arrives with a sample body, auth headers and parameters in place, and the TypeScript generation works from either a named component schema or an endpoint's request and response pair. One ordering rule governs the whole surface — load_spec first, and every other tool operates on whatever it loaded.
What it is
An OpenAPI specification client: one spec loaded from a URL or a file, then browsed, queried, validated against, and turned into code.
What you get
- load_spec from a URL or a local filePath, which has to run before anything else.
- list_endpoints filtered by method, tag and deprecation, and search_endpoints by keyword across path, summary, description and operationId.
- get_endpoint_details with the endpoint's parameters, request body, responses and security.
- Schemas resolved rather than referenced: get_request_schema returns the fully dereferenced request body, and get_response_schema returns the schema for a given status code.
- validate_payload, which checks a JSON payload against an endpoint's request schema, and generate_sample, which builds one from that schema with optional fields included or left out.
- get_auth_schemes for the authentication schemes and their per-endpoint requirements, and get_servers for the servers and their variables.
- generate_typescript_types from a named component schema or from an endpoint's request and response, and generate_curl, which produces a command with a sample body, auth headers and path and query parameters already filled in.
Requirements
An OpenAPI specification reachable by URL or by local path, loaded through load_spec before any other tool will answer. Nothing else — no account, no key.
Setup effort
One command — npx --yes @blackkspydo/openapi-mcp
USE CASES
01
Getting oriented in an API you have never touched
The spec is loaded once and then queried: endpoints listed by method, tag or deprecation, searched across path, summary, description and operationId, and one of them opened with its parameters, responses and security.
02
Building a request body that will actually validate
The request schema comes back fully dereferenced, a sample can be generated from it with or without optional fields, and the payload you assembled is checked against the schema before it is ever sent.
03
Working out what a response will actually contain
Response schemas are addressed per status code, so the success shape and the error shape are separate answers rather than one union you have to untangle.
04
Trying an endpoint from the terminal
The server list supplies the base URL and its variables, the auth schemes say what the endpoint requires, and the generated cURL arrives with a sample body, headers and parameters already in place.
05
Typing a client against the specification
Types come either from a named component schema or from an endpoint's request and response pair, generated off the same dereferenced schemas the validation uses, so the types and the checks agree.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
generate_sample
Generate a sample request payload for an endpoint based on its schema.
generate_typescript_types
Generate TypeScript interfaces/types from OpenAPI schemas. Use schemaName to generate from a component schema (e.g., 'Pet'), or use path+method to generate request/response types for an endpoint.
get_auth_schemes
Get authentication schemes defined in the OpenAPI spec and their requirements per endpoint.
get_endpoint_details
Get detailed information about a specific endpoint including parameters, request body, responses, and security.
get_request_schema
Get the fully dereferenced request body schema for an endpoint.
get_response_schema
Get the response schema for an endpoint by status code.
get_servers
Get available API servers and their variables from the OpenAPI spec.
list_endpoints
List all API endpoints from the loaded OpenAPI spec with optional filtering.
load_spec
Load an OpenAPI specification from a URL or local file. This must be called before using other tools.
search_endpoints
Search for endpoints by keyword across path, summary, description, and operationId.
validate_payload
Validate a JSON payload against the request schema for an endpoint.
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"openapi-mcp": {
"command": "npx",
"args": [
"--yes",
"@blackkspydo/openapi-mcp"
]
}
}
}npx
TERMINAL
npx --yes @blackkspydo/openapi-mcp
