"Spec-WorkFlow documentation or implementation" matching MCP servers:

Turns any OpenAPI/Swagger spec into queryable tools for LLMs, enabling endpoint search, detail retrieval, and schema exploration.

Enables generating markdown API documentation from OpenAPI JSON or route definitions, with a health-check tool.

Audits any MCP server against the official spec, providing HMAC-signed conformity reports.

A Model Context Protocol server that fetches detailed API documentation from a local platform using a document ID. It enables language models to retrieve specific endpoint specifications to assist with tasks like code generation and API integration.

Provides access to comprehensive Riot Games API documentation for League of Legends, Teamfight Tactics, Valorant, and Legends of Runeterra, including endpoint details, parameters, and response formats.

A fully automated system that analyzes Django REST Framework ViewSets to generate accurate OpenAPI 3.0 specification documentation without manual configuration.

Enables AI assistants to query API documentation from Eolink Apikit instances via the Eolink Open API, supporting listing projects, groups, searching APIs by keyword/path, and retrieving detailed API definitions.

Enables AI agents to connect to any GraphQL endpoint, introspect schemas, and execute queries or mutations through auto-generated tools.

Validates OpenAPI specs from files, inline content, or URLs, and generates prompts for agent developers based on the API analysis.

Provides comprehensive documentation for 377 Fortnox API endpoints and 81 resource categories directly from the official OpenAPI specification. It enables users to search, browse, and explore technical endpoint details and data schemas within AI assistants without requiring authentication.

MCP server for reading, writing, and organizing API documentation in Apidog.

A read-only MCP server that exposes Automeli's public API documentation (v2 canonical, v1 frozen) to LLMs via fetch and cache over www.automeli.com artifacts. It enables listing, searching, and retrieving endpoints, OpenAPI specs, error explanations, code snippets, and end-to-end flow guides.

Enables AI agents to create, run, and manage HTTP requests using the Invoker API client's .ivk format. It provides tools for scanning collections, executing requests, managing environments, and building documentation sites.

MCP server for Mockzilla. Lets coding agents like Claude Code, Claude Desktop, Cursor and Gemini CLI install the Mockzilla CLI and run API mocks from an OpenAPI spec or a single endpoint. Log in from the agent to deploy hosted mocks on mockzilla.org

Enables AI agents to discover and read Typeship API documentation and execute API operations through schema-validated MCP tools, with optional read-only mode and configurable result limits.

Provides AI-enabled access to Amazon Business API documentation, sample code, and troubleshooting resources. Enables developers to search and retrieve API documentation, generate integration code, and get guided solutions for common errors during the API integration process.

CLIRank - API discovery for AI agents. APIs scored on CLI relevance: auth method, JSON responses, headless operation, pricing transparency. Search by capability, compare alternatives, read agent-contributed docs. 6 MCP tools for discovery, comparison, and documentation. Agents contribute observations back - crowdsourced API docs by machines, for machines.

A Model Context Protocol (MCP) server for authenticated REST APIs. Drop it into any project, point it at your API, and let AI agents call endpoints — with auto-login, 2FA support, Swagger spec fetch, and fuzzy endpoint search — all without writing a single line of auth code.

Point Claude at any API. JitAPI figures out which endpoints to call and in what order — automatically. Register any OpenAPI spec, search endpoints in plain English, and orchestrate multi-step workflows across multiple APIs. No API keys required — works out of the box with local embeddings.

Enables local analysis of OpenAPI 3 and Swagger 2 JSON/YAML spec files on disk, with no remote fetching of specs or credentials. It groups endpoints by tag, flags operations that appear to lack security, lists deprecated operations, and produces short markdown cheat sheets for agents.