"Cloud Foundry" matching MCP servers:

An MCP server that wraps the ThreeHats Foundry VTT REST API relay so an LLM agent can author and manage Foundry VTT content, primarily creating D&D 5e creatures, through native MCP tools.

MCP server for managing Foundry VTT journal content (entries, categories, pages) and listing actors, enabling AI-assisted world-building via natural language commands.

Enables MCP-capable AI assistants to work with a Foundry VTT world by reading and writing journals, scenes, compendiums, actors, combat, and more, subject to Gamemaster permissions and undoable changes.

Enables MCP clients to interact with Foundry VTT for the Daggerheart RPG, with native duality rolls and resource updates.

Enables preparing Foundry worlds and running encounters through the FoundryVTT REST API Relay, with tools for managing worlds, scenes, encounters, and table play.

Connects Claude Desktop to Foundry VTT for AI-powered campaign management, enabling natural language interaction with game data including quest creation, character management, compendium searches, and dice rolling. Provides 20 MCP tools for seamless integration between Claude and your tabletop RPG sessions.

Enables controlling Foundry VTT 14 from Codex CLI or other MCP clients through a GM browser bridge using Foundry's public APIs and an optional Plutonium adapter.

Enables MCP clients to interact with Foundry Virtual Tabletop worlds via a permissioned Windows host and GM-authorized browser companion, including document management, asset uploads, journal sessions, and background intelligence.

Enables AI-powered campaign management for Foundry Virtual Tabletop through natural language, supporting multiple RPG systems with tools for quest creation, character management, combat resolution, and more.

MCP server + Foundry VTT module for WFRP4e that lets AI clients interact with a Foundry world via tools for managing characters, journals, rolltables, and more.

Enables AI agents to interact with Foundry Virtual Tabletop, supporting reading world data, managing combat, rolling dice, and updating actor attributes via a sidecar architecture.

Enables AI agents to discover and call all Roblox Open Cloud API endpoints through five small tools, without loading an API reference into context.

Enables AI agents to drive a running Roblox Studio in real time over a single WebSocket, executing whole Luau programs, installing in-engine controllers, hot-patching scripts during live playtests, and receiving errors, assertions and other events as pushes. It also reaches Roblox Open Cloud for the open place and answers visual questions via a vision sidecar, exposing all of this through nine MCP tools.

Enables AI agents to query Roblox experience analytics such as DAU, revenue, retention, performance, and funnels through the Open Cloud API.

A local MCP server that gives AI agents read access to Roblox experience analytics via the Open Cloud API, exposing 168 metrics and analysis tools for retention, engagement, monetization, and more.

A local MCP server that lets AI agents manage Roblox developer products and game passes through the Open Cloud API.

Enables AI-powered image generation and curation for Foundry VTT tabletop art, letting users create portraits, tokens, handouts, and scene backgrounds from prompts via a local headless ComfyUI workflow.

Enables Claude to interact with LifeUp Cloud API on your local network for task management, achievements, and user information. Supports 20 tools including creating, editing, and querying tasks, achievements, and shop items.

Enables AI assistants to look up Lichess players, review their recent games and flagged mistakes, and answer chess questions using Lichess's own server analysis, cloud evaluations, and Syzygy tablebase rather than guessing. Also serves daily and by-id puzzles (with solutions hidden until requested) and opening explorer statistics, returning explicit "not available" responses when Lichess has no data.

Enables AI assistants to read and edit live D&D 5e Foundry VTT worlds and manage Molten-hosted server lifecycle via the Model Context Protocol.