The value is in the controls rather than the conversion: filtering decides which endpoints a model even sees, redaction rules keep secrets out of the transcript, and response limits stop one call filling the context.
A generic OpenAPI-to-MCP bridge. It parses a specification and exposes the operations you select as tools, with custom extensions controlling which operations appear, what they are called, and how requests are signed.
- Operations filtered by path pattern, HTTP method, operation id or tag, so a large spec becomes the handful of tools you meant
- Tool names generated from a pattern you choose, with prefixes and suffixes, rather than whatever the spec called them
- Specification patches applied on top of the original — descriptions and examples added without editing the vendor's file
- Custom authentication protocols including Tencent Cloud API Signature V3, and script-generated values for headers, parameters and auth
- Sensitive parameters and response fields marked for automatic redaction, and response length and keys limited so a large payload does not flood the context
- A debug mode for when a call is not going out the way you expect
An OpenAPI specification for the service you want to call, and whatever credentials that service needs — this carries them, it does not issue them. Base URL, default headers, proxy, timeout and retry all sit in the request configuration.
Build from source — clone the repository and build it, then point your client at the binary