The server is published free on npm as apidog-mcp-server. It reads your Apidog project (a freemium product), a published Apidog docs site, or any OpenAPI/Swagger file; the OpenAPI-file mode needs no Apidog account at all.

Does it support remote/OAuth?

No. It runs locally over stdio via npx -y apidog-mcp-server@latest. For Apidog projects it authenticates with an APIDOG_ACCESS_TOKEN; the public-docs and OpenAPI-file modes need no token.

Does it read live API data or just the spec?

Just the specification. It exposes your OpenAPI/Swagger definition (endpoints, schemas, and $ref resources) so an agent can write correct code; it does not call your live API or modify data.

Apidog MCP server

OfficialApidogConfig last verified Jun 1, 2026

Apidog's official MCP server makes your API specifications a data source for AI IDEs so generated code matches the contract.

Apidog MCP Server is Apidog's official Model Context Protocol server. It exposes your API specification to an AI coding assistant as a queryable data source, so the model generates client code, DTOs, and documentation that match the real contract instead of hallucinating fields. On first use it reads and caches the spec locally; the agent then reads endpoints, request and response schemas, and reference resources on demand, and can re-pull the latest version when the spec changes.

The server runs locally over stdio via npx and supports three sources. It can read an Apidog project directly (authenticated with an APIDOG_ACCESS_TOKEN and a project id), a published Apidog API documentation site, or any standard OpenAPI/Swagger file by local path or URL through the --oas flag. An --apidog-api-base-url flag points it at on-premise Apidog deployments. The tool surface is intentionally small and reliable for a model to drive: read the project's OpenAPI spec, read the files referenced by $ref within it, and refresh the cached spec from the server. Alongside Postman and Bruno, it is a clean way to keep an agent grounded in the API it is building against.

Quick install

Copy-paste configs are provided for all 8 supported clients. Pick your client below.

Add to ~/.claude.json

~/.claude.json

json

{
  "mcpServers": {
    "apidog": {
      "command": "npx",
      "args": [
        "-y",
        "apidog-mcp-server@latest",
        "--project-id=<project-id>"
      ],
      "env": {
        "APIDOG_ACCESS_TOKEN": "<APIDOG_ACCESS_TOKEN>"
      }
    }
  }
}

Or via CLI

bash

claude mcp add apidog -- npx -y apidog-mcp-server@latest --project-id=<project-id>

Step-by-step guides

Available tools

Tool	Description
read_project_oas	Reads the content of the project's OpenAPI Spec file.
read_project_oas_ref_resources	Reads the contents of files referenced by $ref in the project's OpenAPI Spec. Multiple files can be retrieved at once.
refresh_project_oas	Re-downloads the latest OpenAPI Spec file content from the server.

Required configuration

APIDOG_ACCESS_TOKENRequired
Apidog personal access token used to read an Apidog project. Not needed for the public docs or OpenAPI-file modes.

What you can do with it

Generate code that matches your API contract

Before writing a client or DTO, the agent reads the project's OpenAPI spec with read_project_oas so it uses the exact endpoints, fields, and types you defined instead of inventing them.

Keep generated code in sync with spec changes

When the API design changes in Apidog, the agent calls refresh_project_oas to pull the latest spec and then updates the affected models and documentation.

FAQ

Is it free?: The server is published free on npm as apidog-mcp-server. It reads your Apidog project (a freemium product), a published Apidog docs site, or any OpenAPI/Swagger file; the OpenAPI-file mode needs no Apidog account at all.
Does it support remote/OAuth?: No. It runs locally over stdio via npx -y apidog-mcp-server@latest. For Apidog projects it authenticates with an APIDOG_ACCESS_TOKEN; the public-docs and OpenAPI-file modes need no token.
Does it read live API data or just the spec?: Just the specification. It exposes your OpenAPI/Swagger definition (endpoints, schemas, and $ref resources) so an agent can write correct code; it does not call your live API or modify data.

← Browse all api-tools servers