Oapi Invoker MCP Server

`oapi-invoker-mcp` invokes any OpenAPI through Model Context Protocol (MCP) server.

Local serverstdio

What is the Oapi Invoker MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Oapi Invoker MCP MCP server moves it into the conversation instead. oapi-invoker-mcp invokes any OpenAPI through Model Context Protocol (MCP) server.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: SPEC_URL, OAPI_INVOKER_DEBUG, GITHUB_TOKEN, SPEC_PATH, SPEC_FORMAT, SPEC_EXTENSION_PATH, SPEC_EXTENSION_FORMAT, ISSUE_TITLE. 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.

Things to watch

  • 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.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by mcpc-tech; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

How to install the Oapi Invoker MCP MCP server

### Using Deno directly

```json
{
  "mcpServers": {
    "capi-invoker": {
      "command": "deno",
      "args": ["run", "--allow-all", "jsr:@mcpc/oapi-invoker-mcp/bin"],
      "env": {
        "SPEC_URL": "https://api.github.com/openapi.json",
        "GITHUB_TOKEN": "your-github-token"
      },
      "transportType": "stdio"
    }
  }
}

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

Configuration

VariableDescriptionRequired
SPEC_URLEndpoint or connection string the server talks to.Yes
OAPI_INVOKER_DEBUGConfiguration value read at startup.Optional
GITHUB_TOKENCredential the server authenticates with.Yes
SPEC_PATHFilesystem location the server is allowed to use.Optional
SPEC_FORMATConfiguration value read at startup.Optional
SPEC_EXTENSION_PATHFilesystem location the server is allowed to use.Optional
SPEC_EXTENSION_FORMATConfiguration value read at startup.Optional
ISSUE_TITLEConfiguration value read at startup.Optional

Frequently asked questions

It connects Oapi Invoker MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Oapi Invoker MCP directly.