claude-emporium

claude-emporium is an MCP server that serves as a centralized gateway for a family of Claude-powered plugin MCPs. It brings together six separate plugin MCPs (praetorian, historian, oracle, gladiator, vigil, and orator) under a single orchestration layer, enabling Claude to discover, evaluate, and compose tools and commands across the plugin set. Using this server, you can query available plugins, initiate plugin-specific workflows, and leverage automated hooks and skills that the plugins expose through MCPs. The server acts as an automation hub: it discovers tool capabilities, orchestrates multi-step tasks, and helps Claude decide when to apply specific plugins based on your prompts and goals.

Prerequisites:

• Node.js v20 or newer installed on your system
• npm (comes with Node.js) or pnpm/yarn if you prefer

Installation steps:

1. Install Node.js from https://nodejs.org/
2. Install the MCP server via npm or npx (no local install required):
   • Using npx (no global install): npm cache clean --force npx -y claude-emporium
   • Or install globally (optional): npm install -g claude-emporium claude-emporium
3. If you are using a local setup, clone the repository and install dependencies: git clone https://github.com/Vvkmnn/claude-emporium.git cd claude-emporium npm install npm run start
4. Configure environment variables as needed (see additional_notes) and ensure the server port is accessible if behind a firewall.

Tips and notes:

• The MCP uses multiple plugins behind the scenes (praetorian, historian, oracle, gladiator, vigil, orator). Each plugin exposes specific capabilities such as plan-generation, memory/search, tool discovery, and orchestration utilities. Expect to see plugin inventories and commands like /search, /restore-vigil, and /review-learning depending on the active workflow.
• Environment variables you may want to configure: CLAUDE_EMPORIUM_PORT: the listening port for the MCP server. CLAUDE_EMPORIUM_API_KEY: if the deployment requires access tokens for Claude or for plugin registries. CLAUDE_EMPORIUM_CONFIG: path or JSON string with runtime settings.
• Common issues: Port conflicts: ensure the configured port is not used by another service. Dependency mismatches: newer Node.js versions may require updated dependencies; run npm install to refresh. API access: some plugin discovery and tool utilities may rely on external APIs; ensure credentials are provided.
• Configuration options: you can adjust which plugins are active, their discovery policies, and how Claude routes prompts to the plugin set through the MCP configuration. Refer to the repository's docs for plugin-specific flags and hooks.