Api Docs MCP Server

MCP server for API and GraphQL documentation and search. That is what the api docs mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Model Context Protocol (MCP) server that provides tools for interacting with API documentation. Supports GraphQL, OpenAPI/Swagger, and gRPC specifications, fetching schema definitions from various sources (local files or remote URLs), caching them, and exposing them through a set of tools.

• Dynamic Tool Registration — Automatically discovers and registers tools from a specified directory
• API Documentation Retrieval — Provides tools to list available API methods (api_docs) and retrieve detailed documentation for specific methods (api_search)
• Schema Caching — Caches API schema information to reduce redundant fetches and improve performance
• Multiple Source Support —
• GraphQL — Supports loading GraphQL schemas from graphql / gql files or json introspection results (local files or remote URLs)
• OpenAPI/Swagger — Supports loading OpenAPI/Swagger yaml / yml / json schemas from local files or remote URLs

What it needs from you

Configuration is passed through the environment: API_SOURCES, YOUR_GITHUB_TOKEN. 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.

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.

How it compares

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by elifuzz; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

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.