MCP Servers

Discover Awesome MCP Servers

Extend your agent with 12,344 capabilities via MCP servers.

All12,344

Swytchcode MCP server

Swytchcode 加速了 API 集成，使开发者能够使用 Postman 集合或 OpenAPI 规范无缝集成任何 API。借助 Swytchcode，开发者可以获得他们首选编程语言的、可用于生产环境的代码，从而将集成时间缩短高达 90%。 Swytchcode 平台支持为 80 多个 API 生成代码，并能够根据需求添加更多 API。这种简化的方法使开发者能够专注于创新，而不是繁琐的集成任务。主要特点： API 支持：与 80 多个 API 集成，包括 Stripe、PayPal 和 Shopify 等流行的金融科技服务。代码生成：生成多种编程语言的代码，确保与各种开发环境的兼容性。按需添加 API：允许开发者根据需要请求对其他 API 的支持。

dicom-mcp: A DICOM Model Context Protocol Server

用于与 DICOM 服务器（PACS 等）交互的模型上下文协议 (MCP)。

Database MCP Server

一个模型上下文协议服务器，它提供通过统一接口连接和交互各种数据库系统（SQLite、PostgreSQL、MySQL/MariaDB、SQL Server）的工具。

Example MCP Server + Client Implementation

一个 MCP 服务器（使用虚拟 API）和基本客户端的演示实现。

Unsplash MCP Server

一个轻量级的服务器，能够与 Unsplash 的图片库无缝集成，让开发者可以直接从 Cursor 编辑器中搜索带有各种滤镜的高质量照片。

Freqtrade-MCP

一个与 Freqtrade 加密货币交易机器人集成的 MCP 服务器。

MCP Tools

镜子 (jìng zi)

Crypto Indicators MCP Server

一个提供各种加密货币技术分析指标和策略的 MCP 服务器。

Mcp Api

MCP 客户端和服务器

Script Tool

MCP 服务器用于运行脚本。 (MCP 服务器 to for running script.)

Fillout.io MCP Server

通过 Fillout.io API 实现表单管理、响应处理和分析，以增强表单互动和洞察力。

LibreChat MCP Servers

Okay, here's a translation of instructions for setting up SuperGateway MCP servers in Docker containers for Docker deployments of LibreChat: **Title: 为 LibreChat Docker 部署设置 Docker 容器中的 SuperGateway MCP 服务器** **Instructions:** This document outlines the steps to set up SuperGateway MCP (Message Control Plane) servers within Docker containers for your LibreChat Docker deployment. This setup allows for improved message routing and management within your LibreChat instance. **步骤 (Bùzhòu - Steps):** 1. **准备 Docker Compose 文件 (Zhǔnbèi Docker Compose Wénjiàn - Prepare the Docker Compose File):** * You will need to modify your existing `docker-compose.yml` file (or create a new one if you don't have one yet). Add a new service definition for each MCP server you want to run. Here's an example: ```yaml version: "3.9" # Or your preferred Docker Compose version services: # ... (Your existing LibreChat services) ... mcp1: image: ghcr.io/daveshapautomator/supergateway:latest # Use the SuperGateway image container_name: mcp1 restart: unless-stopped ports: - "3001:3000" # Map the port (adjust as needed) environment: - NODE_ENV=production - PORT=3000 - MCP_NAME=mcp1 # Unique name for this MCP instance - REDIS_HOST=your_redis_host # Replace with your Redis host - REDIS_PORT=6379 # Replace with your Redis port (default is 6379) - REDIS_PASSWORD=your_redis_password # Replace with your Redis password (if any) - LOG_LEVEL=info # Adjust log level as needed (debug, info, warn, error) # Add any other necessary environment variables for SuperGateway mcp2: image: ghcr.io/daveshapautomator/supergateway:latest container_name: mcp2 restart: unless-stopped ports: - "3002:3000" # Map the port (adjust as needed) environment: - NODE_ENV=production - PORT=3000 - MCP_NAME=mcp2 # Unique name for this MCP instance - REDIS_HOST=your_redis_host # Replace with your Redis host - REDIS_PORT=6379 # Replace with your Redis port (default is 6379) - REDIS_PASSWORD=your_redis_password # Replace with your Redis password (if any) - LOG_LEVEL=info # Adjust log level as needed (debug, info, warn, error) # Add any other necessary environment variables for SuperGateway ``` * **Explanation:** * `version`: Specifies the Docker Compose file version. * `services`: Defines the services to be run. * `mcp1`, `mcp2`: Service names for each MCP instance. Choose descriptive names. * `image`: Specifies the Docker image to use. Use the official SuperGateway image. * `container_name`: Sets the name of the Docker container. * `restart: unless-stopped`: Ensures the container restarts automatically unless explicitly stopped. * `ports`: Maps the container's port (3000 in this example) to a port on the host machine. Make sure these ports are available on your host. **Important:** Each MCP instance needs a *unique* host port. * `environment`: Sets environment variables for the MCP server. **Crucially, you must configure the `REDIS_HOST`, `REDIS_PORT`, and `REDIS_PASSWORD` to match your Redis instance used by LibreChat.** `MCP_NAME` should be unique for each MCP instance. 2. **配置环境变量 (Pèizhì Huánjìng Biànliàng - Configure Environment Variables):** * **`NODE_ENV`**: Set to `production` for a production environment. * **`PORT`**: The port the SuperGateway server listens on *inside* the container. Generally, leave this at `3000`. * **`MCP_NAME`**: A unique name for each MCP instance. This is important for identification and routing. * **`REDIS_HOST`**: The hostname or IP address of your Redis server. This is *critical* for SuperGateway to communicate with Redis. * **`REDIS_PORT`**: The port number of your Redis server (usually 6379). * **`REDIS_PASSWORD`**: The password for your Redis server (if you have one). * **`LOG_LEVEL`**: Controls the verbosity of the logs. Options include `debug`, `info`, `warn`, and `error`. * **Other SuperGateway Configuration**: Consult the SuperGateway documentation for other configurable environment variables. You may need to configure things like API keys or other settings specific to your use case. 3. **启动 Docker Compose (Qǐdòng Docker Compose - Start Docker Compose):** * Navigate to the directory containing your `docker-compose.yml` file in your terminal. * Run the following command to start the services: ```bash docker-compose up -d ``` * `docker-compose up`: Starts the services defined in the `docker-compose.yml` file. * `-d`: Runs the services in detached mode (in the background). 4. **验证 (Yànzhèng - Verification):** * Check the logs of the MCP containers to ensure they started successfully and are connecting to Redis. You can use the following command: ```bash docker logs mcp1 docker logs mcp2 ``` Replace `mcp1` and `mcp2` with the actual names of your MCP containers. Look for any error messages. * Verify that you can access the MCP servers through the ports you mapped in the `docker-compose.yml` file (e.g., `http://your_server_ip:3001`). You might need to configure your firewall to allow access to these ports. The SuperGateway server may have a health check endpoint you can use. 5. **配置 LibreChat (Pèizhì LibreChat - Configure LibreChat):** * You will need to configure LibreChat to use the SuperGateway MCP servers. This typically involves setting environment variables within your LibreChat Docker container. Consult the LibreChat documentation for the specific environment variables required to configure SuperGateway integration. These variables will likely include the addresses (host and port) of your MCP servers. For example: ``` SUPERGATEWAY_URLS=http://your_server_ip:3001,http://your_server_ip:3002 ``` (This is just an example; the actual variable name and format may differ.) * Restart your LibreChat container after making these configuration changes. **重要提示 (Zhòngyào Tíshì - Important Notes):** * **Redis Configuration:** Double-check your Redis configuration. Incorrect Redis settings are a common cause of problems. * **Port Conflicts:** Ensure that the ports you are mapping in your `docker-compose.yml` file are not already in use on your host machine. * **Firewall:** Make sure your firewall allows traffic to the ports you are using for the MCP servers. * **SuperGateway Documentation:** Refer to the official SuperGateway documentation for the most up-to-date information and configuration options. * **LibreChat Documentation:** Refer to the official LibreChat documentation for instructions on how to integrate with SuperGateway. * **Scaling:** You can add more MCP servers by adding more service definitions to your `docker-compose.yml` file. Remember to give each server a unique name and port. * **Security:** Consider security implications, especially if your Redis server is exposed to the internet. Use strong passwords and consider using TLS encryption for Redis connections. This translation provides a comprehensive guide to setting up SuperGateway MCP servers in Docker containers for LibreChat. Remember to consult the official documentation for both SuperGateway and LibreChat for the most accurate and up-to-date information. Good luck!

Creating an MCP Server in Go and Serving it with Docker (part 2)

CF-MCP-Server

Venice AI Image Generator MCP Server

测试 MCP 服务器功能，威尼斯和双子座（图像）。

Deno 2 Playwright Model Context Protocol Server Example

镜子 (jìng zi)

Gemini Flash MCP - Image Generation for Roo Code

用于 Google Gemini 2.0 Flash 图像生成的 MCP 服务器

MCP-Agg: Multi-Channel Platform Aggregator

聚合 MCP 服务器 (Jùhé MCP fúwùqì)

MCP Harbor

一个 Node.js 应用程序，提供模型上下文协议 (Model Context Protocol) 服务器，用于与 Harbor 容器镜像仓库交互，支持项目、仓库、标签和 Helm Chart 的操作。

mcp-excel

MCP 服务器赋予客户端读取 Excel 文件的能力。

MCP (Model Context Protocol) Research

Okay, here's a translation of "Research and documentation about Model Context Protocol (MCP) servers and implementations" into Chinese, along with some nuances and considerations: **Option 1 (More Literal, General):** * **中文:** 模型上下文协议 (MCP) 服务器及其实现的调研和文档 * **Pinyin:** Móxíng shàngxiàwén xiéyì (MCP) fúwùqì jí qí shíxiàn de diàoyán hé wéndàng * **Explanation:** * "模型上下文协议 (MCP)" - Direct translation of "Model Context Protocol (MCP)". Using the acronym in parentheses is helpful for recognition. * "服务器" - "Server" * "及其实现" - "and its implementations" * "调研" - "Research" (formal, academic) * "和文档" - "and documentation" **Option 2 (More Emphasis on Technical Investigation):** * **中文:** 模型上下文协议 (MCP) 服务器及其实现的深入研究与技术文档 * **Pinyin:** Móxíng shàngxiàwén xiéyì (MCP) fúwùqì jí qí shíxiàn de shēnrù yánjiū yǔ jìshù wéndàng * **Explanation:** * "深入研究" - "In-depth research" or "Thorough investigation". This emphasizes a more detailed and technical approach. * "技术文档" - "Technical documentation". This clarifies the type of documentation. **Option 3 (More Concise, Practical):** * **中文:** 模型上下文协议 (MCP) 服务器实现及文档 * **Pinyin:** Móxíng shàngxiàwén xiéyì (MCP) fúwùqì shíxiàn jí wéndàng * **Explanation:** * This is a shorter, more direct translation. It implies that the research is focused on the *implementation* aspects. * "实现" - "Implementation" **Which option is best depends on the context:** * If you're talking about academic research, Option 1 or 2 is better. * If you're talking about practical development and implementation, Option 3 might be more suitable. * If you want to emphasize the technical nature of the documentation, Option 2 is a good choice. **Important Considerations for Chinese Translation of Technical Terms:** * **Consistency:** Once you choose a translation for "Model Context Protocol" (or any other technical term), stick with it throughout your documentation. * **Acronyms:** Including the English acronym (MCP) in parentheses is generally a good practice, especially the first time you use the term. This helps readers who are familiar with the English term. * **Target Audience:** Consider your target audience. Are they primarily Chinese speakers with limited English, or are they bilingual? This will influence how much you need to explain the English terms. * **Context is Key:** The best translation always depends on the specific context in which the phrase is used. I hope this helps! Let me know if you have any other questions.

Goose FM

好的，这是将“MVP of an MCP server that lets ai assistants tune into fm stations”翻译成中文的几种选择，根据不同的侧重点： **选项 1 (偏技术，强调最小可行产品):** > 一个最小可行产品 (MVP) 的 MCP 服务器，允许 AI 助手收听 FM 广播电台。 **选项 2 (更简洁，更通用):** > 一个 MCP 服务器的 MVP，使 AI 助手能够调频收音。 **选项 3 (更口语化，更易理解):** > 一个 MCP 服务器的 MVP 版本，可以让 AI 助手收听 FM 广播。 **选项 4 (强调功能):** > 一个 MCP 服务器的 MVP，其功能是让 AI 助手收听 FM 电台。 **解释:** * **MVP (Minimum Viable Product):** 最小可行产品，指用最少的功能来验证产品概念。 * **MCP Server:** MCP 服务器，具体指什么需要根据上下文判断，可能是一个特定的协议或平台。 * **AI Assistants:** AI 助手，例如 Siri, Alexa, Google Assistant 等。 * **FM Stations:** FM 广播电台。选择哪个翻译取决于你希望强调的方面。如果需要更精确的翻译，请提供更多关于 MCP 服务器的背景信息。