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.
GameCode MCP2 MCP Server
@navicore
Basic information
About GameCode MCP2 MCP Server
mcp in rust both client and server
GameCode MCP2 MCP Server config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryGameCode MCP2 MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
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.yamlare 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
Frequently asked questions
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.
More Other MCP servers
Activepieces
activepiecesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
23.2K
Figs, Relationship Expert
Figs O'Sullivan, LMFTCouples therapist Figs O'Sullivan (LMFT, 17 years, endorsed by Sue Johnson, creator of EFT) inside your AI. Ask relationship questions answered from his clinical writing, name the pattern in a fight, get a three-step rep
Handl
Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
ICSS
chokcoco不止于 CSS
20.7K
Health by Dr Brad
Dr Brad StanfieldHealth by Dr Brad works out a health plan from your own results: which screening is due at your age, and evidence-based suggestions, each with the reason and the published guideline or study behind it. Your record is one
Comments