Api To MCP Server

Generates MCP tool code from OpenAPI specs

Local serverstdioTypeScript

What is the Api To MCP MCP server?

If you already use Api To MCP, the api to mcp mcp server is the piece that lets your assistant work with it directly. Generates MCP tool code from OpenAPI specs.

What the server does

A tool that creates MCP (Model Context Protocol) servers from OpenAPI/Swagger specifications, enabling AI assistants to interact with your APIs. Create your own branded and customized MCPs for specific APIs or services.

This project creates a dynamic MCP server that transforms OpenAPI specifications into MCP tools. It enables seamless integration of REST APIs with AI assistants via the Model Context Protocol, turning any API into an AI-accessible tool.

  • Dynamic loading of OpenAPI specs from file or HTTP/HTTPS URLs
  • Support for OpenAPI Overlays loaded from files or HTTP/HTTPS URLs
  • Customizable mapping of OpenAPI operations to MCP tools
  • Advanced filtering of operations using glob patterns for both operationId and URL paths
  • Comprehensive parameter handling with format preservation and location metadata
  • API authentication handling

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Installation — The Installation tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: GOOGLE_API_KEY, YOUR_API_KEY, OPENAPI_SPEC_PATH, TARGET_API_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as your-custom-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Api To MCP's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by TykTechnologies; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Api To MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.

How to install the Api To MCP MCP server

{
  "mcpServers": {
    "api-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@tyk-technologies/api-to-mcp@latest",
        "--spec",
        "https://petstore3.swagger.io/api/v3/openapi.json"
      ],
      "enabled": true
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GOOGLE_API_KEYCredential the server authenticates with.Yes
YOUR_API_KEYCredential the server authenticates with.Yes
OPENAPI_SPEC_PATHFilesystem location the server is allowed to use.Optional
TARGET_API_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Api To MCP to Installation.

Frequently asked questions

It connects Api To MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Installation) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Api To MCP directly.