Tyk API Management

Tyk API Management

Tool to convert OpenAPI specs into MCP servers for AI-enabled API access.

1
Stars
0
Forks
7
Releases

Overview

OpenAPI to MCP Server is a dynamic tool that converts OpenAPI/Swagger specifications into MCP servers, enabling AI assistants to interact with REST APIs. It loads API definitions from local files or remote URLs and supports OpenAPI overlays to modify or extend specs. OpenAPI operations can be mapped to MCP tools with customizable settings, and you can finely control exposure using advanced glob-based filtering on operationId and URL paths. Parameter handling preserves formats and includes location metadata to ensure accurate request construction. The server uses OpenAPI metadata (title, version, description) to configure itself and employs hierarchical description fallbacks (operation description → operation summary → path summary) for clearer tool descriptions. It supports custom HTTP headers via environment variables and CLI, and includes X-MCP headers for request tracking. Path-level x-mcp extensions allow overriding tool names and descriptions. Configuration is flexible: you can specify options via CLI, environment variables, or a JSON configuration file, and the project provides guidance for forking, customizing, and publishing branded MCP servers. The project also enables API lifecycle operations such as token and user management and analytics via MCP tooling.

Details

Owner
TykTechnologies
Language
TypeScript
License
MIT License
Updated
2025-12-07

Features

Dynamic loading of OpenAPI specs

Load OpenAPI specs from local files or remote HTTP/HTTPS URLs to generate MCP servers on the fly.

OpenAPI Overlays support

Apply overlays to OpenAPI specs via local files or URLs to modify endpoints and attributes before generating tools.

Customizable operation-to-tool mapping

Configure how each OpenAPI operation becomes an MCP tool, enabling custom naming and behavior.

Advanced operation filtering

Filter exposed operations with glob patterns for operationId and URL paths to control exposure.

Comprehensive parameter handling

Preserve parameter formats and capture location metadata to ensure correct parameter extraction and transmission.

API authentication handling

Support API authentication and security schemes to secure connected endpoints.

OpenAPI metadata-driven configuration

Use OpenAPI metadata (title, version, description) to configure MCP server and tool descriptions.

Hierarchical description fallbacks

Fallback from operation description to summary to path summary for robust tool descriptions.

Audience

AI developersCreate MCP servers from OpenAPI specs to enable AI assistants to access APIs.
Claude Desktop usersConfigure and run MCP servers within Claude Desktop to access API tools.
Cursor usersRun MCP servers in Cursor during development to expose API tools.
Vercel SDK integratorsIntegrate MCP tools into JS/TS apps via Vercel AI SDK.
Platform teamsManage tokens, users, analytics and API lifecycles for organizational APIs.

Tags

OpenAPIMCPAIRESTdynamic-loadingoverlaysauthenticationheadersCLIenvironment-variables