Discover Awesome MCP Servers
Extend your agent with 84,517 capabilities via MCP servers.
- All84,517
- 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
BPE MCP Server
Enables querying consolidated Bitcoin pricing, ML signals, funding skew, and market briefings via the BPE API, without HTTP boilerplate.
FFmpeg-MCP Server
An MCP server providing video processing capabilities through FFmpeg, enabling dialog-based local video search, trimming, concatenation, and playback functionalities.
a207-followup-mcp
MCP server for pediatric CKD follow-up management, providing tools to schedule follow-ups based on KDIGO 2024 guidelines, retrieve follow-up records, compute adherence scores, and access PEW history.
knoten
Enables coding agents to query and commit to a research graph that remembers failed experiments, ensuring reproducibility and preventing redundant work.
Logseq Tools
This could be interpreted in a few ways, depending on what you're trying to achieve. Here are a few possible translations and explanations: **1. If you're looking for a way to host your Logseq graph on a server using MCP (Minecraft Protocol) - which is highly unlikely and probably a misunderstanding:** * **Chinese Translation:** 使用 MCP 协议为 Logseq 图谱搭建服务器 * **Pinyin:** Shǐyòng MCP xiéyì wèi Logseq túpǔ dājiàn fúwùqì * **Explanation:** This translates to "Set up a server for the Logseq graph using the MCP protocol." This is likely *not* what you want. MCP is related to Minecraft, and Logseq doesn't directly interact with Minecraft. **2. If you're looking for a *general* server solution to host your Logseq graph (e.g., for collaboration or access from multiple devices):** * **Chinese Translation:** Logseq 图谱的服务器解决方案 * **Pinyin:** Logseq túpǔ de fúwùqì jiějué fāng'àn * **Explanation:** This translates to "Server solution for Logseq graph." This is a more general and likely more accurate interpretation. You'd then need to specify *which* server solution you're interested in. Some options include: * **Self-hosting (e.g., using Git, Nextcloud, or a dedicated server):** 自托管 (zì tuōguǎn) * **Using a cloud service (e.g., GitHub, GitLab, or a dedicated Logseq hosting service if one exists):** 使用云服务 (shǐyòng yún fúwù) **3. If you're looking for a way to *manage* your Logseq graph using a server (e.g., for version control or backups):** * **Chinese Translation:** 使用服务器管理 Logseq 图谱 * **Pinyin:** Shǐyòng fúwùqì guǎnlǐ Logseq túpǔ * **Explanation:** This translates to "Manage Logseq graph using a server." This is also a plausible interpretation, and often involves using Git. **Therefore, to give you the *best* translation, I need more context. Please tell me:** * **What are you trying to *achieve* by using a server with your Logseq graph?** (e.g., collaboration, access from multiple devices, backups, version control) * **What do you mean by "MCP"?** Are you sure you're using the correct term? Once I have this information, I can provide a much more accurate and helpful translation.
Supabase MCP Server
Connects Supabase projects to AI assistants, enabling them to manage database tables, execute SQL queries, and deploy Edge Functions through natural language. It provides a comprehensive suite of tools for project administration, including logs access, documentation search, and environment configuration.
Taiwan Government Open Data MCP Server
Enables searching and querying Taiwan government open datasets from data.gov.tw using AI-powered search through Cloudflare Workers.
burn-mcp-server
AI-powered reading triage MCP. 26 tools with a 24h burn timer — search, triage, burn, vault, and analyze your saved articles. Works with Claude, Cursor, Windsurf. Stdio + HTTPS transports.
Oura Ring MCP Server
A Python-based Model Context Protocol server that provides AI assistants with access to Oura Ring health and fitness data across 15+ endpoints. It enables querying metrics like sleep, activity, readiness, and cardiovascular health through simple authentication and date-range filtering.
io.github.oxgeneral/agentmem
Lightweight persistent memory for AI agents using a single SQLite file with hybrid search (keywords + semantics). Zero to 12MB install, no cloud or server required.
Valkama
A local MCP server with a web board that lets coding agents manage kanban cards, checklists, and work tracking through 30 MCP tools, with live updates and session tracking.
Excel MCP Server
Enables AI assistants to perform comprehensive Microsoft Excel operations including data analysis, cell editing, advanced formatting, and VBA execution on Windows systems. It provides a structured workflow for managing workbooks and worksheets through a dedicated Model Context Protocol interface.
tsb-kasko-mcp
Enables querying Türkiye Sigorta Birliği’s Kasko Değer Listesi (vehicle insurance valuation list) through MCP, CLI, and Python, allowing natural language lookup of current and historical vehicle insurance values.
easyhire-jobs
Read-only MCP server for the public EasyHire job board. Enables searching job openings, retrieving full postings, filtering by criteria, and listing countries with open roles.
jorkal-nft-mcp
MCP server for Solana NFT market data via Magic Eden. Paid with x402 USDC micropayments.
academic-assistant
MCP server that integrates GitHub, Brightspace, Outlook, and local files, enabling natural language queries for assignments, grades, emails, calendar events, repositories, and file operations.
cy-excel-mcp
Parses WeChat order messages, merges follow-up updates, and writes structured orders into a OneDrive Excel workbook through Microsoft Graph.
Azure Cosmos DB MCP Server
以下是将英文翻译成中文: 基于 Node.js 的服务器,连接到 Azure Cosmos DB NoSQL 数据库,允许用户通过 NextJS 前端应用程序中的 AI 助手查询产品和订单。 Here's a slightly more nuanced translation, offering a bit more context: 一个使用 Node.js 构建的服务器,它连接到 Azure Cosmos DB NoSQL 数据库,并允许用户通过 NextJS 前端应用中的 AI 助手来查询产品和订单信息。 **Explanation of differences and why the second option might be preferred:** * **"基于" (jī yú) vs. "使用" (shǐ yòng):** While both mean "based on" or "using," "使用" (shǐ yòng) is often preferred when referring to technology or tools. It emphasizes the *use* of Node.js rather than just its foundation. * **"信息" (xìn xī):** Adding "信息" (information) after "产品和订单" (products and orders) clarifies that the user is querying *information* about these items. It's a subtle addition that improves clarity. * **"构建" (gòu jiàn):** Using "构建" (build) instead of just implying it is more accurate. Ultimately, the best translation depends on the specific context and the desired level of detail. Both are accurate, but the second option is slightly more descriptive.
Lathe
Local MCP server that shapes tailored resume PDFs with live browser preview.
Oracle Database MCP Server
A production-grade MCP server for Oracle database interaction, providing 11 tools for full CRUD, transactions, execution plans, and comprehensive safety guardrails.
BrixUI MCP Server
An MCP server that connects AI clients to Figma components, design tokens, and variables from the BrixUI Design System, enabling component browsing, searching, and token retrieval.
@bdelanghe/site-mcp
A local, read-only MCP server that exposes verified profile, posts, corpus, and other identity data from robertdelanghe.dev's signed static API.
llm-toolkit
MCP server toolkit with payload library, WAF bypass generator, rate limiter, plugin system, and inter-MCP bridge for security testing.
MCP-Demo
mcp-regulations-gov
Enables access to federal regulatory dockets, documents, and public comments from Regulations.gov via tools like get_docket and get_comment.
mcp-relay-kit
A unified MCP gateway that reduces context token usage by exposing all services through just two tools (search and execute), supporting built-in services like Asana and Sentry as well as proxied external MCP servers.
recibosplit
Read-only MCP server for querying group expense splits and balances from a self-hosted receipt splitting app.
qdrant-mcp-local
以下は、ローカル環境でQdrantとMCP-server-qdrantを簡単に立ち上げるためのDocker Compose設定です。 ```yaml version: "3.9" services: qdrant: image: qdrant/qdrant:latest ports: - "6333:6333" - "6334:6334" volumes: - qdrant_data:/qdrant/storage restart: unless-stopped mcp-server-qdrant: image: your-mcp-server-qdrant-image:latest # ここにあなたのMCP-server-qdrantのイメージ名を指定してください ports: - "8000:8000" # 例:MCP-server-qdrantが8000番ポートで動作する場合 environment: QDRANT_HOST: qdrant QDRANT_PORT: 6333 # その他のMCP-server-qdrantに必要な環境変数を設定 depends_on: - qdrant restart: unless-stopped volumes: qdrant_data: ``` **説明:** * **`version: "3.9"`**: Docker Composeファイルのバージョンを指定します。 * **`services`**: 起動するサービスを定義します。 * **`qdrant`**: Qdrantのサービス定義です。 * **`image: qdrant/qdrant:latest`**: 最新のQdrantイメージを使用します。 * **`ports`**: ホストマシンのポートとコンテナのポートをマッピングします。 * `6333:6333`: QdrantのgRPCポートをマッピングします。 * `6334:6334`: QdrantのHTTPポートをマッピングします。 * **`volumes`**: データを永続化するために、ホストマシンのボリュームとコンテナ内のディレクトリをマッピングします。 * `qdrant_data:/qdrant/storage`: Qdrantのデータを`qdrant_data`ボリュームに保存します。 * **`restart: unless-stopped`**: コンテナが停止した場合、自動的に再起動します。ただし、手動で停止した場合は再起動しません。 * **`mcp-server-qdrant`**: MCP-server-qdrantのサービス定義です。 * **`image: your-mcp-server-qdrant-image:latest`**: **ここにあなたのMCP-server-qdrantのDockerイメージ名を指定してください。** * **`ports`**: ホストマシンのポートとコンテナのポートをマッピングします。 * `8000:8000`: MCP-server-qdrantが8000番ポートで動作する場合の例です。必要に応じて変更してください。 * **`environment`**: MCP-server-qdrantに必要な環境変数を設定します。 * `QDRANT_HOST: qdrant`: Qdrantのホスト名を`qdrant`に設定します。Docker Composeはサービス名をホスト名として解決します。 * `QDRANT_PORT: 6333`: QdrantのgRPCポートを6333に設定します。 * **その他の環境変数**: MCP-server-qdrantに必要なその他の環境変数を設定してください。例えば、APIキーや認証情報などです。 * **`depends_on`**: `qdrant`サービスが起動してから`mcp-server-qdrant`サービスを起動するように依存関係を設定します。 * **`restart: unless-stopped`**: コンテナが停止した場合、自動的に再起動します。ただし、手動で停止した場合は再起動しません。 * **`volumes`**: ボリュームを定義します。 * **`qdrant_data`**: Qdrantのデータを保存するためのボリュームです。 **使い方:** 1. 上記のYAMLコードを`docker-compose.yml`という名前で保存します。 2. `your-mcp-server-qdrant-image:latest`をあなたのMCP-server-qdrantのDockerイメージ名に置き換えてください。 3. MCP-server-qdrantに必要な環境変数を`environment`セクションに追加してください。 4. ターミナルで`docker-compose.yml`ファイルがあるディレクトリに移動し、次のコマンドを実行します。 ```bash docker-compose up -d ``` これにより、QdrantとMCP-server-qdrantがバックグラウンドで起動します。 5. サービスが起動していることを確認するには、次のコマンドを実行します。 ```bash docker-compose ps ``` **注意点:** * この設定は、ローカル環境での開発およびテストを目的としています。本番環境で使用する場合は、セキュリティやパフォーマンスに関する考慮事項を追加する必要があります。 * `your-mcp-server-qdrant-image:latest`をあなたのMCP-server-qdrantのDockerイメージ名に置き換えることを忘れないでください。 * MCP-server-qdrantに必要な環境変数を`environment`セクションに追加してください。 * 必要に応じて、ポートマッピングやボリュームマッピングを調整してください。 **中国語訳:** 以下是一个用于在本地环境中轻松启动 Qdrant 和 MCP-server-qdrant 的 Docker Compose 配置: ```yaml version: "3.9" services: qdrant: image: qdrant/qdrant:latest ports: - "6333:6333" - "6334:6334" volumes: - qdrant_data:/qdrant/storage restart: unless-stopped mcp-server-qdrant: image: your-mcp-server-qdrant-image:latest # 请在此处指定您的 MCP-server-qdrant 镜像名称 ports: - "8000:8000" # 示例:如果 MCP-server-qdrant 在 8000 端口上运行 environment: QDRANT_HOST: qdrant QDRANT_PORT: 6333 # 设置 MCP-server-qdrant 所需的其他环境变量 depends_on: - qdrant restart: unless-stopped volumes: qdrant_data: ``` **说明:** * **`version: "3.9"`**: 指定 Docker Compose 文件的版本。 * **`services`**: 定义要启动的服务。 * **`qdrant`**: Qdrant 的服务定义。 * **`image: qdrant/qdrant:latest`**: 使用最新的 Qdrant 镜像。 * **`ports`**: 将主机端口映射到容器端口。 * `6333:6333`: 映射 Qdrant 的 gRPC 端口。 * `6334:6334`: 映射 Qdrant 的 HTTP 端口。 * **`volumes`**: 为了持久化数据,将主机卷映射到容器内的目录。 * `qdrant_data:/qdrant/storage`: 将 Qdrant 数据保存到 `qdrant_data` 卷中。 * **`restart: unless-stopped`**: 如果容器停止,则自动重启。但是,如果手动停止,则不会重启。 * **`mcp-server-qdrant`**: MCP-server-qdrant 的服务定义。 * **`image: your-mcp-server-qdrant-image:latest`**: **请在此处指定您的 MCP-server-qdrant 的 Docker 镜像名称。** * **`ports`**: 将主机端口映射到容器端口。 * `8000:8000`: 如果 MCP-server-qdrant 在 8000 端口上运行,这是一个示例。根据需要进行更改。 * **`environment`**: 设置 MCP-server-qdrant 所需的环境变量。 * `QDRANT_HOST: qdrant`: 将 Qdrant 的主机名设置为 `qdrant`。 Docker Compose 将服务名称解析为主机名。 * `QDRANT_PORT: 6333`: 将 Qdrant 的 gRPC 端口设置为 6333。 * **其他环境变量**: 设置 MCP-server-qdrant 所需的其他环境变量。例如,API 密钥或凭据。 * **`depends_on`**: 设置依赖关系,以便在 `qdrant` 服务启动后启动 `mcp-server-qdrant` 服务。 * **`restart: unless-stopped`**: 如果容器停止,则自动重启。但是,如果手动停止,则不会重启。 * **`volumes`**: 定义卷。 * **`qdrant_data`**: 用于存储 Qdrant 数据的卷。 **用法:** 1. 将上述 YAML 代码保存为 `docker-compose.yml`。 2. 将 `your-mcp-server-qdrant-image:latest` 替换为您的 MCP-server-qdrant 的 Docker 镜像名称。 3. 将 MCP-server-qdrant 所需的环境变量添加到 `environment` 部分。 4. 在终端中,导航到包含 `docker-compose.yml` 文件的目录,然后运行以下命令: ```bash docker-compose up -d ``` 这将启动 Qdrant 和 MCP-server-qdrant 在后台运行。 5. 要验证服务是否正在运行,请运行以下命令: ```bash docker-compose ps ``` **注意事项:** * 此配置旨在用于本地环境中的开发和测试。 如果在生产环境中使用,则需要添加有关安全性和性能的注意事项。 * 不要忘记将 `your-mcp-server-qdrant-image:latest` 替换为您的 MCP-server-qdrant 的 Docker 镜像名称。 * 将 MCP-server-qdrant 所需的环境变量添加到 `environment` 部分。 * 根据需要调整端口映射和卷映射。
Stripe Connect MCP Server
Read-only access to Stripe data including customers, charges, subscriptions, balance, and invoices.
RCSB PDB MCP Server
Provides tools to query, retrieve, and download protein structure data from the RCSB Protein Data Bank via the MCP protocol.