MCP Servers

Discover Awesome MCP Servers

Extend your agent with 20,472 capabilities via MCP servers.

All20,472

Smithery CLI

Smithery CLI MCPサーバーインストーラー

mcp-servers-kurtseifried

鏡 (Kagami)

MCP Server-Client Example

鏡 (Kagami)

GitHub MCP Server

GitHub用のModel Context Protocol (MCP) サーバー (mcp-goベース)

Model Context Protocol and Fireproof Demo: JSON Document Collection Server

鏡 (Kagami)

Slack Mcp Bot Integration

WIP: Slack用簡易MCP (Model Context Protocol) サーバーの例

Template project to build MCP server using SpringBoot

MCP Server

鏡 (Kagami)

MCP Radarr and Sonarr Server

RadarrとSonarrサービスのMCPサーバー

Browserbase MCP Server

このサーバーは、Browserbase、Puppeteer、Stagehandを使用して、クラウドブラウザの自動化機能を提供します。このサーバーにより、LLMはウェブページとインタラクトしたり、スクリーンショットを撮ったり、クラウドブラウザ環境でJavaScriptを実行したりすることができます。

LLM Chat Replay

あなた自身のLLMに保存されたセッション用のチャットリプレイビジュアライザー。あなたのLLM + MCPファイルシステムサーバーを使ってトランスクリプトを作成し、ここで再生して、他の人と共有できるようにします。

MCP Servers Schemas

鏡 (Kagami)

MCP Demo Project

MCPサーバーの機能を紹介するためのデモリポジトリ

McpDotNet

.NET 向けの MCP クライアントおよびサーバー実装

Linux Command MCP (Model Context Protocol)

Linux コマンドを実行するための MCP サーバーとクライアント

CrateDocs MCP

Rust クレートのドキュメント用の MCP サーバー

The Pensieve MCP Server

頭の中から余分な思考を吸い出し、それを洗面器に注ぎ込み、ゆっくりと吟味するだけです。そうすると、思考がこの形になっていると、パターンや繋がりを見つけやすくなるのです、分かりますか？

AutoMCP

指定された YAML スキーマに基づいて、MCP サーバーおよびクライアントのコードを自動生成するためのライブラリ

Weekly Report Checker MCP Server

Googleスプレッドシート上の週報提出状況を監視・分析し、未提出者の確認、統計情報の表示、個人の報告状況の追跡を可能にするMCPサーバー。

SingleStore MCP Server

鏡 (Kagami)

tRPC <-> MCP

Okay, I understand. You want to use tRPC routes to serve as an MCP (Minecraft Protocol) server. This is a somewhat unusual request, as tRPC is designed for type-safe APIs, typically used for web applications, while the Minecraft Protocol is a binary protocol used for communication between Minecraft clients and servers. Here's a breakdown of why this is challenging, and some potential approaches (though none are ideal): **Why This is Difficult (and Probably Not a Good Idea):** * **Different Protocols:** tRPC uses HTTP/HTTPS and typically JSON for data transfer. The Minecraft Protocol is a custom binary protocol. You can't directly "serve" the Minecraft Protocol over tRPC. They are fundamentally incompatible. * **Binary vs. Text:** tRPC deals with text-based data (JSON). The Minecraft Protocol is binary, requiring you to pack and unpack data in specific formats (e.g., using VarInts, strings with length prefixes, etc.). * **State Management:** Minecraft servers are inherently stateful. They need to track player positions, inventories, world data, etc. tRPC is generally designed for stateless requests. You'd have to implement complex state management on top of tRPC, which is not its intended use. * **Performance:** tRPC adds overhead compared to a direct socket connection. Minecraft servers need to be highly performant to handle many players simultaneously. Using tRPC as an intermediary would likely introduce significant latency. * **Complexity:** You'd essentially be building a translation layer between the Minecraft Protocol and tRPC. This would be a complex and error-prone undertaking. **Potential (But Not Recommended) Approaches:** If you *absolutely* need to use tRPC for some reason (e.g., for authentication or some other pre-processing), here's how you *might* approach it, but be warned that this is likely to be very difficult and inefficient: 1. **tRPC as a Proxy/Gateway:** * **Minecraft Client -> tRPC Endpoint -> Minecraft Server:** The Minecraft client would *not* directly connect to the Minecraft server. Instead: * The client would send a request to a tRPC endpoint. This request would need to contain all the data necessary for a specific Minecraft Protocol packet, encoded in a way that tRPC can handle (e.g., as a JSON string or a base64 encoded binary string). * The tRPC endpoint would: * Decode the data from the tRPC request. * Construct the appropriate Minecraft Protocol packet. * Forward the packet to a *real* Minecraft server. * Receive the response from the Minecraft server. * Encode the response into a format suitable for tRPC (e.g., JSON or base64). * Send the response back to the client via tRPC. * **Example (Highly Simplified):** * **Minecraft Client (wants to send a chat message):** * Client encodes the chat message into a Minecraft Protocol packet (e.g., `0x03 <length> <message>`). * Client base64 encodes the packet: `base64Encode("0x03 <length> <message>")` * Client sends a tRPC request to `/minecraft/chat` with the base64 encoded packet as the payload. * **tRPC Server (`/minecraft/chat` endpoint):** * Decodes the base64 encoded packet. * Sends the decoded packet to the real Minecraft server. * Receives the response from the Minecraft server (if any). * Encodes the response (if any) into JSON or base64. * Sends the encoded response back to the client. 2. **Custom Minecraft Client/Proxy:** * You'd need to write a custom Minecraft client or a proxy that sits between the official client and the tRPC server. This client/proxy would: * Intercept Minecraft Protocol packets. * Convert them into tRPC requests. * Send the requests to the tRPC server. * Receive responses from the tRPC server. * Convert the responses back into Minecraft Protocol packets. * Forward the packets to the official Minecraft client or the real Minecraft server. **Code Example (Illustrative and Incomplete - TypeScript):** ```typescript import { initTRPC } from '@trpc/server'; import { z } from 'zod'; import { base64Encode, base64Decode } from './base64'; // Implement these const t = initTRPC.create(); const router = t.router({ minecraftChat: t.procedure .input(z.object({ packet: z.string() })) // Expects base64 encoded packet .mutation(async ({ input }) => { try { const decodedPacket = base64Decode(input.packet); // **IMPORTANT:** Replace this with your actual Minecraft server connection logic // This is just a placeholder! const minecraftServerResponse = await sendToMinecraftServer(decodedPacket); const encodedResponse = base64Encode(minecraftServerResponse); return { response: encodedResponse }; } catch (error) { console.error("Error processing Minecraft chat:", error); throw new Error("Failed to process Minecraft chat"); } }), }); export type AppRouter = typeof router; // Placeholder function - you need to implement this! async function sendToMinecraftServer(packet: Uint8Array): Promise<Uint8Array> { // This is where you'd establish a socket connection to your Minecraft server // and send the packet. You'd also need to handle the response. console.log("Sending packet to Minecraft server:", packet); // Simulate a response return new Uint8Array([0x00, 0x01, 0x02]); // Example response } ``` **Important Considerations:** * **Security:** Be extremely careful about security. You're exposing your Minecraft server to potential vulnerabilities through the tRPC layer. Validate all data rigorously. * **Error Handling:** Implement robust error handling to gracefully handle invalid packets or server errors. * **Performance Testing:** Thoroughly test the performance of your solution to ensure it can handle the expected load. * **Minecraft Protocol Documentation:** You'll need to have a deep understanding of the Minecraft Protocol. Refer to the official documentation (if available) or community resources. * **Libraries:** Consider using libraries that help with Minecraft Protocol encoding/decoding (e.g., `prismarine-protocol` in JavaScript/TypeScript). **In Summary:** While technically possible, using tRPC as a direct MCP server is highly discouraged due to the fundamental differences between the protocols, the added complexity, and the potential performance issues. A more traditional Minecraft server implementation using a dedicated library and socket connections is almost always the better approach. If you *must* use tRPC, treat it as a proxy/gateway and be prepared for a significant amount of work. Carefully consider the security implications.

MCP GitLab Review Server

GitLab でレビュー用の MCP (Minecraft Protocol) サーバーを構築する、ということですね。より正確な翻訳と、もしあれば具体的な状況に合わせたアドバイスをするために、もう少し詳しく教えていただけますでしょうか？例えば、以下のような情報があると助かります。 * **「レビュー用」とは具体的に何を指しますか？** 例えば、開発中の変更をテストするため、特定のブランチのコードを試すため、など。 * **MCP Server とは何ですか？** Minecraft Protocol Server のことでしょうか？もしそうであれば、どのような目的で使用しますか？ * **GitLab をどのように利用していますか？** CI/CD パイプラインを使用していますか？ * **どのような環境に構築したいですか？** ローカル環境、クラウド環境（AWS, GCP, Azure など）、オンプレミス環境など。これらの情報があると、より的確な翻訳とアドバイスができます。とりあえず、現時点での翻訳としては、以下のようなものが考えられます。 * **レビュー用 MCP サーバーを GitLab で構築する:** GitLab でレビュー用の MCP サーバーを構築する * **GitLab を使ってレビュー用の MCP サーバーを立てる:** GitLab を使ってレビュー用の MCP サーバーを立てるもし、GitLab CI/CD を使って自動的に MCP サーバーを構築・デプロイしたい、というような状況であれば、以下のような表現も考えられます。 * **GitLab CI/CD を使ってレビュー用 MCP サーバーを自動デプロイする:** GitLab CI/CD を使ってレビュー用 MCP サーバーを自動デプロイするより詳しい情報をお待ちしています。