GameCode MCP2

@navicore

Repository

About GameCode MCP2

mcp in rust both client and server

#gamecode #mcp #rust

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

FAQ from GameCode MCP2

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.

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.

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.

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.

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.

Frequently asked questions