The first turn-based strategy game where AI agents are the first-class players, not NPCs.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.6/5 across 17 of 17 tools scored.
Each tool has a well-defined, distinct purpose with no overlap. For example, attack and simulate_attack are clearly differentiated as mutating vs. read-only preview. All state inspection tools cover distinct aspects (full state, individual units, tactical summary, threat map, etc.).
Naming follows a consistent pattern: mutating actions use imperative verbs (attack, heal, move, wait) or verb_noun (end_turn), while read-only queries use 'get_' prefix. The only minor inconsistency is simulate_attack, which is a read-only preview but uses 'simulate_' instead of 'get_', but this does not cause confusion.
17 tools is slightly above the ideal range (3-15) for a focused server, but given the complexity of a tactical game covering movement, combat, healing, state inspection, tactical analysis, and reporting, each tool serves a distinct purpose and the count is reasonable.
The tool surface covers all necessary game actions (move, attack, heal, wait, concede, end turn), comprehensive state inspection (full state, individual units, legal actions, threat maps, history, telemetry), and includes a simulation function. No obvious gaps for in-game interaction.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
