Random Tables MCP server

@pipeworx/random-tables

Pipeworx original composable random tables for tabletop and narrative play — encounters, loot, weather, complications, NPC traits, plot hooks, tavern scenes, rumours and settlement quirks — with nested {{table:}} references resolved recursively, plus caller-supplied custom tables. Keyless, no upstream, no COGS.

Part of Pipeworx — an MCP gateway connecting AI agents to 1872+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

built-in table. Returns both the raw entry text and the fully resolved text (nested {{table:}} references expanded). Reproducible via seed.

• rolltable(table, count?, seed?, sessionid?) — roll 1-20 entries from a

([{text, weight?}]); entries may reference built-in tables the same way.

• rollcustomtable(entries, count?, seed?) — roll from a table YOU supply

entry count, optionally filtered to fantasy | scifi | modern.

• listrandomtables(genre?) — every built-in table's id, title, genre and

entry text, so any {{table:}} references are visible as written).

• getrandomtable(table) — one built-in table in full, unresolved (raw

Built-in tables

encountersfantasy, encountersscifi, encountersmodern, loot, weather, complication, npcpersonality, npcsecret, npcoccupation, plothook, tavern, rumour, settlementquirk, npcfull (a composed sentence that nests npcpersonality + npcoccupation + npcsecret in one roll — the worked example of nested references).

Genre-tagged tables (encounters, loot, tavern) are fantasy/scifi/modern flavored; the rest are genre-agnostic and apply under any listrandom_tables genre filter.

Nested references

An entry's text may embed {{table:}}, which is resolved by rolling a weighted entry from that table and substituting it in, recursively, up to 6 levels of nesting. A reference to an unknown table id, or a cycle (a table that ends up referencing itself through a chain of other references), is a loud error naming the offending id or the full chain — never a silent truncation or an empty substitution. rollcustomtable's caller-supplied entries may reference built-in tables the same way, but not other entries in the same custom table (a custom table has no id of its own to reference).

Randomness and reproducibility

Every rolling tool takes an optional seed; the seed actually used is always returned (in meta.seed), whether you supplied one or not. The same seed and arguments reproduce the same draw. These are content generators, not divination — there is no separate "meaning" layer to keep apart from interpretation; the table text is the result, and how you use it at the table is up to you.

Sessions

sessionid on rolltable draws without replacement across calls — useful when you don't want the same loot item or the same rumour to repeat while a session is live. It is hosted-only, backed by the gateway's shared KV (injectCacheKv: true); the npm standalone package has no KV, so a call that passes sessionid there gets back sessionsupported: false and a plain seeded roll instead (every tool still works without session_id regardless of environment).

There is no separate "open session" tool. Pass any string as sessionid on your first call for a table — the response tells you plainly whether it continued an existing session or had to open a new one, and gives you the real sessionid to reuse on your next call. Omit sessionid entirely for an ordinary independent weighted roll (the common case; no KV needed). rollcustom_table has no session support — sessions only track built-in tables, which have a stable id and size to key a session on.

Auth

Keyless.

Data sources

Shortened. The full README is on GitHub.