"Google Docs" matching MCP servers:

Enables interaction with Google Ads through the Google Ads API using GCloud authentication. Supports GAQL query execution, performance data retrieval, account management, and resource discovery with pagination and multiple output formats.

An MCP server that enables management of Google Play games via the Google Games Management API, allowing automated interactions for game resets, hiding/unhiding data, and player management through natural language commands.

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.

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.

Provides Plaid developers with sandbox integration tools for creating test items, reading financial data, simulating webhooks and login failures, plus docs-quality tools for API search and OpenAPI-vs-Postman-vs-docs drift checking.

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.

Enables turning any docs URL (OpenAPI, llms.txt, or HTML) into lean, callable MCP tools with add/list/call operations, plus timeout and truncation guards.

Enables LLMs to dereference and query OpenAPI/Swagger specifications, search endpoints and schemas, validate payloads, extract security schemes, and generate production-ready integration code in multiple languages.

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

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

A lightweight MCP server for searching SmugMug documentation and calling the live SmugMug API.

Enables searching and reading published Hoppscotch API documentation, inspecting endpoint details, and retrieving saved response examples through MCP tools.

Generates API documentation in Confluence from Swagger/OpenAPI specs or NestJS controller files, including automatic Postman collection generation.

A local stdio server that lets coding agents build and verify a merchant payment integration against a sandbox, creating and cancelling invoices, simulating payment outcomes, checking invoice status, and validating webhook signatures. It also serves embedded docs as resources and refuses live or payout keys, keeping all work out of production paths.

Enables coding agents to discover, write, and test integrations for LinkedIn (Classic, Sales Navigator, Recruiter), WhatsApp, Instagram, Telegram, Gmail/Outlook/IMAP email, and Google/Outlook calendar by reading the live API contract and executing real calls on connected accounts.

An MCP server for API discovery and execution with a token-efficient search -> execute workflow over OpenAPI, Google Discovery, and optional native GraphQL and gRPC sources.

Exposes Docusaurus documentation and OpenAPI specs as an MCP server, enabling AI agents to search docs and inspect API endpoints.

Enables coding agents to check requests against a live OpenAPI 3.x specification rather than guessing, by resolving endpoints from a docs anchor, operationId, path fragment or tag, revealing what each operation accepts and returns with $refs resolved, and diffing a concrete payload to report missing, unknown, mistyped, or forbidden fields with suggested corrections. All five tools are strictly read-only, never touching the API the schema describes, and return actionable errors with close-match suggestions.

An MCP server that crawls API documentation websites and exposes their content to AI models, enabling them to search, browse, and reference API specifications.

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.