"Searching for local information or documents" matching MCP servers:

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

Enables AI assistants to interact with the Post For Me API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

MCP server for Akamai APIs. 198 tools covering Property Manager, Edge DNS, CPS, WAF, and reporting. Built with TypeScript, featuring modular architecture, comprehensive testing, and multi-account support. Make Akamai accessible to AI assistants.

This local stdio MCP server enables AI clients to search, read, and safely write Omeka S REST API resources such as items, media, item sets, site pages and blocks, with value annotations and read-back verification of writes.

Free x402 endpoint checker plus paid report and metadata tools. Remote MCP server for agents. Written by AI named Nock, not a human.

This server enables interacting with the National Digital Health Mission's Health Information User (HIU) API, allowing agents to access and manage health information through the Multi-Agent Conversation Protocol.

Lets AI assistants safely explore a Matrix42 instance by discovering web services and the data model, running validated ASQL queries, searching the service desk, and previewing ticket actions — read-only by default and without exposing credentials.

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 Claude to create local, persistent mock REST APIs on demand from plain-language descriptions, with data written to disk so it survives restarts.

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

Parses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.

Turns an existing Express, Hono, Fastify, or Next.js API into a Streamable HTTP MCP endpoint, exposing one tool per OpenAPI operation that runs in-process through the app's existing routes, auth, validation, and handlers. It also serves discovery documents and readiness guidance so models can better understand and call the API.

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

Enables AI assistants to explore and interact with the Facets Control Plane API via natural language, supporting operations like searching endpoints, loading schemas, and making authenticated API calls.

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.

An MCP server for interacting with Treasure Data API, allowing users to retrieve database information and check server status through natural language queries.

Enables LLMs to send HTTP requests to a local development server, allowing interaction with APIs running on localhost.

Free JSON Schema validation, JSON to TypeScript, CSV to JSON, JSON repair and JSON to CSV for AI agents. Hosted MCP plus local STDIO. Connect once with a scoped key; enforce tool allowlists and quotas, inspect request IDs. Runnable repair → validate → CSV workflow. Bounded OpenAPI and webhook checks. No LLM calls or payments. Setup: invokeport.com/agents.

An MCP server that generates MCP servers. Give it an API definition - OpenAPI 3.0/3.1 or a Postman collection or extend an existing server - and it scaffolds a complete, runnable, ownable TypeScript or Python MCP server for that collection of APIs.

Enables coding agents to validate OpenAPI documents and JSON Schemas, validate data against a schema, and diff OpenAPI versions—including against a git ref—to classify breaking changes and suggest semver updates.

Enables coding agents to validate OpenAPI documents, detect breaking changes between API versions including against git refs, and validate JSON Schemas and data.

Exposes YApi's API management capabilities to MCP clients, enabling operations like listing projects, categories, searching APIs, and managing API details.

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.

API client for coding agents. Sends saved HTTP, GraphQL and gRPC requests, runs collections with their checks, and creates or edits requests over stdio or loopback HTTP, with secret values redacted and calls limited to an allowlist of hosts.

Replay-verified minimal JSON reproductions and deterministic TypeScript/OpenAPI drift checks. Local-first CLI and MCP server.

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.

Zero-telemetry local developer execution layer for AI coding agents. Provides deterministic tools to inspect listening network ports and processes, calculate IPv4 CIDR subnet ranges and usable hosts, decode embedded creation timestamps from distributed IDs (UUIDv7, ULID, Snowflake, MongoDB ObjectId), and convert Unix epoch timestamps to UTC, ISO 8601, and local time.

Enables searching, describing, and calling Procore REST API endpoints through a local MCP server, with read-only access by default and optional write operations when enabled.

Enables searching YApi interfaces by keyword and retrieving detailed interface schemas, including request/response, for project-level tokens.