Get the FREE Ultimate OpenClaw Setup Guide →

omgflux

This mcp uses the flux api of ohmygpt to generate images

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio xxpe3-omgflux-mcp-server node /path/to/omgflux-mcp-server/build/index.js \
  --env OHMYGPT_API_KEY="your-api-key-here"

How to use

Omg Flux MCP is a Node.js-based MCP server that runs a built index.js file to provide its modular Minecraft Community Protocol (MCP) capabilities. It expects configuration via an mcpServers entry and uses the OHMYGPT_API_KEY environment variable to access external AI-powered services. Once started, the server exposes its MCP functionality according to the built code, enabling you to interact with the provided tools and endpoints as part of your MCP ecosystem. To customize behavior, modify the environment variables or the start command path to your built index.js file.

How to install

Prerequisites:

  • Node.js v18.0.0 or higher
  • npm (comes with Node.js)

Installation steps:

  1. Clone the repository:
git clone https://github.com/XXpE3/omgflux-mcp-server.git && cd omgflux-mcp-server
  1. Install dependencies:
npm install
  1. Build the project:
npm run build
  1. Run the server using your preferred MCP manager or directly with Node.js:
node /path/to/omgflux-mcp-server/build/index.js

Replace /path/to with the actual path to your repository after building. If you are using an MCP manager, configure it using the provided mcp_config example below and start the manager according to its instructions.

Additional notes

Notes and tips:

  • Ensure Node.js version compatibility (v18+ as recommended).
  • Set OHMYGPT_API_KEY to a valid API key to enable external AI-powered features.
  • The path in the mcp_config should point to the built index.js produced by npm run build.
  • If you rebuild, update the path in the config to reflect the new build/index.js location.
  • When deploying, consider adding a process manager (e.g., PM2) to keep the server running and to restart on failures.
  • If you encounter permissions issues, verify that the user running the server has read access to the build file and the environment is correctly set up for Node.js execution.

Related MCP Servers

Sponsor this space

Reach thousands of developers