Discover Awesome MCP Servers

Walrus MCP Server

Enables AI assistants to store and retrieve data using the Walrus decentralized storage network. Supports blob storage operations, retrieval by ID, and blockchain-verified availability through the Sui network.

mac-use-mcp

Zero-dependency macOS desktop automation for AI agents. Screenshot, mouse, keyboard, clipboard, and window control via MCP. 18 tools, macOS 13+, one command: npx mac-use-mcp.

Mcp Qdrant Docker

Okay, here's a Docker configuration example for a Qdrant MCP (Multi-Cluster Proxy) server, along with explanations to help you understand it. I'll provide both a `docker-compose.yml` example and a `Dockerfile` example (if you want to build a custom image). **Understanding the Components** * **Qdrant MCP (Multi-Cluster Proxy):** This acts as a single entry point to multiple Qdrant clusters. It handles routing requests to the appropriate cluster based on configuration. It's useful for scaling, geographic distribution, and isolating workloads. * **Docker:** A platform for running applications in isolated containers. * **docker-compose:** A tool for defining and managing multi-container Docker applications. * **Dockerfile:** A text document that contains all the commands a user could call on the command line to assemble an image. **Example 1: `docker-compose.yml` (Recommended for Simplicity)** This is the easiest way to get started. It defines the Qdrant MCP service and its dependencies. ```yaml version: "3.9" # Use a recent Docker Compose version services: qdrant-mcp: image: qdrant/qdrant-mcp:latest # Use the official Qdrant MCP image ports: - "6333:6333" # Expose the gRPC port - "6334:6334" # Expose the HTTP port (for the dashboard) environment: - QDRANT_MCP__CONFIG_PATH=/qdrant-mcp/config/config.yaml # Path to the config file volumes: - ./config:/qdrant-mcp/config # Mount a local directory for configuration restart: unless-stopped networks: - qdrant-network networks: qdrant-network: driver: bridge ``` **Explanation:** * **`version: "3.9"`:** Specifies the Docker Compose file version. Use a version compatible with your Docker installation. * **`services:`:** Defines the services that make up your application. * **`qdrant-mcp:`:** The name of the service (you can choose a different name). * **`image: qdrant/qdrant-mcp:latest`:** Specifies the Docker image to use. `qdrant/qdrant-mcp` is the official image. `latest` tag is used here, but it's highly recommended to use a specific version tag (e.g., `qdrant/qdrant-mcp:v1.5.0`) for production to avoid unexpected updates. * **`ports:`:** Maps ports from the container to your host machine. * `6333:6333`: Maps the gRPC port (used for Qdrant client communication). * `6334:6334`: Maps the HTTP port (used for the Qdrant MCP dashboard). * **`environment:`:** Sets environment variables for the container. * `QDRANT_MCP__CONFIG_PATH=/qdrant-mcp/config/config.yaml`: Specifies the path to the Qdrant MCP configuration file *inside* the container. This is crucial. * **`volumes:`:** Mounts a directory from your host machine into the container. * `./config:/qdrant-mcp/config`: Mounts the `./config` directory (relative to where you run `docker-compose up`) on your host to the `/qdrant-mcp/config` directory inside the container. This allows you to modify the configuration without rebuilding the image. **You need to create a `config` directory and place your `config.yaml` file there.** * **`restart: unless-stopped`:** Automatically restarts the container if it crashes, unless you explicitly stop it. * **`networks:`:** Defines a network for the container. * **`qdrant-network:`:** The name of the network. * **`driver: bridge`:** Uses the default bridge network driver. **How to Use `docker-compose.yml`:** 1. **Create a directory:** Create a directory for your Qdrant MCP configuration (e.g., `qdrant-mcp`). 2. **Create `docker-compose.yml`:** Place the `docker-compose.yml` file in that directory. 3. **Create `config.yaml`:** Create a `config` subdirectory within the main directory (e.g., `qdrant-mcp/config`). Place your Qdrant MCP configuration file (`config.yaml`) in the `config` subdirectory. **This is essential!** See below for an example `config.yaml`. 4. **Run `docker-compose up`:** Open a terminal, navigate to the directory containing `docker-compose.yml`, and run `docker-compose up -d`. The `-d` flag runs the containers in detached mode (in the background). **Example `config.yaml` (Important!)** This is a *minimal* example. You'll need to adapt it to your specific Qdrant cluster setup. ```yaml grpc_port: 6333 http_port: 6334 clusters: cluster1: address: "qdrant-cluster-1:6333" # Replace with the actual address of your Qdrant cluster cluster2: address: "qdrant-cluster-2:6333" # Replace with the actual address of your Qdrant cluster rules: - collection_name: "my_collection" cluster: "cluster1" - collection_name: "another_collection" cluster: "cluster2" ``` **Explanation of `config.yaml`:** * **`grpc_port`:** The port the MCP listens on for gRPC requests. * **`http_port`:** The port the MCP listens on for HTTP requests (for the dashboard). * **`clusters`:** A dictionary of Qdrant clusters. Each cluster has a name (e.g., `cluster1`) and an `address`. The `address` should be the hostname or IP address and port of your Qdrant cluster's gRPC endpoint. **Replace `"qdrant-cluster-1:6333"` and `"qdrant-cluster-2:6333"` with the actual addresses of your Qdrant clusters.** These addresses must be resolvable from within the Docker container. If your Qdrant clusters are also running in Docker, use their service names within the same Docker network. * **`rules`:** A list of rules that determine which cluster a request is routed to. Each rule specifies a `collection_name` and the `cluster` to which requests for that collection should be routed. In this example, requests for the `my_collection` collection will be routed to `cluster1`, and requests for `another_collection` will be routed to `cluster2`. **Important Considerations for `config.yaml`:** * **Address Resolution:** The addresses in the `clusters` section *must* be resolvable from within the Docker container. If your Qdrant clusters are also running in Docker, make sure they are on the same Docker network and use their service names as the addresses. If they are running outside of Docker, use their IP addresses or hostnames. * **Rules:** The `rules` section is critical. Carefully define the rules to ensure that requests are routed to the correct clusters. You can use more complex rules based on other criteria (see the Qdrant MCP documentation). * **Configuration Options:** The `config.yaml` file can contain many other configuration options. Refer to the official Qdrant MCP documentation for a complete list of options. **Example 2: `Dockerfile` (For Custom Image Building - Less Common)** If you need to customize the Qdrant MCP image (e.g., add custom scripts or dependencies), you can use a `Dockerfile`. ```dockerfile FROM qdrant/qdrant-mcp:latest # Copy your custom configuration file COPY config/config.yaml /qdrant-mcp/config/config.yaml # (Optional) Add any other custom commands here, e.g., installing dependencies # Set the environment variable (if needed, but usually not necessary if you COPY the config) ENV QDRANT_MCP__CONFIG_PATH=/qdrant-mcp/config/config.yaml # The ENTRYPOINT and CMD are already defined in the base image, so you usually don't need to override them. ``` **Explanation:** * **`FROM qdrant/qdrant-mcp:latest`:** Starts from the official Qdrant MCP image. Again, use a specific version tag instead of `latest` for production. * **`COPY config/config.yaml /qdrant-mcp/config/config.yaml`:** Copies your `config.yaml` file from the `config` directory (relative to the `Dockerfile`) to the `/qdrant-mcp/config/config.yaml` location inside the image. * **`ENV QDRANT_MCP__CONFIG_PATH=/qdrant-mcp/config/config.yaml`:** Sets the environment variable. This is often redundant if you're copying the config file directly, but it's good practice to include it. * **`ENTRYPOINT` and `CMD`:** The base image already defines the `ENTRYPOINT` and `CMD` to start the Qdrant MCP server, so you usually don't need to override them. **How to Use `Dockerfile`:** 1. **Create a directory:** Create a directory for your Qdrant MCP configuration (e.g., `qdrant-mcp`). 2. **Create `Dockerfile`:** Place the `Dockerfile` in that directory. 3. **Create `config` directory and `config.yaml`:** Create a `config` subdirectory within the main directory (e.g., `qdrant-mcp/config`). Place your Qdrant MCP configuration file (`config.yaml`) in the `config` subdirectory. 4. **Build the image:** Open a terminal, navigate to the directory containing the `Dockerfile`, and run `docker build -t my-qdrant-mcp .` (the `.` specifies the current directory as the build context). Replace `my-qdrant-mcp` with a name for your custom image. 5. **Run the container:** Run the container using `docker run -d -p 6333:6333 -p 6334:6334 my-qdrant-mcp`. You might also need to specify a network if your Qdrant clusters are in Docker. **Important Notes:** * **Qdrant Cluster Addresses:** The most important part is configuring the `config.yaml` file with the correct addresses of your Qdrant clusters. Make sure these addresses are resolvable from within the Docker container. * **Networking:** If your Qdrant clusters are also running in Docker, put them on the same Docker network as the Qdrant MCP container. This will allow you to use the service names of the Qdrant clusters as the addresses in the `config.yaml` file. * **Security:** For production deployments, consider security best practices, such as using HTTPS, setting up authentication, and limiting access to the Qdrant MCP server. * **Monitoring:** Monitor the Qdrant MCP server to ensure it is running correctly and routing requests as expected. * **Documentation:** Refer to the official Qdrant MCP documentation for the most up-to-date information and configuration options: [https://qdrant.tech/documentation/concepts/mcp/](https://qdrant.tech/documentation/concepts/mcp/) **Indonesian Translation of Key Terms:** * **Docker:** Docker (no translation needed) * **Container:** Kontainer * **Image:** Citra (or Gambar) * **docker-compose:** docker-compose (no translation needed) * **Dockerfile:** Dockerfile (no translation needed) * **Qdrant MCP (Multi-Cluster Proxy):** Qdrant MCP (Proksi Multi-Klaster) * **Cluster:** Klaster * **Configuration:** Konfigurasi * **Address:** Alamat * **Port:** Port (no translation needed) * **Environment Variable:** Variabel Lingkungan * **Volume:** Volume * **Network:** Jaringan * **Rule:** Aturan I hope this comprehensive example helps you set up your Qdrant MCP server with Docker! Let me know if you have any more questions.

MCP Test

Here are a few ways to interpret "MCP server with GitHub integration" and their Indonesian translations: **1. Minecraft Protocol (MCP) Server with GitHub Integration (Focus on Minecraft):** * **Indonesian:** Server MCP (Minecraft Protocol) dengan integrasi GitHub. * **Explanation:** This is the most literal translation. It assumes you're talking about a Minecraft server that uses the MCP protocol and has some kind of integration with GitHub. This could mean using GitHub for version control of server files, automated deployments, or other related tasks. **2. Server for Managing Configuration Profiles (MCP) with GitHub Integration (Focus on Configuration):** * **Indonesian:** Server untuk mengelola profil konfigurasi (MCP) dengan integrasi GitHub. * **Explanation:** This interpretation assumes "MCP" refers to a system for managing configuration profiles (perhaps for applications or systems). The GitHub integration would likely be used for version control and collaboration on these configuration profiles. **3. Server that uses a specific MCP library/framework with GitHub Integration (Focus on a specific tool):** * **Indonesian:** Server yang menggunakan pustaka/kerangka kerja MCP tertentu dengan integrasi GitHub. * **Explanation:** This suggests that "MCP" is the name of a specific library or framework. The translation highlights that the server utilizes this MCP library and integrates with GitHub. **To provide a more accurate translation, please clarify what you mean by "MCP". For example:** * "I want to set up a Minecraft server and use GitHub to manage the server files." * "I'm looking for a tool to manage application configuration profiles and integrate it with GitHub for version control." * "I'm using the MCP framework for [specific purpose] and want to integrate it with GitHub." Once you provide more context, I can give you a more precise and helpful Indonesian translation.

Perplexity Sonar MCP Server

Server MCP untuk integrasi Perplexity API dengan Claude Desktop dan klien MCP lainnya.

pancake-pos-mcp

Enables AI assistants to manage Vietnamese e-commerce POS operations including orders, products, customers, inventory, supply chain, sales, CRM, and multi-channel integration via Pancake POS API.

BTP MCP Server

Connects AI agents to SAP BTP platform APIs for service discovery, instance management, and destination queries via natural language.

engram

An MCP server that stores atomic facts extracted from text, links them to entities and relationships, and synthesizes higher-order observations (patterns, preferences, insights) via a reflect loop.

Trayd

Trade Robinhood through Claude Code. Check portfolio, get quotes, place orders — one-line setup, no coding required. OAuth 2.1 with KMS-encrypted token storage.

mcp_repo9756c6c7-ee07-4f3a-ada4-f6e2705daa02

Ini adalah repositori pengujian yang dibuat oleh skrip pengujian MCP Server untuk GitHub.

MCP Gemini Server

Sebuah server khusus yang membungkus model AI Gemini dari Google dalam antarmuka Model Context Protocol (MCP), memungkinkan LLM (Model Bahasa Besar) lain dan sistem yang kompatibel dengan MCP untuk mengakses kemampuan Gemini seperti pembuatan konten, pemanggilan fungsi, obrolan, dan penanganan file melalui alat yang terstandarisasi.

Register UZ MCP Server

Enables access to Slovak Registry of Financial Statements data, allowing users to search companies, retrieve financial reports, balance sheets, income statements, and analyze Slovak business financial data through natural language queries.

Proton MCP Server

Enables full Proton Mail management through the Model Context Protocol by connecting to a local Proton Mail Bridge instance. It allows users to list, search, read, send, and organize emails using natural language commands.

mcp-google-gdrive

An MCP server that enables AI assistants to list, read, create, and manage files in Google Drive. It features automatic conversion of Google Workspace formats into Markdown, CSV, and plain text for seamless integration with AI workflows.

Storyden

A modern community hub with forum and knowledge base. Native MCP built-in, ready for the next era of internet culture.

Coolify MCP Server

Enables AI assistants to interact with Coolify self-hosted instances for application deployment, management, and monitoring. Features 4 unified tools optimized for VS Code's limits, covering app management, environment configuration, system administration, and built-in documentation.

ASCIIFlow MCP Server

Exposes ASCIIFlow drawing primitives as tools to enable AI assistants to generate ASCII wireframes and diagrams from natural language descriptions. It provides commands for creating canvases and drawing boxes, lines, arrows, and text using a character-grid coordinate system.

mcp-test

just a test

mcp-spacefrontiers

Cari di data cendekiawan dan jaringan sosial

Memory Server with Qdrant Persistence

Memfasilitasi representasi knowledge graph dengan pencarian semantik menggunakan Qdrant, mendukung embedding OpenAI untuk kesamaan semantik dan integrasi HTTPS yang kuat dengan persistensi graph berbasis file.

Serveur MCP Airbnb

Cermin dari

authorize-net-mcp

Server MCP TypeScript Node.js Authorize.net Eksperimental

RhinoMCP

Menghubungkan Rhino3D ke Claude AI melalui Model Context Protocol, memungkinkan alur kerja pemodelan dan desain 3D yang dibantu AI melalui kontrol langsung atas fungsionalitas Rhino.

research-hub

AI-operable research workspace integrating Zotero, Obsidian, and NotebookLM. Search papers (arXiv/Semantic Scholar/PubMed/CrossRef), ingest into Zotero, sync per-paper notes to Obsidian, verify NotebookLM briefs. All three external tools optional.

Materials Project Platform MCP Server

The Materials Project MCP Server is server that provides programmatic access to the Materials Project database. It enables LLMs, to search, analyze, and retrieve up to date materials science data.

Dell Isilon (PowerScale) MCP Server

Enables AI assistants to interact with Dell PowerScale (Isilon) OneFS clusters through over 2,400 tools generated from the REST API specification. It supports managing storage protocols, snapshots, networking, and cluster configurations using natural language.

dev-loop-mcp

An MCP server that automates the full software development lifecycle through an AI-driven TDD state machine. It handles everything from task decomposition and test-driven development to integration testing and automated pull request creation.

IDA-doc-hint-mcp

Pembaca dokumentasi Ida (semacam) server mcp