"Scraping Langchain and Langgraph documentation" matching MCP servers:

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

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.

Implements a secure MCP server with API Key and JWT authentication, providing tools like echo, login, secure_action, and admin_action. Includes MCP Inspector integration for testing and debugging.

Enables precise measurement of live HTTP and WebSocket services while maintaining an append-only, evidence-based ledger of claims that agents can query with explicit timestamps, staleness indicators, and instructions for re-verification.

This server facilitates scalable discovery and execution of OpenAPI endpoints using semantic search and high-performance processing, overcoming limitations of large spec handling for streamlined API interactions.

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.

MCP server for scraping with declarative configs

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.

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.

MCP server that provides 22 tools to manage Apidog API documentation, including importing OpenAPI specs, exporting, diffing, analyzing, and bulk-editing endpoints.

Enables AI assistants to automatically manage Apifox API documentation by importing OpenAPI/Swagger specifications and exporting existing API structures. Supports batch operations, intelligent deprecation marking, and smart scope detection for partial module imports.

Precisely filter and fetch API documentation from Apifox or any OpenAPI URL, reducing context bloat by fetching only needed endpoints.

Enables AI assistants to search, browse, and generate example payloads from Sage Intacct REST API documentation using OpenAPI specs.