"A guide for finding similarities in Obsidian note content" 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.

Goodday‑MCP is a lightweight Model Context Protocol (MCP) server designed to seamlessly integrate with the Goodday project management platform via its API v2. It enables querying of projects, tasks, and users—without altering any data—making it ideal for secure context-aware applications

A Node In Layers package that simplifies creation of MCP (Model-Control-Protocol) servers with tools for defining models, adding CRUD operations, and interacting with clients.

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

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.

Provides AI assistants with access to OpenAPI specifications, enabling API discovery, schema retrieval, and direct API execution with support for OAuth 2.0 and other authentication methods.

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.

Enables agents to interact with the Logflare API by writing JavaScript functions that run in a Vercel Sandbox, using three tools: search, execute_read, and execute_write.

Run the requests in a Postman collection folder and get structured, assertion-level results back straight from your AI assistant.

Provides a generic HTTP client tool allowing AI agents to make arbitrary HTTP requests from their environment, with support for environment-variable placeholders for secrets.

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

Enables testing how different MCP clients handle tool results containing both content and structuredContent, including outputSchema enforcement and mismatch scenarios.

ozon-mcp is a knowledge-rich MCP server that turns the entire Ozon seller toolkit into 15 high-leverage tools. AI agents (Claude, Cursor, Cline, Continue, Goose, Zed, …) can search the API in Russian or English, drill into any of 466 methods with a fully-resolved JSON Schema, and execute calls with built-in safety guards. Subscription- aware, automatic pagination over all 4 cursor styles, retry/ba

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

A read-only API change deploy gate for AI coding agents that analyzes OpenAPI specs to determine if changes are safe to deploy. It provides tools for comparing specs, explaining breaking changes, and generating migration guides.

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

A high-performance, multi-protocol API mock server with 18 built-in MCP tools for managing HTTP, GraphQL, gRPC, WebSocket, MQTT, SSE, and SOAP mocks, chaos engineering, stateful CRUD resources, and request verification.

A TypeScript-based MCP server that enables AI assistants to execute HTTP requests with full control over methods, headers, and body content. It facilitates seamless interaction with web APIs and endpoints through a versatile tool that handles automatic JSON formatting and response truncation.

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.