Poker

mcp server for poker app
  • javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "hirao-y-poker_mcp": {
      "command": "node",
      "args": [
        "src/mcp_server_stdio_v4.js"
      ],
      "env": {
        "POKER_INSTALL_PATH": "C:/Poker"
      }
    }
  }
}

You will run a modular MCP server that manages YAML-based input for radiation-shielding calculations with full MCP support. It exposes a STDIO-based interface so you can send structured commands to build, validate, and execute shielding models and calculations in a robust, auditable workflow.

How to use

You interact with the Poker MCP Server through an MCP client that speaks the MCP protocol over STDIO. The server starts from a local script and stays ready to accept instructions for creating geometric bodies, assigning materials, placing radiation sources and detectors, running calculations, and saving or resetting your model. Follow the flow below to accomplish typical tasks.

How to install

# Install dependencies for the server
npm install

# Or run the MCP server directly with NPX
npx poker-mcp

Configuration and usage notes

The core entry point for the local MCP server is the main server file located at src/mcp_server_stdio_v4.js. When running locally, you typically start the server with a node command that points to this file and relies on your environment to locate data and libraries.

Environment variables are optional. If you use the default data source for nuclide information, you may set POKER_INSTALL_PATH to guide the server to the ICRP-07 data directory. If you provide this variable, it will be used to copy data to the active data directory on first run.

Examples of common tasks

Create a concrete shielding body with specified dimensions. The server will perform collision checks and prepare the model for further refinement.

Assign materials to your shielding volume, for example adding concrete with its density, before placing sources and detectors.

Place a radiation source and let the system automatically consider descendant nuclides and potential detector placements. Run the full shielding calculation and analyze dose distributions.

Security and stability tips

Rely on the STDIO MCP interface for deterministic, low-latency communication. Keep your YAML inputs validated and backed up. Use the built-in backup and reset features to maintain a safe working state during model exploration.

Troubleshooting tips

If you encounter startup issues, verify that Node.js version is at least 18.0.0, dependencies are installed, and the server script path is correct. Ensure the environment variable POKER_INSTALL_PATH is set only if you need to point to an alternate data source.

Notes on extension and usage

The server is designed to manage a complete workflow from geometry creation to calculation results. You can rely on automatic validation features to prevent non-physical configurations and ensure unit consistency across dimensions, densities, and activities. All changes can be backed up and restored as needed.

Available tools

poker_proposeBody

Propose a new body (geometry) in the current model with automatic collision detection and consistency checks.

poker_updateBody

Update an existing body’s parameters (size, position, shape) with validation.

poker_deleteBody

Remove a body from the model and revalidate the surrounding setup.

poker_proposeZone

Assign or modify a material zone (e.g., concrete density) within the body.

poker_updateZone

Update material properties for a zone and verify consistency.

poker_deleteZone

Delete a material zone from the model.

poker_proposeTransform

Define geometric transforms for positioning or aligning components.

poker_updateTransform

Edit existing transforms and ensure they remain collision-free.

poker_deleteTransform

Remove a transform from the model.

poker_proposeBuildupFactor

Create a buildup factor setting to control buildup calculations.

poker_updateBuildupFactor

Modify buildup factor parameters and validate results.

poker_deleteBuildupFactor

Remove a buildup factor configuration.

poker_changeOrderBuildupFactor

Reorder buildup factor entries to adjust calculation priority.

poker_proposeSource

Place a radiation source in the model and auto-suggest descendant nuclides.

poker_updateSource

Modify source properties such as position, strength, and spectrum.

poker_deleteSource

Delete a source from the model.

poker_proposeDetector

Configure detector placements and types for dose mapping.

poker_updateDetector

Update detector settings and optimize layout.

poker_deleteDetector

Remove a detector configuration.

poker_proposeUnit

Define or adjust unit settings for length, density, angle, and activity.

poker_getUnit

Query current unit configuration.

poker_updateUnit

Change unit settings and propagate validity checks.

poker_validateUnitIntegrity

Check the consistency and correctness of unit definitions across the model.

poker_analyzeUnitConversion

Analyze and report conversion factors between differing unit systems.

poker_applyChanges

Save the current model changes to the working YAML configuration.

poker_executeCalculation

Run the shielding calculation and produce results for interpretation.

poker_resetYaml

Reset YAML input at specified level while preserving key settings.

poker_confirmDaughterNuclides

Confirm and ensure correct descendant nuclide handling.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational