rpg-generator

This MCP server provides two utilities for generating random tabletop RPG content: random_campaign_idea and random_region_attributes. The ideas combine character types, settings, and movie inspirations to produce a unique campaign concept each time, while the region attributes generator outputs a formatted, markdown-style description including region tags, population level, and population characteristics to help with world-building. You can access these tools through an MCP client (such as Claude) by invoking the corresponding tool endpoints exposed by the rpg-generator-mcp-server. The server is designed to be easy to extend with additional generators following the existing pattern in the source code, so you can add more tools that produce creative content or world-building data for your RPGs.

Prerequisites:

• Node.js (recommended LTS)
• npm (comes with Node.js)

Installation steps:

1. Clone the repository: git clone https://github.com/guyroyse/rpg-generator-mcp-server.git cd rpg-generator-mcp-server

2. Install dependencies: npm install

3. Build the TypeScript project (produces JavaScript for runtime): npm run build

4. Start the MCP server:

   • If the project provides a start script, run: npm run start
   • Otherwise, run the built server directly (path may vary depending on build output): node dist/index.js

Note: The README references using the server binary-like command rpg-generator-mcp-server for Claude configuration, which implies the package can be installed or linked as a CLI tool. If you install via npm as a package name, ensure it’s available in your PATH after installation.

Tips and considerations:

• The server exposes two main tools: random_campaign_idea and random_region_attributes. They are designed to be combined with MCP clients like Claude or other MCP-enabled assistants.
• To test with Claude, you can add an entry to claude_desktop_config.json under mcpServers like shown in the README, replacing the command with the server binary/name you use locally.
• If you extend the server with new generators, follow the existing pattern by creating a new generator function and wiring it into mcp-server.ts so it becomes accessible as a new tool.
• If you encounter environment or path issues, verify that the build output directory matches the runtime path you’re invoking (e.g., dist/ or build/), and ensure Node is able to execute the server binary or entry point.
• For testing without full build/run cycles, you can try the MCP Inspector via npm run inspect as described in the README to verify tool shapes and responses.