ANY API

Exposes APIs via OpenAPI v3 by generating MCP tools from endpoints for AI interactions.

typescript

GitHub Stars

typescript

Language

3 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "ryddle-any-api-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/any-api-mcp/build/index.js"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY",
        "API_URL": "https://api.example.com",
        "AUTH_TYPE": "bearer-endpoint",
        "API_SECRET": "YOUR_API_SECRET",
        "CONFIG_PATH": "/path/to/config.json",
        "SERVER_NAME": "my-api-mcp",
        "OPENAPI_SPEC_PATH": "./open-api.yaml"
      }
    }
  }
}

ANY API MCP Server dynamically exposes any API that provides an OpenAPI v3 specification as MCP tools. By parsing the spec, it turns API endpoints into usable tools for your AI assistants, enabling you to interact with diverse APIs through a consistent MCP interface.

How to use

You connect an MCP client to the local MCP server you run, and the server automatically generates tools from your API’s OpenAPI spec. Each operation in the spec becomes a corresponding MCP tool that your AI can invoke. You can use various authentication methods to access protected APIs, and you can point the server at either a config file or environment variables for setup. Start the server with the provided runtime command, then configure your MCP client to reference the local server.

How to install

Prerequisites you need before installation: Node.js v16 or higher, and network access to the API you want to expose.

Install dependencies and build the project locally with these steps:

npm install
npm run build

Configuration and usage notes

Configure the server either with a JSON configuration file or through environment variables.

Configuration file (recommended) example shows core options you can customize, including the API URL, path to the OpenAPI spec, and authentication settings.

Environment variables offer an alternative setup, mirroring the same configuration knobs.

Starting and connecting from an MCP client

Run the server locally using the standard runtime command shown in examples. The server is intended to run as a local process and be referenced by your MCP client configuration.

node /absolute/path/to/any-api-mcp/build/index.js

Built by

VeilStrat

AI signals for GTM teams