MCP.so
ログイン

GameCode MCP2 MCP Server

@navicore

基本情報

カテゴリ

その他

トランスポート

stdio

作者

navicore

GameCode MCP2 MCP Server について

mcp in rust both client and server

#gamecode#mcp#rust

GameCode MCP2 MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

GameCode MCP2 MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is GameCode MCP2?

GameCode MCP2 is a clean implementation of the Model Context Protocol (MCP) for dynamic tool integration. It exposes tools defined in a YAML configuration file directly via MCP, supporting both built-in handlers and external commands, and communicates over stdio using pure JSON-RPC 2.0 without external dependencies.

How to use GameCode MCP2?

Compile the server with cargo build --release --bin gamecode-mcp2, create a tools.yaml file (see examples/tools.yaml), then run the server binary. It communicates via stdio and can be configured as an MCP server in Claude Desktop or integrated via the mcp-client crate.

Key features of GameCode MCP2

  • Tools defined in tools.yaml are exposed directly via MCP, not through meta-tools
  • Pure JSON-RPC 2.0 over stdio without external dependencies
  • Dynamic tool loading – configure tools via YAML without recompiling
  • Support for both internal handlers and external commands

Use cases of GameCode MCP2

  • Exposing custom command-line tools as MCP tools for AI assistants
  • Building a lightweight MCP server with minimal dependencies
  • Integrating MCP into a CLI application (gamecode-cli) via the provided client crate
  • Rapidly prototyping and testing MCP tool configurations with YAML

よくある質問

1

What runtime or dependencies are required?

The server is written in Rust and requires Cargo to build. It has no external runtime dependencies; communication is pure JSON-RPC 2.0 over stdio.

2

How are tools configured?

Tools are defined in a `tools.yaml` file. Each tool entry specifies a name, description, command (either an external executable path or `"internal"`), arguments with CLI flags or positional handling, and optionally an internal handler name.

3

How does GameCode MCP2 differ from other MCP implementations?

This implementation exposes tools directly (not through meta-tools) and supports dynamic YAML-based tool loading without recompilation, with a focus on simplicity and minimal dependencies.

4

What transport protocol does it use?

It uses stdio (standard input/output) for communication, following the MCP specification with messages such as `initialize`, `tools/list`, and `tools/call`.

5

Can I use GameCode MCP2 with Claude Desktop?

Yes. Add a configuration entry to your Claude Desktop settings pointing to the compiled `gamecode-mcp2` binary.

コメント

「その他」の他のコンテンツ