Skip to content
Back to search

postflop-mcp

MCP server that solves heads-up postflop poker spots with a GTO solver

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sawadakaku--postflop-mcp/badge.svg)](/listings/sawadakaku--postflop-mcp)

HTML

<a href="/listings/sawadakaku--postflop-mcp"><img src="/api/listings/sawadakaku--postflop-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Desktop

Download `postflop-mcp.mcpb` from the [latest release](https://github.com/sawadakaku/postflop-mcp/releases/latest) and open it. It contains binaries for macOS (Apple Silicon and Intel), Linux (x86_64) and Windows (x86_64).

Prebuilt binary

Download the archive for your platform from the [latest release](https://github.com/sawadakaku/postflop-mcp/releases/latest), extract it, and put the binary somewhere on your `PATH` as `postflop-mcp`. On macOS, if Gatekeeper blocks the downloaded binary, run `xattr -d com.apple.quarantine postflop-mcp`.

From source

Requires stable Rust ([rustup](https://rustup.rs/)).

cargo install --git https://github.com/sawadakaku/postflop-mcp --locked

This installs `~/.cargo/bin/postflop-mcp`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 109 lines
  1. # postflop-mcp
  2. An MCP server that solves heads-up postflop spots (flop, turn or river) with a GTO solver and answers questions about the solution. Connect it to Claude or another MCP client and ask "solve this spot" or "how does this hand play here, and why?" — the answers come from solver numbers.
  3. - Solver: [postflop-solver](https://github.com/b-inary/postflop-solver) (AGPL-3.0)
  4. - A single Rust binary using the MCP stdio transport
  5. - Solved games are cached; solving the same spot again loads in about a second
  6. - Range charts, game trees and suit-by-suit blocker tables are written as HTML you can open in a browser
  7. - MCP Registry name: `mcp-name: io.github.sawadakaku/postflop-mcp`
  8. ## Install
  9. ### Claude Desktop
  10. Download `postflop-mcp.mcpb` from the [latest release](https://github.com/sawadakaku/postflop-mcp/releases/latest) and open it. It contains binaries for macOS (Apple Silicon and Intel), Linux (x86_64) and Windows (x86_64).
  11. ### Prebuilt binary
  12. Download the archive for your platform from the [latest release](https://github.com/sawadakaku/postflop-mcp/releases/latest), extract it, and put the binary somewhere on your `PATH` as `postflop-mcp`. On macOS, if Gatekeeper blocks the downloaded binary, run `xattr -d com.apple.quarantine postflop-mcp`.
  13. ### From source
  14. Requires stable Rust ([rustup](https://rustup.rs/)).
  15. ```bash
  16. cargo install --git https://github.com/sawadakaku/postflop-mcp --locked
  17. ```
  18. This installs `~/.cargo/bin/postflop-mcp`.
  19. ## Register with an MCP client
  20. Claude Code:
  21. ```bash
  22. claude mcp add postflop -- postflop-mcp
  23. ```
  24. Other clients (config file):
  25. ```json
  26. {
  27. "mcpServers": {
  28. "postflop": { "command": "postflop-mcp" }
  29. }
  30. }
  31. ```
  32. ## Usage
  33. Call `solve` first, then point at nodes with paths.
  34. ```text
  35. solve board="Ks7d2c" oop_range="99-22,AJs-A2s,KTs+,..." ip_range="22+,A2s+,..." pot_bb=5.5 stack_bb=97.5
  36. names={"oop": "BB", "ip": "BTN"}
  37. node_info path="x" # BTN's frequencies and EVs after BB checks
  38. hand_detail path="x b33" hand="A7s" # BB's A7s facing a 33% bet
  39. range_chart path="x b33 c / 5h" player="BB" # BB's range chart on the 5h turn (HTML)
  40. resolve_from path="x b33 c / 5h / x" tree={"turn": ["50%,a/a", "50%,100%,a/a"]} # re-solve with other sizes
  41. ```
  42. A path alternates action segments and card segments separated by ` / `: `x` check, `c` call, `f` fold, `allin` all-in, `b75` / `r75` a 75%-pot bet / raise.
  43. ### Tools
  44. | Tool | What it does |
  45. | --- | --- |
  46. | `solve` | Solve a spot (or load it from the cache). `dry_run` only estimates memory |
  47. | `node_info` | Player to act, pot, stacks, and frequency / combos / EV per action |
  48. | `hand_detail` | A combo's or class's frequencies, EVs and equity per action |
  49. | `range` | A range by hand class and by made-hand label |
  50. | `action_range` | The hands taking an action, with the value/bluff split |
  51. | `lookahead` | Frequencies for the next few actions |
  52. | `range_chart` | 13x13 range chart (HTML) |
  53. | `tree_view` | Clickable game tree with range charts (HTML) |
  54. | `suit_chart` | Suit-by-suit table with blocker effects (HTML) |
  55. | `resolve_from` | Re-solve from a street start with other sizes, locks, ranges or stack |
  56. | `exploit` | Best response to a biased opponent, with gain and risk |
  57. | `bookmark` | Name a branch |
  58. | `compare_lines` | Compare lines side by side |
  59. | `compare_stacks` | Re-solve with other stack depths and compare (HTML too) |
  60. Units: amounts and EV are in bb; frequencies, equities and shares are 0-1. EV is the profit from the node on, and folding is 0. Terms are defined in [docs/glossary.md](docs/glossary.md); the design is in [docs/design.md](docs/design.md).
  61. ## How heavy is it
  62. - From the river: under a second
  63. - From the turn: seconds to tens of seconds
  64. - From the flop: tens of seconds to minutes. With the default tree, a BTN vs BB single-raised pot took about 2.5 minutes, 2GB of memory and a 1GB cache file on an Apple Silicon Mac
  65. For a heavy spot, check the memory first with `solve` and `dry_run=true`. Fewer bet sizes (`tree`) or narrower ranges make it lighter.
  66. The default tree, for both players: flop bets 33% and 75%; turn and river bets 50% and all-in; raises are all-in only.
  67. ## Environment variables
  68. | Name | Default | Meaning |
  69. | --- | --- | --- |
  70. | `POSTFLOP_MCP_CACHE_DIR` | `~/.cache/postflop-mcp/games` | Where solved games are cached. `off` disables caching |
  71. | `POSTFLOP_MCP_VIEWS_DIR` | `~/.cache/postflop-mcp/views` | Where HTML views are written |
  72. | `POSTFLOP_MCP_MAX_MEMORY_GB` | `8` | Memory limit for solving. Above it, the game is solved compressed |
  73. Cache files can be deleted at any time; the spot is just solved again.
  74. ## Limitations
  75. - Heads-up only. Preflop is not solved (you pass the ranges)
  76. - No rake
  77. - `exploit` works only at turn or river nodes
  78. ## Releasing
  79. Bump `version` in `Cargo.toml` and `manifest.json`, commit, then push a matching tag (`git tag v0.2.0 && git push origin v0.2.0`). The release workflow tests and builds every platform, creates the GitHub Release with the `.mcpb` bundle and binaries, and publishes `server.json` to the MCP Registry.
  80. ## License
  81. AGPL-3.0-or-later ([LICENSE](LICENSE)), matching postflop-solver.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.