u/EnergyRemarkable6139

Content Name: Foundry API Bridge

Content Type: Module

System: D&D5e

Description: Posting a dev update on Foundry API Bridge — a self-hosted HTTP API for your Foundry world.

Point any HTTP client (curl, Python, your homegrown script, an external dashboard) at it, and read or write actors, items, journals, scenes, and combat — programmatically, from outside Foundry.

Short demo above, then the endpoint surface and the roadmap.

The project is under active development. New endpoints ship in regular updates, with priorities driven by real use. Expect frequent updates over the next few months as the surface fills out.

Roadmap

  • Endpoint coverage — continuing to fill the HTTP surface driven by real use cases.
  • Client socket — real-time push channel from Foundry to external clients. The current API is request/response; the socket layer lets external code subscribe to events (combat start, HP change, scene activation, chat) and react without polling.

Links

u/EnergyRemarkable6139 — 9 days ago

Content Name: Foundry API Bridge

Content Type: Module + companion MCP server

System: D&D5e (with system-agnostic features)

Description:

Foundry API Bridge is a set of MCP tools that expose the Foundry VTT API to external clients. It runs as a companion server alongside your Foundry instance and provides programmatic access to actors, scenes, tokens, combat, journals, roll tables, and compendiums. Any MCP-compatible client can read and modify world state, letting you script or offload routine GM work — building NPCs from compendium entries, populating scenes, advancing combat, updating journal pages, rolling on tables — without clicking through the Foundry UI.

The bridge exposes ~80 tools across actors, items, scenes, tokens, combat, rolls, active effects, journals, roll tables, chat, and compendiums. Item activation is Midi-QOL-aware (target resolution, AoE templates, upcasting). Scene queries return an ASCII tactical map and an optional canvas screenshot.

Example workflow — staging a Phandelver side quest into Foundry from prepared notes. The narrative, NPC descriptions, statblocks, and encounter tactics come from the DM; the bridge handles formatting and entity creation across three phases:

  1. Journal — multi-page entry with headings, blockquoted read-aloud, tables, skill-check formatting
  2. Actors — NPCs built from compendium statblocks, bios populated from the journal, portraits and active effects applied
  3. Linking — second pass replacing NPC name mentions with @UUID[Actor.X]{Name} references

Video above.

Link: Foundry module — foundryvtt.com/packages/foundry-api-bridge. The MCP server is hosted; endpoint and credentials come with the Patreon tier. Source on GitHub: alexivenkov/foundry-api-bridge-module.

Patreon: patreon.com/nitromoon — Adventurer (€3/mo) and Dungeon Master (€10/mo) tiers.

u/EnergyRemarkable6139 — 16 days ago