Discover Awesome MCP Servers
Extend your agent with 29,072 capabilities via MCP servers.
- All29,072
- Developer Tools3,867
- Search1,714
- Research & Data1,557
- AI Integration Systems229
- Cloud Platforms219
- Data & App Analysis181
- Database Interaction177
- Remote Shell Execution165
- Browser Automation147
- Databases145
- Communication137
- AI Content Generation127
- OS Automation120
- Programming Docs Access109
- Content Fetching108
- Note Taking97
- File Systems96
- Version Control93
- Finance91
- Knowledge & Memory90
- Monitoring79
- Security71
- Image & Video Processing69
- Digital Note Management66
- AI Memory Systems62
- Advanced AI Reasoning59
- Git Management Tools58
- Cloud Storage51
- Entertainment & Media43
- Virtualization42
- Location Services35
- Web Automation & Stealth32
- Media Content Processing32
- Calendar Management26
- Ecommerce & Retail18
- Speech Processing18
- Customer Data Platforms16
- Travel & Transportation14
- Education & Learning Tools13
- Home Automation & IoT13
- Web Search Integration12
- Health & Wellness10
- Customer Support10
- Marketing9
- Games & Gamification8
- Google Cloud Integrations7
- Art & Culture4
- Language Translation3
- Legal & Compliance2
Remote MCP Server with WorkOS AuthKit
An example MCP server that allows remote clients to connect and authenticate using WorkOS AuthKit, providing organization-centric authentication with permission-based access control for tools.
Nara Market FastMCP Server
Provides access to South Korean government procurement (G2B) and Nara Market shopping mall data, enabling users to search bid announcements, procurement statistics, product catalogs, and contract information through 15 specialized tools.
MCP client-server
Okay, I can help you understand the concept and provide a basic outline for creating an MCP (Minecraft Protocol) client and server. However, building a fully functional MCP client and server is a complex task that requires significant programming knowledge and time. I'll give you a simplified overview and point you in the right direction. **Understanding the Minecraft Protocol (MCP)** The Minecraft Protocol is the communication protocol used between Minecraft clients and servers. It's a binary protocol, meaning data is sent as raw bytes, not human-readable text. It's constantly evolving with each Minecraft version. Key aspects include: * **Handshaking:** The initial connection process where the client and server agree on the protocol version. * **Login:** Authentication of the player. * **Data Packets:** Packets are used to send information about the world, entities, player actions, chat messages, and more. Each packet has a specific ID and a defined structure. * **Compression:** The protocol supports compression to reduce bandwidth usage. * **Encryption:** The protocol uses encryption to protect sensitive data like passwords. **High-Level Outline** Here's a general outline for creating a basic MCP client and server: **1. Choose a Programming Language:** * **Java:** The language Minecraft is written in. It's a natural choice and has libraries that can help. * **Python:** Easier to learn and prototype with, but might be less performant for a full-fledged server. * **C++:** Offers the best performance but is more complex. * **C#:** A good option, especially if you're familiar with .NET. **2. Set Up Networking:** * **Sockets:** Use sockets to establish a TCP connection between the client and server. This is the foundation of network communication. **3. Implement the Handshake:** * **Client:** * Send a handshake packet to the server. This packet includes the protocol version, server address, and next state (login or status). * **Server:** * Receive the handshake packet. * Validate the protocol version. * Set the connection state based on the "next state" value. **4. Implement Login (Simplified):** * **Client:** * Send a login start packet with the player's username. * **Server:** * Receive the login start packet. * (For a very basic server, you might skip authentication and just accept the username.) * Send a login success packet back to the client. * **Client:** * Receive the login success packet. **5. Implement Basic Data Packet Handling:** * **Client & Server:** * Define structures for the packets you want to support (e.g., chat messages, player position updates). * Implement functions to serialize (encode) data into packets and deserialize (decode) packets into data. * Use a packet ID to identify the type of packet being sent/received. * Implement a main loop that continuously reads data from the socket, identifies the packet, and processes it. **6. Implement Compression (Optional):** * Use a compression algorithm like zlib to compress packets before sending them. **7. Implement Encryption (Optional):** * Use encryption (e.g., AES) to encrypt packets after the handshake. **Example (Conceptual - Python):** ```python import socket import struct # For packing/unpacking binary data # --- Server --- def handle_client(client_socket): # Receive handshake handshake_data = client_socket.recv(256) # Adjust buffer size as needed # ... (Parse handshake data to get protocol version, etc.) # Send login success (simplified) login_success_packet = struct.pack(">bi", 0x02, 12345) # Example packet ID and data client_socket.sendall(login_success_packet) # Main loop (receive and process packets) while True: try: packet_header = client_socket.recv(2) # Example: 2 bytes for packet ID if not packet_header: break # Connection closed packet_id = struct.unpack(">h", packet_header)[0] # Unpack short (2 bytes) if packet_id == 0x01: # Example: Chat message packet # ... (Receive chat message data) # ... (Process chat message) pass else: print(f"Unknown packet ID: {packet_id}") except ConnectionResetError: print("Client disconnected") break # --- Client --- def connect_to_server(server_address, server_port): client_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) client_socket.connect((server_address, server_port)) # Send handshake handshake_packet = struct.pack(">bi", 0x00, 762) # Example packet ID and protocol version client_socket.sendall(handshake_packet) # Receive login success login_success_data = client_socket.recv(256) # ... (Parse login success data) # Main loop (send and receive packets) while True: # ... (Create a chat message packet) chat_message_packet = struct.pack(">hi", 0x01, 67890) # Example packet ID and data client_socket.sendall(chat_message_packet) # ... (Receive packets from the server) server_data = client_socket.recv(256) # ... (Process server data) ``` **Important Considerations:** * **Protocol Version:** The Minecraft protocol changes with each version. You *must* use the correct protocol version for the Minecraft client you want to connect to. You can find protocol information on the Minecraft Wiki and in community-maintained documentation. * **Data Types:** The protocol uses specific data types (e.g., VarInt, VarLong, strings with prefixes). You need to handle these correctly. * **Error Handling:** Implement robust error handling to deal with network issues, invalid packets, and other unexpected situations. * **Security:** Be very careful about security, especially if you're handling authentication. Never store passwords in plain text. * **Threading/Asynchronous Programming:** For a server, you'll need to use threading or asynchronous programming to handle multiple clients concurrently. **Where to Find More Information:** * **Minecraft Protocol Wiki:** The official Minecraft Wiki is a good starting point, but it may not always be up-to-date. Search for "Minecraft Protocol" on the wiki. * **Wiki.vg:** This is a very valuable resource for the Minecraft protocol. It has detailed information about packets, data types, and the handshake process. [https://wiki.vg/Protocol](https://wiki.vg/Protocol) * **Community Projects:** Look at open-source Minecraft client and server implementations (e.g., in Java, Python, or C++) for inspiration and examples. Be aware that these projects can be complex. * **Books and Tutorials:** Search online for tutorials and books on Minecraft server development. **In summary, building an MCP client and server is a significant undertaking. Start with the basics (sockets, handshake, login) and gradually add more features. Use the resources I've provided to understand the protocol and learn from existing projects.**
Spider MCP Server
Enables crawling and extracting clean content from documentation websites with optional LLM-powered analysis for intelligent summaries, code example extraction, and content classification.
Better Telegram MCP
Production-grade MCP server for Telegram with dual-mode Bot API and MTProto. 6 composite tools covering messages, chats, media, contacts management with 3-tier token optimization.
MCP-Server-and-client-Implementation-on-Linux
Okay, here's a translation of "MCP Server and client Implementation on Linux (Rather then using Claude Desktop)" into Spanish, along with some considerations for clarity: **Option 1 (Most Direct):** * **Implementación de servidor y cliente MCP en Linux (en lugar de usar Claude Desktop)** **Option 2 (Slightly More Explanatory):** * **Implementación de un servidor y un cliente MCP en Linux, en lugar de utilizar la aplicación de escritorio Claude.** **Option 3 (If you want to emphasize *avoiding* Claude Desktop):** * **Implementación de un servidor y un cliente MCP en Linux, sin usar Claude Desktop.** **Explanation of Choices:** * **"Implementación"** is the standard translation of "implementation." * **"Servidor y cliente"** are the direct translations of "server and client." * **"MCP"** It's assumed that "MCP" is an acronym or proper noun that doesn't need translation. If it *does* have a Spanish equivalent, you should substitute it. * **"en lugar de"** is the most common translation of "rather than." "En vez de" is also acceptable. * **"aplicación de escritorio"** is a good translation of "desktop application" or "desktop." I used it in Option 2 to make it clearer that you're referring to the Claude Desktop *application*. * **"sin usar"** (Option 3) emphasizes the *avoidance* of Claude Desktop. **Which option is best depends on the context.** If the audience is very familiar with the terminology, Option 1 is fine. If you want to be extra clear, Option 2 is a good choice. If the key point is *not* using Claude Desktop, Option 3 is best.
Portfolio Tracker MCP Server
Enables AI clients to track investment portfolios by retrieving positions, calculating profit and loss, and refreshing price data via Yahoo Finance. It allows users to monitor overall performance and query specific ticker details through natural language interactions.
Edgee MCP Server
MCP Server for the Edgee API, enabling organization management, project operations, component management, and user administration through the Model Context Protocol.
mcp-server-intro
MCP Domain Availability Server
Enables checking domain availability and pricing using the GoDaddy OTE API, supporting multiple TLD suffixes and both fast and full check modes.
ThinMCP
A local MCP gateway that compresses multiple upstream servers into two tools, search and execute, to minimize model context usage. It provides a compact, code-driven interface for discovering and calling tools across various upstream sources on demand.
Amadeus MCP Server
Un servidor de Protocolo de Contexto de Modelo que se conecta a la API de Amadeus, permitiendo a los asistentes de IA buscar vuelos, analizar precios, encontrar las mejores ofertas de viaje y planificar viajes a varias ciudades.
docx-comparison-mcp
Generates Word documents for comparison tables and specifications from structured JSON data. Supports both stdio mode for Claude Desktop/Code and HTTP mode for AI frameworks like Dify and LangFlow.
Brightspace MCP Server
MCP server for Brightspace (D2L): check grades, due dates, announcements, rosters & more using Claude, ChatGPT, Cursor, or any MCP client. Built with TypeScript and the D2L REST API.
local-memory-mcp
Description: Persistent local memory for Claude, Cursor and Codex. 13 MCP tools, SQLite + FTS5 + Knowledge Graph. No cloud, no API keys. One command: npx @studiomeyer/local-memory-mcp.
WHOOP MCP Server
Enables access to WHOOP fitness and health data through all WHOOP v2 API endpoints. Supports OAuth 2.0 authentication and provides comprehensive access to user profiles, physiological cycles, recovery metrics, sleep analysis, and workout data.
Remote MCP Server on Cloudflare
Featurebase MCP Server
Enables interaction with Featurebase API to manage feature requests, feedback posts, comments, and upvotes. Supports creating, updating, and organizing customer feedback through natural language commands.
Figma MCP Server
Espejo de
MCP UI Glue Code Generator
Automates frontend integration by mapping messy API JSON responses to Vue or React Design System components, generating Zod schemas for type-safe data transformation with live UI previews in chat.
MCPX MCP Gateway
MCPX is a remote-first MCP aggregator that enables zero-code integration, unified access, and dynamic routing across multiple MCP servers. It offers tool-level access controls, usage visibility, and customization to streamline and secure agentic workflows.
figma-mcp-flutter-test
Here are a few options for translating "Figma MCP Server を使用して Figma デザインを Flutter で再現する実験プロジェクト" depending on the nuance you want to convey: **Option 1 (Most Literal):** * **Spanish:** Proyecto experimental para reproducir diseños de Figma en Flutter usando el servidor Figma MCP. **Option 2 (Slightly More Natural):** * **Spanish:** Proyecto experimental para recrear diseños de Figma en Flutter con el servidor Figma MCP. **Option 3 (Emphasizing the "Experiment"):** * **Spanish:** Proyecto experimental que explora la recreación de diseños de Figma en Flutter utilizando el servidor Figma MCP. **Explanation of Choices:** * **"Proyecto experimental"**: This is the standard translation for "experimental project." * **"reproducir" / "recrear"**: Both "reproducir" and "recrear" can work for "reproduce." "Recrear" might be slightly better as it implies a more creative process. * **"usando" / "con" / "utilizando"**: All three translate to "using" or "with." "Utilizando" is more formal. "Con" is often the most natural choice. * **"el servidor Figma MCP"**: This part is kept as is, assuming "Figma MCP Server" is a specific, known entity. I recommend **Option 2: "Proyecto experimental para recrear diseños de Figma en Flutter con el servidor Figma MCP."** as it sounds the most natural in Spanish.
zoty
A lightweight MCP server that connects AI agents to a local Zotero library for paper management and metadata retrieval. It enables users to search titles and abstracts, browse collections, and automatically ingest papers via arXiv ID or DOI with PDF attachments.
cook-tool
A recipe query tool that supports querying recipes and reporting dish names through the command line, suitable for cooking enthusiasts and developers.
MCP Dockerized Server
A minimal, containerized MCP server that exposes a Streamable HTTP transport with API key authentication, allowing secure access to MCP endpoints.
BinDiff MCP Tool
Enables binary comparison capabilities by leveraging IDA Pro and BinDiff to analyze similarities and differences between files. Users can perform automated function analysis to identify changed functions and compare original binaries against patched versions.
AuthMCP Gateway
Secure MCP protocol proxy with OAuth2 + Dynamic Client Registration (DCR), JWT auth, RBAC, rate limiting, multi-server aggregation, and a monitoring/admin dashboard.
MUXI Framework
Un marco de agentes de IA extensible.
World Bank Data360 MCP Server
Enables access to World Bank Data360 API with 1000+ economic and social indicators across 200+ countries and 60+ years of historical data, allowing searches, temporal coverage checks, and filtered data retrieval through natural language queries.
programmatic-mcp
A meta MCP server that orchestrates other MCP servers by lazily connecting to them and exposing their tools as JavaScript libraries. It allows users to execute JavaScript code that programmatically interacts with multiple MCP servers within a unified environment.