One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice

Tyk AI Studio can turn a single OpenAPI 3.x specification into a reusable Tool accessible through three interfaces: model-initiated calls in chat, authenticated REST requests, and an MCP server connection. Using Frankfurter’s exchange-rate API as an example, the tutorial explains that importable specifications need a complete servers URL, operation IDs for every endpoint, and plain ASCII text, while access also depends on correctly configured privacy levels. Tools must be granted separately to an App, which manages credentials, budgets, and permitted services, and to a chat room, which determines what the model can use; configuration must then be pushed to the gateway. Once configured, the same API definition and App credential support natural-language model requests, JSON-based calls through a gateway endpoint, and MCP clients that discover operations and parameters dynamically. The approach centralizes API descriptions, authentication, metering, and updates, though the tutorial notes a release-specific MCP port difference that users must adjust.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.