Konfig MCP Engine
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 |
|---|---|
| konfig_transform_openapiB | Transforms an OpenAPI 3.0/3.1 specification JSON object into ready-to-call MCP Tool schemas for AI agents. |
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
There is only one tool, so there is no possibility of confusion or misselection. Its purpose is stated precisely: transform an OpenAPI spec into MCP tool schemas.
The single tool uses a clear snake_case verb_noun pattern with a namespace prefix (konfig_transform_openapi). Consistency cannot really be violated with one tool, but the naming is readable and predictable.
A single tool is thin for something branded as an 'Engine'; it covers only the transform step of what could be a larger workflow. Still, the narrow stated purpose makes one tool defensible, so it sits at borderline rather than clearly wrong.
The surface covers transformation but offers no validation, listing, batch processing, or reverse conversion, leaving agents to handle errors and preprocessing themselves. It is usable for its core task but has notable gaps around it.