Discover Awesome MCP Servers

MCP Mobile Automation Test

A comprehensive server that integrates mobile testing frameworks with JIRA, generating BDD test scenarios and framework-compatible test scripts automatically.

MCP Screenshot Server

Enterprise-grade screenshot capture server for AI agents with multi-format support, PII masking, multi-monitor support, and security controls for capturing full screens, specific windows, or custom regions across Linux, macOS, and Windows.

Kali MCP Server

Enables AI assistants to execute penetration testing commands and security tools on Kali Linux remotely. Supports automated reconnaissance, vulnerability scanning, and CTF solving through integration with 25+ offensive security tools like nmap, gobuster, and nuclei.

Memory Bank MCP Server

A Model Context Protocol server that provides structured workflow tools for managing software development projects through different complexity levels, offering specialized modes for project planning, design, implementation, and documentation.

Strapi MCP Server

Enables AI assistants to interact with Strapi CMS instances through REST API operations. Supports content management, media uploads, schema introspection, and multiple server configurations with JWT authentication.

message-mcp

Real-time push notifications and alert sounds free you from staring at the screen. While the AI works, you can comfortably enjoy a cup of coffee.

replicant-mcp

An MCP server that enables AI assistants to build, test, and debug Android applications by interacting directly with the Android development environment. It provides tools for managing emulators, executing Gradle tasks, running ADB commands, and performing UI automation via accessibility trees.

MCP Obsidian

Enables semantic search across Obsidian vaults using vector embeddings and ChromaDB. Supports multiple vaults with real-time indexing and provides both MCP server and CLI interfaces for natural language querying of notes.

MCP Secure Local Server

A security-focused Model Context Protocol server that enables controlled local tool execution through strict network firewalls, filesystem protections, and rate-limiting policies. It features a plugin-based architecture for progressive tool discovery and includes reference implementations for web searching and bug tracking.

DICOM MCP Server

Enables AI assistants to query, read, download, and move medical imaging data on DICOM servers (PACS, VNA) including patient searches, study retrieval, PDF report extraction, and image transfer to AI endpoints for analysis.

Whisper CLI MCP Server

An MCP server that provides shell command execution and OpenAI Whisper transcription capabilities for audio files.

genome-mcp

Intelligent Genomic Data Server Provides high-quality gene information queries, homologous gene analysis, and evolutionary research functions via the MCP protocol.

github-mcp-server

Okay, here are a few options for setting up a GitHub-backed Minecraft Protocol (MCP) server that you can use with Cursor or Claude for development and testing. I'll focus on approaches that are relatively easy to manage and integrate with your coding workflow. **Understanding the Goal** The core idea is to have a Minecraft server that: 1. **Is version-controlled:** Its configuration and potentially even some of its data are stored in a GitHub repository. 2. **Is easily deployable/runnable:** You can quickly start and stop it for testing changes you make in Cursor or Claude. 3. **Is relatively lightweight:** You don't need a massive, resource-intensive server for development. **Option 1: Dockerized Server with GitHub Configuration** This is a popular and recommended approach. Docker allows you to package the server and its dependencies into a container, making it portable and reproducible. * **GitHub Repository:** * Create a new GitHub repository (e.g., `my-minecraft-dev-server`). * In the repository, create the following structure: ``` my-minecraft-dev-server/ ├── Dockerfile ├── server.properties (Minecraft server configuration) ├── plugins/ (Optional: Your development plugins) └── data/ (Optional: World data, if you want to version it) ``` * **`Dockerfile`:** This file defines how to build the Docker image. Here's a basic example (adapt it to your desired Minecraft version): ```dockerfile FROM openjdk:17-slim # Or your preferred Java version # Set working directory WORKDIR /app # Copy server files COPY server.properties . COPY plugins/ plugins/ COPY data/ data/ # Download the Minecraft server JAR (replace with your desired version) RUN wget https://launcher.mojang.com/v1/objects/5b8f03ba9545a4ca3c67422afca9c610c20292a6/server.jar -O minecraft_server.jar # Expose the Minecraft server port EXPOSE 25565 # Start the server CMD ["java", "-Xmx2G", "-Xms2G", "-jar", "minecraft_server.jar", "nogui"] ``` * **Explanation:** * `FROM`: Specifies the base image (Java). Use a Java version compatible with your Minecraft server version. * `WORKDIR`: Sets the working directory inside the container. * `COPY`: Copies your configuration files, plugins, and world data into the container. * `RUN wget ...`: Downloads the Minecraft server JAR file. **Important:** Replace the URL with the correct download URL for the Minecraft version you want to use. You can find these URLs on the Minecraft website or in the Minecraft launcher's JSON files. * `EXPOSE`: Exposes the default Minecraft port (25565). * `CMD`: Defines the command to run when the container starts. The `-Xmx` and `-Xms` flags set the maximum and initial memory allocation for the server. Adjust these values based on your needs. `nogui` runs the server in headless mode (without a graphical interface). * **`server.properties`:** This file contains the Minecraft server configuration. You can customize settings like the server name, difficulty, game mode, etc. A minimal example: ```properties enable-command-block=true gamemode=creative difficulty=normal pvp=true level-name=world server-port=25565 server-ip= max-players=10 online-mode=false # Set to false for development (no authentication) spawn-animals=true spawn-npcs=true allow-flight=true motd=My Dev Server ``` * **Important:** Set `online-mode=false` for development purposes. This disables authentication, allowing you to connect without a valid Minecraft account. **Do not use this in a public server!** * **`plugins/` (Optional):** Place your development plugins (JAR files) in this directory. * **`data/` (Optional):** If you want to version your world data, place the world folder in this directory. Be aware that world data can be large, so consider using `.gitignore` to exclude unnecessary files. * **Building and Running the Docker Container:** 1. **Clone the repository:** `git clone <your_repository_url>` 2. **Navigate to the repository directory:** `cd my-minecraft-dev-server` 3. **Build the Docker image:** `docker build -t my-minecraft-server .` (The `.` specifies the current directory as the build context.) 4. **Run the Docker container:** `docker run -d -p 25565:25565 my-minecraft-server` * `-d`: Runs the container in detached mode (in the background). * `-p 25565:25565`: Maps port 25565 on your host machine to port 25565 in the container. * **Connecting to the Server:** * In your Minecraft client, connect to `localhost:25565`. * **Workflow with Cursor/Claude:** 1. **Edit Files:** Make changes to your plugins, `server.properties`, or other configuration files in the GitHub repository using Cursor or Claude. 2. **Commit and Push:** Commit your changes to the repository and push them to GitHub. 3. **Rebuild the Docker Image (if necessary):** If you've changed the `Dockerfile` or any files that are copied during the build process, you'll need to rebuild the image: `docker build -t my-minecraft-server .` 4. **Restart the Container:** To apply the changes, stop and restart the Docker container: * `docker stop <container_id>` (Find the container ID using `docker ps`) * `docker run -d -p 25565:25565 my-minecraft-server` **Option 2: Direct Server Installation with GitHub Configuration (Less Recommended)** This approach involves installing the Minecraft server directly on your machine and using GitHub to manage the configuration files. It's less isolated than Docker, but it can be simpler to set up initially. * **GitHub Repository:** Similar to Option 1, create a repository to store your `server.properties`, plugins, and potentially world data. * **Install Minecraft Server:** 1. Download the Minecraft server JAR file from the Minecraft website. 2. Create a directory on your machine to store the server files (e.g., `~/minecraft-dev-server`). 3. Place the JAR file in this directory. * **Configure the Server:** 1. Create a `server.properties` file in the server directory. (You can copy the example from Option 1 and customize it.) 2. Create a `plugins/` directory for your development plugins. * **Version Control:** 1. Initialize a Git repository in the server directory: `git init` 2. Add the `server.properties` file, `plugins/` directory, and any other files you want to track to the repository. 3. Create a `.gitignore` file to exclude unnecessary files (e.g., the `world/` directory if you don't want to version the world data). 4. Commit your changes and push them to your GitHub repository. * **Running the Server:** 1. Open a terminal and navigate to the server directory. 2. Run the server: `java -Xmx2G -Xms2G -jar minecraft_server.jar nogui` * **Workflow with Cursor/Claude:** 1. **Edit Files:** Make changes to your plugins, `server.properties`, or other configuration files in the server directory using Cursor or Claude. 2. **Commit and Push:** Commit your changes to the repository and push them to GitHub. 3. **Restart the Server:** Stop the server (usually by typing `stop` in the server console) and then run it again to apply the changes. **Option 3: Using a Pre-built Docker Image (Simplest for Quick Setup)** If you just want a quick and easy way to get a server running, you can use a pre-built Docker image from Docker Hub. This avoids the need to create your own `Dockerfile`. * **Find a Suitable Image:** Search Docker Hub for Minecraft server images. Look for images that are well-maintained and have good documentation. Some popular options include: * `itzg/minecraft-server` * `kbs2/minecraft-server` * **Run the Container:** Use the `docker run` command to start the container, following the instructions provided in the image's documentation. You'll typically need to specify environment variables to configure the server (e.g., the Minecraft version, server properties). Example (using `itzg/minecraft-server`): ```bash docker run -d \ -p 25565:25565 \ -e EULA=TRUE \ -e VERSION=LATEST \ -e ONLINE_MODE=FALSE \ -v minecraft_data:/data \ itzg/minecraft-server ``` * `-e EULA=TRUE`: Accepts the Minecraft EULA. * `-e VERSION=LATEST`: Uses the latest Minecraft version. You can specify a specific version (e.g., `1.19.4`). * `-e ONLINE_MODE=FALSE`: Disables authentication (for development). * `-v minecraft_data:/data`: Creates a named volume to store the server data. This allows the data to persist even if you stop and remove the container. * **Configuration:** Many pre-built images allow you to configure the server using environment variables or by mounting a configuration directory. Refer to the image's documentation for details. * **GitHub Integration:** You can still use a GitHub repository to store your `server.properties` file and mount it into the container. This allows you to version control your configuration. **Key Considerations:** * **Minecraft Version:** Make sure the Minecraft server version you use is compatible with the plugins you're developing. * **Java Version:** Use a Java version that is compatible with the Minecraft server version. Minecraft 1.17 and later require Java 17. * **Memory Allocation:** Adjust the `-Xmx` and `-Xms` flags to allocate enough memory to the server. The amount of memory you need will depend on the number of players, the size of the world, and the complexity of your plugins. * **EULA:** You must accept the Minecraft EULA to run a Minecraft server. If you're using a Docker image, check the documentation for how to accept the EULA (usually through an environment variable). * **Security:** When `online-mode=false`, the server is not authenticated. **Do not use this setting on a public server!** It's only suitable for local development. * **World Data:** Be mindful of the size of your world data. If you're versioning it, consider using `.gitignore` to exclude unnecessary files. * **Plugin Development:** When developing plugins, you'll typically need to compile your code into JAR files and place them in the `plugins/` directory of the server. **Which Option to Choose?** * **Beginner:** Option 3 (pre-built Docker image) is the easiest way to get started quickly. * **Intermediate:** Option 1 (Dockerized server with GitHub configuration) provides a good balance of flexibility and reproducibility. * **Advanced:** Option 2 (direct server installation) gives you the most control, but it's also the most complex to manage. **Spanish Translation of Key Terms:** * GitHub: GitHub * MCP (Minecraft Protocol): MCP (Protocolo de Minecraft) * Cursor: Cursor * Claude: Claude * Server: Servidor * Docker: Docker * Dockerfile: Dockerfile * Repository: Repositorio * Configuration: Configuración * Plugins: Plugins (Complementos) * World Data: Datos del Mundo * Image: Imagen * Container: Contenedor * Port: Puerto * Environment Variables: Variables de Entorno * Version Control: Control de Versiones * Commit: Confirmar (Cambios) * Push: Enviar (Cambios) * EULA: EULA (Acuerdo de Licencia de Usuario Final) * Online Mode: Modo Online * Offline Mode: Modo Offline I hope this helps! Let me know if you have any other questions.

VibeOps MCP

Enforces structured product development through contract-based validation of modules, features, and issues with type-specific requirements (user stories, bugs, tech debt, spikes) using JSON schemas.

Pommel Horse Aesthetics MCP Server

Analyzes pommel horse gymnastics routines using a categorical aesthetics framework that evaluates element groups, spatial patterns, temporal qualities, and form with 85% deterministic taxonomy and 15% LLM synthesis.

ICON MCP v109 MCP Server

An MCP server that provides AI agents and LLMs with standardized tool access to the ICON MCP v109 API. It supports asynchronous operations and simplifies deployment through Docker and Docker Compose.

DebtStack.ai MCP Server

Provides AI agents with real-time access to corporate credit data, including debt structures, bond pricing, and guarantor chains extracted from SEC filings. It enables complex financial analysis such as screening companies by leverage, tracing corporate hierarchies, and searching covenant language.

Twitter MCP Server

Enables Twitter automation including posting tweets, replying to tweets, and searching for tweets with structured results using browser automation through Browserbase and Stagehand.

Figma to React MCP

Automates the conversion of Figma designs into TypeScript React components and integrates with GitHub to create pull requests for the generated code. It includes visual regression testing with Playwright and accessibility validation to ensure implementations match the original designs.

Xcode Errors MCP Server

Bridges Xcode and Cursor to provide real-time access to build errors, warnings, and debug output from Xcode's DerivedData, enabling automated error analysis and fixes directly within Cursor.

M365 Calendar MCP Server

Enables AI assistants to manage Microsoft 365 and Outlook calendars through the Microsoft Graph API. It supports comprehensive event operations including listing, creating, and updating meetings, as well as finding available slots across multiple attendees.

macOS Control MCP Server

Enables full desktop automation on macOS through natural language, including mouse control, keyboard input, screen capture, and GUI interaction using PyAutoGUI.

FastMCP Todo Server

Here are a few options for translating your request, depending on the nuance you want to convey: **Option 1 (Most straightforward):** > Servidor MCP simple para proporcionar a mi Cursor Local acceso para agregar elementos a mi lista de tareas de MongoDB. **Option 2 (Slightly more natural flow):** > Un servidor MCP sencillo para darle a mi Cursor Local acceso para añadir elementos a mi lista de tareas en MongoDB. **Option 3 (Focus on the purpose):** > Un servidor MCP simple que permita a mi Cursor Local añadir elementos a mi lista de tareas de MongoDB. **Explanation of choices:** * **MCP:** It's likely best to leave "MCP" as is, assuming it's an acronym or specific term. * **Cursor Local:** Again, leaving this as is is probably best, unless you have a specific Spanish equivalent in mind. * **agregar / añadir:** Both "agregar" and "añadir" are good translations for "add." "Añadir" might sound slightly more natural in some contexts. * **lista de tareas:** This is the standard translation for "todo list." * **en MongoDB / de MongoDB:** Both are acceptable. "En MongoDB" (in MongoDB) is slightly more common when referring to the location of the data. "De MongoDB" (of MongoDB) could be used to emphasize that the list *belongs* to MongoDB. Choose the option that best fits the context of your project and your personal preference.

RoxyBrowser Playwright MCP

Enables AI-powered browser automation through RoxyChrome browsers using Playwright's accessibility tree for fast, lightweight web interactions without requiring vision models or screenshots.

Shell Executor MCP Server

Provides safe shell command execution capabilities for AI agents and tools like VS Code Copilot through a whitelist-based filtering system.

Nordic Thingy:52 MCP Server

Enables Claude to control Nordic Thingy:52 IoT devices via Bluetooth LE, allowing users to manage LED colors, play sounds, and read environmental sensors through natural language conversations.

MCP Server Starter Template

A comprehensive template for building MCP servers that expose UI component registries and design systems to AI assistants. It enables users to browse, fetch, and retrieve implementation details from registries following the shadcn/ui format.