JSPM

relay-mcp

1.2.0
    • ESM via JSPM
    • ES Module Entrypoint
    • Export Map
    • Keywords
    • License
    • Repository URL
    • TypeScript Types
    • README
    • Created
    • Published
    • Downloads 10
    • Score
      100M100P100Q67485F
    • License MIT

    Universal OpenAPI to MCP relay server with enterprise authentication

    Package Exports

    • relay-mcp
    • relay-mcp/dist/index.js

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (relay-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    Relay

    Universal OpenAPI ➜ MCP relay server with enterprise authentication.

    npm version npm downloads

    What is Relay?

    Relay converts any OpenAPI/Swagger specification into AI-callable MCP tools. It acts as a bridge between AI assistants and REST APIs, automatically generating tools from API documentation and executing real HTTP requests.

    Main Function: Transform any REST API into MCP tools that AI assistants can use directly.

    Installation

    npm install relay-mcp

    Basic Usage

    1. Install and build:
    npm install
    npm run build
    1. Configure (create .env file):
    SWAGGER_SOURCE=url
    SWAGGER_URL=https://petstore.swagger.io/v2/swagger.json
    AUTH_TYPE=none
    1. Run the server:
    npm start
    1. Add to MCP client (e.g., Claude Desktop for stdio):
    {
      "mcpServers": {
        "relay": {
          "command": "node",
          "args": ["/path/to/relay/dist/index.js"],
          "env": {
            "SWAGGER_SOURCE": "url",
            "SWAGGER_URL": "https://petstore.swagger.io/v2/swagger.json",
            "AUTH_TYPE": "none",
            "TRANSPORT": "stdio"
          }
        }
      }
    }

    Or run as a standalone server with SSE/HTTP:

    # For SSE transport
    TRANSPORT=sse TRANSPORT_PORT=3000 npm start
    
    # For HTTP transport
    TRANSPORT=http TRANSPORT_PORT=3000 npm start

    Then configure your MCP client to connect to http://localhost:3000/mcp.

    Features

    • Dynamic tool generation from any OpenAPI/Swagger spec
    • Real HTTP execution with interceptors and structured logging
    • Auth: API Key (header/query), Bearer, Basic
    • OpenAPI 2.0 and 3.x support
    • Multiple transport modes: stdio, SSE (Server-Sent Events), HTTP

    Documentation

    License

    MIT