Skip to main content
Glama

ttt-mcp — Tic-Tac-Toe MCP Server

A minimal MCP server exposing a tic-tac-toe game as tools, intended to be played by Claude (via Claude Desktop) against a human via chat.

Tools exposed

  • new_game — reset to empty board, X to move

  • get_state — return current board + status

  • make_move(row, col) — place the current player's mark; server alternates turns

Related MCP server: Tic-Tac-Toe MCP Server

Setup

cd ttt-mcp
npm install
npm run build

Wire it into Claude Desktop

Edit your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add (or merge into) this:

{
  "mcpServers": {
    "tic-tac-toe": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/ttt-mcp/dist/index.js"]
    }
  }
}

Replace the path with your actual absolute path. Then fully quit and restart Claude Desktop.

Verify it loaded

In Claude Desktop, open a new chat and look for the MCP tools indicator (slider/plug icon near the input). You should see tic-tac-toe listed with three tools.

If it's missing, check Claude Desktop's MCP logs:

  • macOS: ~/Library/Logs/Claude/mcp*.log

Test outside Claude Desktop

You can poke the server directly with the official inspector:

npm run inspect

This launches a web UI that lets you call the tools manually — handy for debugging.

Playing

In Claude Desktop chat, just say: "Let's play tic-tac-toe. You start."

I'll call new_game, make a move, and we go from there. When it's your turn, tell me your move ("row 1 column 2") and I'll call make_move on your behalf, then take my own turn.

What to add next

  • Per-conversation game state (currently single global state)

  • AI difficulty levels (right now I just decide moves myself in chat)

  • Replay history / undo

  • Multiple game rooms

  • Web frontend that subscribes to state changes

Available Tools

35 tools
bs_claude_fireA

Fire the Navy cannons at the given coordinates on the pirate fleet. Claude chooses the target — reason about it in chat first, then call this. Returns hit/miss/sunk — and if sunk, reveals what the pirate ship was carrying.

Inputs: row (required), col (required).

bs_get_stateA

Get the current battle map — both attack grids and fleet status. Free, does not count as a shot.

Inputs: no named parameters.

bs_human_fireA

Fire the pirate cannons at the given coordinates on the Navy's grid. Call this when the human gives their shot. Returns hit/miss/sunk — and if sunk, reveals what that Navy ship was carrying.

Inputs: row (required), col (required).

bs_new_gameA

Start a new Battleship game: Pirates vs the Royal Navy. Both fleets are placed secretly. Each ship carries hidden cargo revealed only when sunk. Pirates fire first.

Inputs: no named parameters.

cc_catchA

Attempt to catch the creature currently encountered. Only usable when a creature has appeared during cc_explore. Catching is not guaranteed — difficulty and party bond both matter.

Inputs: no named parameters.

cc_exploreA

Search the current area for wild creatures. May trigger an encounter or a near-miss. Can be called up to 10 times per visit; the counter resets when you leave and return.

Inputs: no named parameters.

cc_moveA

Move to an adjacent area by direction. Moving resets the explore counter for the new area. Available directions are always shown in the PATHS section of the current view.

Inputs: direction (required).

cc_nameB

Give a creature in your party a new nickname.

Inputs: current_name (required), new_name (required).

cc_new_gameA

Begin a new Critter Catch adventure. Places you in Millhaven and introduces the quest.

Inputs: player_name (required).

cc_new_turnA

Reset the action counter to begin a new turn. ONLY call this after you have summarized the previous turn for the player in plain text AND received their reply. Pass their reply as player_message. Do not call this before the player has responded.

Inputs: player_message (required).

cc_partyA

View your full party — bond levels, moods, personalities, and any discovered traits.

Inputs: no named parameters.

cc_recallA

Invite a retired creature back into your party. Only available in Millhaven.

Inputs: nickname (required).

cc_releaseB

Release a creature from your party. This cannot be undone.

Inputs: nickname (required).

cc_retireA

Send a creature home to Millhaven to rest. Only available once their bond reaches 70. They are not lost — use cc_recall when you return to Millhaven to bring them back.

Inputs: nickname (required).

cc_statusA

View your current location, party summary, rare observations, and recent event log.

Inputs: no named parameters.

ms_flag_cellA

Plant or remove a warning post (P) on a square to mark a suspected mine. Flufflings won't accidentally wander into posted squares. Counts as one step.

Inputs: row (required), col (required).

ms_get_stateA

Survey the current state of the minefield. Free — does not cost a step.

Inputs: no named parameters.

ms_new_gameA

Start a new Fluffling minefield crossing. 9×9 field, 10 hidden mines. The first step is always safe — mines are placed after it. Call ms_reveal_cell to send the first scout.

Inputs: no named parameters.

ms_next_turnA

The Flufflings catch their breath and check in with the player. Resets the step counter and gives 8 fresh steps. Must be called after reaching the turn limit — chat first, then call this to continue the crossing.

Inputs: no named parameters.

ms_reveal_cellA

Send a Fluffling scout to a square at (row, col). If it's clear of nearby mines, the surrounding area cascades open automatically. Counts as one step this turn.

Inputs: row (required), col (required).

ot_buyA

Buy supplies at a trading post or fort. Only available at stops where trading is possible. Prices: food=$2/day, medicine=$6/dose, ammo=$1/round, parts=$10, oxen=$20.

Inputs: item (required), quantity (required).

ot_clear_gameA

Abandon the current journey and clear all game state. Use this to start fresh — especially useful if a stale game from a previous session is still loaded. After calling this, use ot_new_game to begin a new journey.

Inputs: no named parameters.

ot_cross_riverA

Choose how to cross the current river. Ford=fast but risky. Caulk=float the wagon, medium risk. Ferry=safe but costs $15. Wait=lose 2 days and food but calmer water. Narrate the crossing dramatically.

Inputs: method (required).

ot_huntA

Stop to hunt for food. Takes half a day, uses ammo, and the results are unpredictable. Narrate the hunt to the human.

Inputs: no named parameters.

ot_make_wishA

Make your wish at the Well at Eldenmoor. Only available after reaching the Well. The outcome is uncertain. State your wish clearly. Narrate the ending based on the outcome returned.

Inputs: wish (required).

ot_new_gameA

Begin the journey to the Well at Eldenmoor. Provide the human player's name — Claude names its own character, and a pet is assigned at random. The trail is generated fresh each run — stops, NPCs, and scenery will differ. Read the full intro to the human before asking what they want to do.

Inputs: player_name (required).

ot_restA

Make camp and rest for 1–3 days. Recovers health for everyone but costs food and time. Worth it when someone is struggling.

Inputs: days (required).

ot_sellA

Sell surplus supplies at a trading post or fort. You'll take a loss — traders know you're desperate — but cash in hand beats dead weight in the wagon. Only available where trading is possible. Ammo isn't worth selling. Sell prices: food=$1/day (buy $2), medicine=$4/dose (buy $6), parts=$6 (buy $10), oxen=$12 (buy $20). You must keep at least 1 ox.

Inputs: item (required), quantity (required).

ot_statusA

Check the current state of the journey — party health, supplies, location, and recent events. Free, no cost.

Inputs: no named parameters.

ot_travelB

Hit the trail for 3 days. Always costs food and may affect health — plan supplies before calling. Costs: easy=-6 food, +9hp each; steady=-9 food, 0hp change; hard=-12 food, -21hp each, -12hp pet. Random events add further gains/losses on top. Narrate what happens to the human dramatically.

Inputs: pace (required).

ot_use_medicineA

Use one dose of medicine on a party member. Restores significant health. Use it when someone is struggling or worse.

Inputs: target (required).

ttt_get_stateA

Get the current Tic-Tac-Toe board, status, player names, and legal moves.

Inputs: no named parameters.

ttt_make_moveA

Place the current player's mark at (row, col). Rows and columns are 0–2; top-left is row 0, col 0. The server alternates turns automatically. Returns updated board, status, and legal moves in one response.

Inputs: row (required), col (required).

ttt_new_gameA

Start a fresh Tic-Tac-Toe game. X always moves first. Optionally name the players so roles are explicit in every response.

Inputs: player_x_name, player_o_name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool is prefixed by a unique game abbreviation (bs, cc, ms, ot, ttt), making it immediately clear which game they belong to. Within each group, tools have distinct action names, so an agent can easily select the correct tool for a given game and task.

    Naming Consistency5/5

    All tools follow a consistent 'prefix_verb_noun' pattern, using snake_case throughout. For example, bs_new_game, cc_explore, ms_reveal_cell, ot_travel, ttt_make_move. There are no deviations in style or convention.

    Tool Count4/5

    With 35 tools across four distinct games, the count is on the higher side but well-justified by the complexity of each game (e.g., Oregon Trail has 12 tools, Critter Catch has 11). No tool feels superfluous, and the overall scope is appropriate for a multi-game server.

    Completeness5/5

    Each game's toolset covers the core gameplay loop comprehensively: Battleship covers firing and state; Critter Catch covers exploration, catching, and party management; Minefield covers revealing, flagging, and turns; Oregon Trail covers travel, supplies, health, and events; Tic-Tac-Toe covers moves and state. No obvious gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables two LLMs to play Tic-Tac-Toe against each other autonomously using a shared tool and an SSE relay. The server facilitates agent-to-agent communication by holding tool responses until the opponent makes a move, managing the game state in real-time.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables two people to play turn-based tic-tac-toe together inside their AI chat clients, with a shared interactive board, lobby, invitations, and rematches.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI models and human players to play tic-tac-toe together through MCP, with server-enforced rules, turn-based waiting, and live board state via tools, resources, and prompts.
      MIT