Discover Awesome MCP Servers

Feishu MCP Server

A remote Model Context Protocol server for Feishu (Lark) that supports OAuth authentication and deployment on Cloudflare Workers. It allows AI clients to interact with Feishu documents, perform content searches, and manage document blocks with a zero-configuration experience.

Obsidian MCP Server Plugin

Turns an Obsidian vault into a local Model Context Protocol server that allows AI tools to directly read, search, and write to your notes. It features folder-level access control and a built-in dashboard for easy integration with tools like Claude Desktop and Cursor.

mcp_slack

fetch the latest channels messages chat

Store Screenshot Generator MCP

Generates beautiful App Store and Play Store screenshots by inserting app images into iPhone/iPad mockup frames with customizable text overlays and gradient backgrounds. Supports multiple device types and batch generation with both free and pro subscription tiers.

MCP Declarative Server

A utility module for creating Model Context Protocol servers declaratively, allowing developers to easily define tools, prompts, and resources with a simplified syntax.

Trapper Keeper MCP

An MCP server that automatically manages and organizes project documentation using the document reference pattern, keeping CLAUDE.md files clean and under 500 lines while maintaining full context for AI assistants.

WHOOP MCP Server

Connects WHOOP fitness data to Claude Desktop, enabling natural language queries about workouts, recovery, sleep patterns, and physiological cycles with secure OAuth authentication and local data storage.

Zaifer-MCP

Enables LLM assistants like Claude to interact with Zaif cryptocurrency exchange through natural language, supporting market information retrieval, chart data, trading, and account management for BTC/JPY, ETH/JPY, and XYM/JPY pairs.

Hubble MCP Server

A Python-based Model Context Protocol server that integrates with Claude Desktop, allowing users to connect to Hubble API services by configuring the server with their Hubble API key.

arXiv MCP Server

Enables interaction with arXiv.org to search scholarly articles, retrieve metadata, download PDFs, and load article content directly into LLM context for analysis.

Jina AI Remote MCP Server

Provides access to Jina AI's suite of tools including web search, URL reading, image search, embeddings, and reranking capabilities. Enables users to extract web content as markdown, search academic papers, capture screenshots, and perform semantic operations through natural language.

Mendix Context Bridge

Enables AI agents to read and understand local Mendix project structure and logic by connecting directly to the .mpr file via MCP. Allows querying microflows, entities, attributes, and modules in read-only mode without requiring cloud access.

Artsy Analytics MCP Server

A Model Context Protocol server that provides Artsy partner analytics tools for Claude Desktop, allowing users to query gallery metrics, sales data, audience insights, and content performance through natural language.

Apple MCP Server

Enables interaction with Apple apps like Messages, Notes, and Contacts through the MCP protocol to send messages, search, and open app content using natural language.

MCP Link - Convert Any OpenAPI V3 API to MCP Server

Okay, I can help you understand how to convert an OpenAPI V3 API definition to an MCP (presumably referring to a **Microservice Control Plane**) server. However, the process isn't a direct, one-step conversion. It involves several steps and considerations. Here's a breakdown of the general approach and key concepts: **Understanding the Goal** * **OpenAPI V3:** This describes your API's structure, endpoints, data models, authentication, etc. It's a *specification*. * **MCP (Microservice Control Plane):** This is an infrastructure layer that manages and orchestrates your microservices. It typically handles things like: * Service discovery * Traffic management (routing, load balancing) * Security (authentication, authorization) * Observability (metrics, logging, tracing) * Deployment and scaling The goal is to use the OpenAPI definition to *configure* your MCP to properly handle requests to your API. You're not "converting" the OpenAPI file into an MCP server itself. You're using it as a blueprint to tell the MCP how to manage your API. **General Steps** 1. **Choose an MCP:** The first step is to select a Microservice Control Plane. Popular options include: * **Istio:** A very popular and powerful open-source service mesh. * **Linkerd:** Another open-source service mesh, known for its simplicity. * **Kong:** An API gateway and service mesh. * **Envoy:** A high-performance proxy often used as a building block for service meshes. * **Commercial Solutions:** Many cloud providers (AWS, Azure, GCP) offer managed service mesh or API gateway solutions. The choice depends on your requirements (scale, complexity, existing infrastructure, budget, etc.). 2. **Deploy Your API (Microservice):** You need to have your actual API implementation running as a microservice. This is the code that handles the requests defined in your OpenAPI specification. This microservice needs to be deployed in an environment that the MCP can manage (e.g., Kubernetes). 3. **Configure the MCP using the OpenAPI Definition:** This is the core of the process. You'll use the OpenAPI definition to configure the MCP to: * **Route traffic:** Tell the MCP how to route incoming requests to the correct microservice based on the URL path, HTTP method, and other criteria defined in the OpenAPI spec. * **Apply security policies:** Configure authentication and authorization based on the security schemes defined in the OpenAPI spec (e.g., API keys, OAuth 2.0, JWT). * **Implement rate limiting:** Set limits on the number of requests allowed per client or API endpoint. * **Transform requests/responses (if needed):** The MCP can sometimes be used to transform requests or responses to match the expected format. * **Enable observability:** Configure the MCP to collect metrics, logs, and traces for your API. 4. **Specific MCP Configuration Methods:** The exact way you configure the MCP depends on the chosen MCP. Here are some common approaches: * **Istio:** * **Virtual Services:** Define how traffic is routed to your microservices. You can use the OpenAPI spec to help define the routing rules. * **Gateway:** Configures the entry point for external traffic into your service mesh. * **AuthorizationPolicy:** Defines access control rules. * **RequestAuthentication:** Configures how to authenticate requests. * **Istio API Definitions:** Istio has its own API definitions (CRDs - Custom Resource Definitions) that you use to configure its behavior. You'll need to translate the information from your OpenAPI spec into these Istio API definitions. * **Kong:** * **Plugins:** Kong uses plugins to add functionality like authentication, rate limiting, and request transformation. You can configure these plugins using the Kong Admin API or declarative configuration files. The OpenAPI spec can guide you in configuring these plugins. * **Services and Routes:** Define the upstream services and the routes that map to them. * **Other MCPs:** Each MCP will have its own configuration mechanisms. Consult the documentation for your chosen MCP. **Example (Conceptual - Istio)** Let's say your OpenAPI spec defines an endpoint: ```yaml paths: /users/{userId}: get: summary: Get a user by ID parameters: - name: userId in: path required: true schema: type: integer responses: '200': description: Successful operation content: application/json: schema: type: object properties: id: type: integer name: type: string ``` In Istio, you might create a `VirtualService` like this (simplified): ```yaml apiVersion: networking.istio.io/v1alpha3 kind: VirtualService metadata: name: user-service spec: hosts: - "user-service.example.com" # Or the hostname of your service gateways: - my-gateway http: - match: - uri: prefix: /users/ route: - destination: host: user-service # The Kubernetes service name of your microservice port: number: 8080 # The port your microservice is listening on ``` This `VirtualService` tells Istio to route any requests to `/users/*` to the `user-service` microservice. You would then configure other Istio resources (e.g., `AuthorizationPolicy`) to handle authentication and authorization for this endpoint, based on the security schemes defined in your OpenAPI spec. **Tools and Automation** * **OpenAPI to MCP Configuration Generators:** Some tools can help automate the process of generating MCP configuration from OpenAPI definitions. These tools are often specific to a particular MCP. Search for tools like "OpenAPI to Istio configuration generator" or "OpenAPI to Kong configuration generator." * **Scripting:** You can write scripts (e.g., using Python and the Istio or Kong API) to programmatically generate the MCP configuration based on your OpenAPI spec. * **Configuration Management Tools:** Tools like Terraform or Ansible can be used to manage the deployment and configuration of your MCP. **Important Considerations** * **Complexity:** Configuring an MCP can be complex, especially for large and complex APIs. * **Security:** Pay close attention to security when configuring your MCP. Make sure you properly authenticate and authorize requests. * **Testing:** Thoroughly test your API after configuring the MCP to ensure that everything is working as expected. * **Evolution:** As your API evolves, you'll need to update your OpenAPI definition and reconfigure your MCP. **In summary, there's no single "convert" button. You need to:** 1. **Choose an MCP.** 2. **Deploy your API as a microservice.** 3. **Use your OpenAPI definition as a blueprint to configure the MCP to manage traffic, security, and observability for your API.** 4. **Use tools and scripting to automate the configuration process where possible.** To give you more specific guidance, please tell me: * **Which MCP are you using (or considering)?** * **What is your deployment environment (e.g., Kubernetes, AWS, Azure)?** * **What are your key requirements (e.g., security, rate limiting, observability)?** Then I can provide more tailored advice.

Amap MCP Server

Provides comprehensive geographic information services and route planning for AI agents via the Amap (Gaode Maps) API. It supports geocoding, multi-modal navigation, POI searches, and administrative region queries.

Weather MCP Server

Provides weather information for cities through a protected MCP interface with Nevermined payment integration. Demonstrates both high-level and low-level MCP server implementations with paywall protection for tools, resources, and prompts.

Serverless VPC Access MCP Server

An auto-generated MCP server for Google's Serverless VPC Access API, enabling communication with Google Cloud VPC networks through natural language interactions.

Microsoft Planner MCP

Enables interaction with Microsoft Planner tasks through natural language using Azure CLI authentication. Supports listing plans, creating/updating/deleting tasks, managing buckets, and integrating GitHub links without complex OAuth setup.

TradingView MCP Server

Enables trading analysis across Forex, Stocks, and Crypto with 25+ technical indicators, real-time market data, and Pine Script v6 development tools including syntax validation, autocomplete, and version conversion.

PAELLADOC

A Model Context Protocol (MCP) server that implements AI-First Development framework principles, allowing LLMs to interact with context-first documentation tools and workflows for preserving knowledge and intent alongside code.

Document Organizer MCP Server

Enables systematic document organization with PDF-to-Markdown conversion, intelligent categorization, and automated workflow management. Supports project documentation standards and provides complete end-to-end document processing pipelines.

MCP Desktop Tools

An MCP server that provides Claude with comprehensive desktop automation capabilities including browser control, window management, and native mouse/keyboard input on Windows. It enables users to capture screenshots, launch applications, and interact with the system clipboard through natural language.

Bargainer MCP Server

A Model Context Protocol server that aggregates and compares deals from multiple sources including Slickdeals, RapidAPI marketplace, and web scraping, enabling users to search, filter, and compare deals through a chat interface.

Gemini Context MCP Server

鏡 (Kagami)

Real Estate MCP Server

Enables real estate property searches with location and criteria filtering, plus comprehensive mortgage calculations including monthly payments and affordability analysis. Currently uses mock data for property searches but provides full mortgage calculation functionality.

Micro.blog Books MCP Server

Enables management of Micro.blog book collections through natural language, allowing users to organize bookshelves, add/move books, and track reading goals. Built with FastMCP for reliable integration with Claude Desktop.

GitLab MCP Server

Connects AI assistants to GitLab, enabling natural language queries for merge requests, code reviews, pipeline tests, job logs, and commit discussions directly from chat.

Greenhouse MCP Server by CData

This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Greenhouse (beta): https://www.cdata.com/download/download.aspx?sku=PGZK-V&type=beta