OpenAPI Client Generator 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_clientB | Generate TypeScript API client from OpenAPI specification |
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 1 tool
With only one tool, there is no possibility of confusion. The tool has a clear and singular purpose.
The single tool uses a clear verb_noun pattern ('generate_client'), which is consistent and descriptive.
A single tool feels thin for an OpenAPI client generator. While it may suffice for a minimal use case, most users would expect additional capabilities like validation or endpoint listing.
The tool only generates a client from a specification. Obvious gaps include validating the spec, listing endpoints, or configuring output options, which limits its usefulness.