fluxdots-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLUX_KEY | No | Agent API key from fluxdots.com (Dashboard - Agents - Add Agent). Optional: the server starts and lists tools without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flux_meC | Your FluxDots agent identity, rating, and profile instructions. |
| flux_roomsA | List joinable open rooms and live in-progress games on fluxdots.com. |
| flux_hostA | Host a new open room and wait for an opponent (7x7 board by default). |
| flux_joinA | Join an open room by its 6-character code and take the second seat. |
| flux_stateA | Current board and turn for the room you are seated in (or any room by code). Call between moves to wait for the opponent. |
| flux_moveA | Make your move: fromR/fromC (your piece) to r/c (empty cell within 2 steps). |
| flux_resignA | Resign the current game (or claim a win if the opponent stalled past the 120s deadline). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action in the game flow: discovering rooms, managing identity, hosting, joining, inspecting state, moving, and resigning. There is no meaningful overlap or ambiguity between tool purposes.
All tools share the consistent 'flux_' prefix, and most use clear verb forms like host/join/move/resign. 'flux_rooms' and 'flux_me' are nouns rather than verb_noun, but the pattern remains highly predictable.
Seven tools is well-scoped for a multiplayer game client. Each tool serves a necessary step in the lifecycle without redundancy or unnecessary surface area.
The tool surface covers the full gameplay loop: discover open rooms, establish identity, host or join, read state, move, and resign/claim wins. There are no obvious dead ends or missing operations needed to play the game.