Discover Awesome MCP Servers

Remote MCP Server

A Cloudflare Workers-based MCP server that allows users to deploy and customize tools without authentication requirements, compatible with Cloudflare AI Playground and Claude Desktop.

Vercel MCP Relay Server

Enables AI assistants to interact with the Vercel REST API to manage projects, deployments, domains, environment variables, and teams through natural language commands.

Cloudflare Remote MCP Server

A template for deploying remote Model Context Protocol servers on Cloudflare Workers using Server-Sent Events (SSE). It enables the creation and hosting of custom AI tools that can be accessed via the Cloudflare AI Playground or local clients like Claude Desktop.

Diagrams MCP Server

Enables creation of infrastructure and architecture diagrams as code using the Python diagrams library, supporting 15+ cloud providers, 500+ node types, custom icons, and flowcharts with multiple output formats.

Overwatch2 MCP Server

An MCP server that provides Overwatch 2 hero data, allowing users to retrieve hero lists and detailed information about specific heroes.

Whoop MCP Server

Espejo de

TShark2MCP

An MCP server that enables AI-assisted network packet analysis using Wireshark's TShark tool. It provides tools for pcap file overview, session extraction, protocol filtering, and statistical analysis through a standardized interface.

Chess MCP Server

Enables AI assistants to play, analyze, and track chess games with full rule validation and support for standard algebraic notation. It provides tools for position evaluation and game state persistence during user sessions.

rekordbox-mcp

MCP server for rekordbox DJ database access. Provides read-only querying of tracks, playlists, and DJ session history from encrypted rekordbox SQLite databases using pyrekordbox.

Advertising-Analysis

A demonstration project of an MCP server for injecting advertisements into LLM responses, showcasing the risks of advertising injection middleware.

RateSpot MCP Server

Provides access to RateSpot.io mortgage rate APIs, enabling AI assistants to fetch real-time mortgage rates, compare loan products, calculate payments, and access comprehensive lending information.

mcp-book-search

Servidor MCP para la búsqueda de libros nacionales

Python Server MCP

Un servicio de precios de criptomonedas que proporciona información de precios de criptomonedas en tiempo real a través de un marco MCP (Protocolo de Contexto de Modelo) con integración de la API de CoinMarketCap.

WeatherAPI MCP Server

Proporciona datos actuales del clima y la calidad del aire para cualquier ciudad utilizando WeatherAPI, integrándose fácilmente con clientes MCP como n8n y la aplicación de escritorio Claude.

Web-QA

An AI-powered MCP server that automates web testing workflows by enabling recording, execution, and discovery of tests through natural language prompts.

CodeMerge

A Model Context Protocol server that uses Osmosis-Apply-1.7B to intelligently apply code edits while preserving the structure of the original code.

Gemini 2.5 Flash Image MCP

Enables conversational image generation and editing with Google's Gemini 2.5 Flash Image Preview. Supports text-to-image generation, natural language image editing, multi-image composition, and style transfer with optional file saving.

Linkup MCP Server

Provides real-time web search and webpage content fetching capabilities through Linkup's API, enabling AI assistants to access current information, news, and data from trusted sources across the web.

Gmail MCP

Enables AI assistants to interact with Gmail accounts via IMAP, allowing them to list, search, read, and send emails, manage labels and folders, and access attachments through the Model Context Protocol.

Selenium MCP Server

Enables AI assistants to automate web browser interactions through Selenium WebDriver. Supports multi-browser automation, element interaction, navigation, and web testing capabilities.

OpenFeature MCP Server

Provides OpenFeature SDK installation guidance through MCP tool calls. Enables AI clients to fetch installation prompts and setup instructions for various OpenFeature SDKs across different programming languages and frameworks.

RobotFrameworkLibrary-to-MCP

Okay, I can help you understand how to turn a Robot Framework library into an MCP (Message Center Protocol) server. It's a bit of a complex process, but here's a breakdown of the concepts and steps involved, along with considerations: **Understanding the Goal** First, let's clarify what we mean by "turning a Robot Framework library into an MCP server." Essentially, you want to expose the functionality of your Robot Framework library so that other applications (clients) can access and use it remotely via the MCP protocol. **Key Concepts** * **Robot Framework Library:** A collection of keywords (functions) that can be used in Robot Framework test cases. * **MCP (Message Center Protocol):** A communication protocol used for exchanging messages between applications. It's often used in embedded systems and other scenarios where a lightweight, reliable communication mechanism is needed. It defines how messages are formatted, sent, and received. * **Server:** A program that listens for incoming requests from clients and provides services in response. In this case, the server will receive MCP messages, interpret them as requests to execute Robot Framework library keywords, and send back the results as MCP messages. * **Client:** A program that sends requests to the server. **General Steps** Here's a high-level outline of the steps involved: 1. **Choose an MCP Implementation/Library:** You'll need a library or framework that handles the MCP protocol details (message encoding/decoding, connection management, etc.). There isn't a single, universally standard MCP library, so you'll need to find one that suits your needs and programming language. If you're using Python (which is common with Robot Framework), you might need to adapt an existing MCP implementation or create your own. 2. **Create a Server Application:** This will be the core of your MCP server. It will: * **Listen for Incoming Connections:** Set up a socket to listen for incoming TCP/IP connections from MCP clients. * **Receive MCP Messages:** Receive and decode MCP messages from clients. * **Parse MCP Messages:** Determine which Robot Framework keyword the client is requesting to execute and extract any arguments. * **Execute Robot Framework Keywords:** Call the appropriate keyword from your Robot Framework library with the provided arguments. * **Format Results as MCP Messages:** Take the results returned by the Robot Framework keyword (success/failure, return values) and encode them into MCP messages. * **Send MCP Response:** Send the MCP response message back to the client. * **Handle Errors:** Gracefully handle errors that occur during message processing or keyword execution. 3. **Map MCP Messages to Robot Framework Keywords:** You'll need a mechanism to map incoming MCP messages to specific keywords in your Robot Framework library. This could be a simple lookup table or a more sophisticated routing system. 4. **Implement Data Serialization/Deserialization:** MCP messages are typically byte streams. You'll need to serialize data (arguments to keywords, return values) into a format suitable for transmission over MCP and deserialize it on the receiving end. Common serialization formats include: * **JSON:** Human-readable and widely supported. * **Protocol Buffers (protobuf):** Efficient and language-neutral. * **MessagePack:** Another efficient binary serialization format. * **Custom Binary Format:** If you need maximum performance or have very specific requirements, you could define your own binary format. 5. **Error Handling:** Implement robust error handling to catch exceptions during keyword execution, message parsing, or network communication. Send appropriate error messages back to the client via MCP. **Example (Conceptual - Python)** ```python # This is a simplified example and requires a real MCP library # and proper error handling. import socket import json from robot.api import logger # For Robot Framework logging # Assume you have a Robot Framework library called 'MyLibrary' from MyLibrary import MyLibrary # MCP Configuration HOST = '127.0.0.1' # Standard loopback interface address (localhost) PORT = 65432 # Port to listen on (non-privileged ports are > 1023) # Initialize Robot Framework library my_library = MyLibrary() def handle_client(conn, addr): print(f"Connected by {addr}") while True: data = conn.recv(1024) # Receive data from the client if not data: break try: # Decode MCP message (assuming JSON for simplicity) message = json.loads(data.decode('utf-8')) keyword = message['keyword'] args = message.get('args', []) # Arguments are optional # Execute Robot Framework keyword try: result = getattr(my_library, keyword)(*args) # Call the keyword response = {'status': 'success', 'result': result} except Exception as e: logger.error(f"Error executing keyword: {e}") response = {'status': 'error', 'message': str(e)} # Encode response as MCP message (JSON) response_data = json.dumps(response).encode('utf-8') conn.sendall(response_data) except json.JSONDecodeError: error_message = {'status': 'error', 'message': 'Invalid JSON'} conn.sendall(json.dumps(error_message).encode('utf-8')) except AttributeError: error_message = {'status': 'error', 'message': f'Keyword "{keyword}" not found'} conn.sendall(json.dumps(error_message).encode('utf-8')) except Exception as e: logger.exception("Unexpected error") error_message = {'status': 'error', 'message': f'Internal server error: {e}'} conn.sendall(json.dumps(error_message).encode('utf-8')) conn.close() print(f"Connection closed with {addr}") def start_server(): with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s: s.bind((HOST, PORT)) s.listen() print(f"Listening on {HOST}:{PORT}") while True: conn, addr = s.accept() handle_client(conn, addr) # Handle each client in a separate thread for concurrency (recommended) if __name__ == "__main__": start_server() ``` **Important Considerations** * **Security:** If you're exposing your Robot Framework library over a network, security is paramount. Consider: * **Authentication:** Verify the identity of clients before allowing them to execute keywords. * **Authorization:** Control which clients have access to which keywords. * **Encryption:** Encrypt the MCP messages to protect sensitive data in transit (e.g., using TLS/SSL). * **Concurrency:** If you expect multiple clients to connect to your server simultaneously, you'll need to handle concurrency properly (e.g., using threads or asynchronous programming). The example above shows a basic single-threaded server. For production, you'd want to use threads or asyncio. * **Error Handling:** Implement robust error handling to catch exceptions during keyword execution, message parsing, or network communication. Send appropriate error messages back to the client via MCP. * **Data Types:** Carefully consider how you'll handle data types when passing arguments to keywords and returning results. MCP typically deals with byte streams, so you'll need to serialize and deserialize data appropriately. * **Performance:** If performance is critical, choose efficient serialization formats and optimize your code. * **MCP Library Choice:** The choice of MCP library will significantly impact the complexity of your implementation. If a suitable library doesn't exist, you might need to implement the MCP protocol yourself, which is a non-trivial task. **In summary:** Turning a Robot Framework library into an MCP server involves creating a server application that listens for MCP messages, parses them to determine which Robot Framework keyword to execute, executes the keyword, and sends the results back to the client as MCP messages. You'll need to choose an MCP library, implement data serialization/deserialization, and handle concurrency and security. The complexity of the task depends on the specific requirements of your application and the availability of suitable MCP libraries. The example code provides a basic starting point, but it needs to be adapted and extended to meet the needs of a real-world application. Remember to prioritize security and error handling.

Fusion 360 MCP Integration

Enables AI assistants to interact programmatically with Autodesk Fusion 360 for creating parametric 3D models through simple API calls.

MCP Bridge API

MCP Bridge es un proxy ligero, rápido y agnóstico a LLM para conectarse a múltiples servidores del Protocolo de Contexto de Modelos (MCP) a través de una API REST unificada. Permite la ejecución segura de herramientas en diversos entornos como dispositivos móviles, web y periféricos. Diseñado para la flexibilidad, la escalabilidad y la fácil integración con cualquier backend de LLM.

ITSM Integration Platform

Here are a few possible translations of "MCP for ITSM tool integration," depending on the context. "MCP" is the tricky part, as it could stand for several things. I'll provide options based on the most likely interpretations: **Assuming "MCP" stands for "Managed Cloud Provider":** * **Integración de herramientas ITSM con un proveedor de nube gestionada.** (This is a general translation.) * **Integración de herramientas ITSM a través de un proveedor de nube gestionada.** (This emphasizes the "through" aspect.) **Assuming "MCP" stands for "Microsoft Certified Professional" (less likely in this context, but possible):** * **Integración de herramientas ITSM con un profesional certificado de Microsoft.** (This is a literal translation, but might not be the best if you're talking about a *solution* rather than a person.) * **Integración de herramientas ITSM con una solución basada en la certificación Microsoft.** (This is a more nuanced translation, suggesting the integration leverages Microsoft certification standards.) **Assuming "MCP" is an acronym specific to the company or project:** * **Integración de herramientas ITSM con [Nombre completo de MCP].** (The best option if you know what MCP stands for. For example: "Integración de herramientas ITSM con el Módulo de Control de Procesos.") **General Options (if you don't know what MCP stands for and need a placeholder):** * **Integración de herramientas ITSM con MCP.** (Simply leaves the acronym as is. This is fine if the audience knows what MCP means.) * **Integración de herramientas ITSM con [Sistema/Plataforma/Herramienta] MCP.** (This is a more descriptive placeholder, suggesting what MCP *might* be.) **Therefore, to give you the *best* translation, I need to know what "MCP" stands for in your context.** Please provide more information!

Google Chat MCP Server

Enables posting text messages to Google Chat spaces through webhook-based integration, providing simple and secure message delivery without OAuth setup requirements.

w3c-mcp

MCP Server for accessing W3C/WHATWG/IETF web specifications. Provides AI assistants with access to official web standards data including specifications, WebIDL definitions, CSS properties, and HTML elements.

Simple MCP POC

A proof-of-concept MCP server that enables reading local files and performing basic arithmetic operations. It provides a simple foundation for understanding how tools are exposed to MCP clients.

Codebase MCP Server

Enables AI assistants to semantically search and understand code repositories using PostgreSQL with pgvector embeddings. Provides repository indexing, natural language code search, and development task management with git integration.