How to add AI to Foundry VTT
Install Familiar, activate your licence key, then paste a provider key or connect a plan you already pay for.
Guides
I built Familiar and run my own campaign on it every week. Setup first, then the method.
You bring a published adventure and prep it in Foundry. The AI runs it, from one scene to the whole DM's side, and does not invent the plot.
New to Familiar? These four, in this order, take you from an empty module to a first session.
Not playing D&D 5e? See what Familiar does on your system.
Install Familiar and connect an AI. The rest of the guides build on these two.
Install Familiar, activate your licence key, then paste a provider key or connect a plan you already pay for.
What to have ready, three ways through the setup, the check that proves the link, and the faults every client shares.
One page per assistant that has its own way in. Open the one you already pay for.
Anthropic builds both clients, so no agent app sits in the path. How you add each one, and what differs between them.
Codex is the route in, as a tab in the ChatGPT app or as Codex CLI, on every plan including Free.
Antigravity or a Gemini API key in Familiar's own chat window: which suits your table, and the snags only Antigravity has.
xAI's terminal agent is the one Grok that speaks to a Foundry game. One command registers Familiar and a second proves the link.
Where Muse Code keeps Familiar and your model, what /mcp has to say before the first ask, and the fixes for its installer.
MCP or a provider key, which model to run, and whether to run one yourself.
MCP rides a subscription you already hold. A provider key buys a specific model and tighter spend. The numbers, and what only the built-in chat can do.
Which model holds a tool chain together, where to get one, and when to turn the thinking up or down.
Run the model on your own PC, so your world never leaves the machine. One settings tab and one switch. Without a discrete GPU, expect minutes per turn.
For a GM with Familiar connected and a session coming up.
Where a bare chat window breaks down, and the method that starts where it stops: who runs what, and what a session looks like.
Which parts of a published adventure go into journals, which onto sheets, and how to bake your rulings into the pages the AI reads.
Your vault is never copied into Foundry: the AI reads it where it is. The setup, and how to fence off the folders it should not see.
Five lines make Garric the innkeeper, and a busier NPC gets a fuller anchor card. What he says when a player asks past the page.
A long campaign overflows any context window. Keep a searchable record in Foundry so the AI reads from your notes, not a fading window.
Watch a troll's illegal claw get refused, verbatim, and see which calls the rules engine hands back to you.
For a small table, and for anyone building one like mine.
You take the player seat for once and Familiar runs the rest of the table. How a session goes, and the limits to know going in.
One PC, one player, a microphone, and an AI playing two heroes and every monster. The exact rig, and the order to build it in.
A copy-paste rules pack for any AI running a game: roll only when it matters, run the adventure you prepared, never decide for the players.
Something stopped working? The faults every client shares, and the fix for each.
Need a map for tonight? The battlemap generator has its own page.
Giving the table a voice? Voices, music, sound effects and transcription have their own page.
Looking for the full tool list? See everything Familiar can do.