After an entry is written, the stub tools read it for entities that deserve their own page and create placeholders for them — which is how one character description turns into a linked set of locations and factions instead of a dead end. Order matters: world first, taxonomies second, entries third.
A worldbuilding pipeline over MCP: it creates a world project on disk, generates taxonomy guidelines, writes entries that reference their taxonomy, stubs out entities they mention, and builds a static website from the result.
- instantiate_world — a complete world project structure in its own uniquely named folder
- generate_taxonomy_guidelines and create_taxonomy_folders — custom taxonomies such as characters, locations and artifacts
- create_world_entry — entries that automatically reference the taxonomy overview they belong to
- identify_stub_candidates and create_stub_entries — placeholder pages for entities your writing mentions
- generate_image_from_markdown_file — an image per entry, with a style and an aspect ratio from 1:1, 16:9, 9:16, 3:4 or 4:3
- build_static_site — a navigable website with image galleries
- File helpers: save_world_content, read_world_content, list_world_files
Pip install -e . and npm install in the cloned repository, then run vibe_worldbuilding_server.py from your client. Image generation is the only part that needs credentials — a FAL API key in FAL_KEY; everything else works without one.
One command — mcp install vibe_worldbuilding_server.py -v FAL_KEY=your_fal_api_key_here