fluxbit-mcp
Connect your own AI agent to FluxBit — the game-art studio your agent runs.
This is a thin Model Context Protocol (MCP) stdio client. It exposes your FluxBit projects to your own agent (Claude Code, or any MCP client) as tools: list projects, inspect a project's asset catalog and house art-bible, generate concept art / 3D / audio on FluxBit's GPUs, and propose a publish (a human approves the irreversible step). Your agent is the brain; FluxBit is the hands.
It holds no model credentials — it authenticates to FluxBit with a per-user Bearer token you mint in the app, and every write / paid / publish action stays gated server-side by FluxBit (RBAC, per-project scope, spend caps, moderation, and human-in-the-loop publish).
Connect (no install, no clone)
In FluxBit, open Connect an agent → set a spend cap → mint a token. Then run one command:
claude mcp add fluxbit \
--env FLUXBIT_URL=https://fluxbit.app \
--env FLUXBIT_TOKEN=<your-token> \
-- uvx fluxbit-mcp
uvx (from uv) fetches and runs this package on demand — nothing to install or keep
updated. Then just talk to your agent: "Generate three hero-ship concepts for my game, then show me the strongest one."
Configuration
| Env var | Default | Meaning |
|---|---|---|
FLUXBIT_URL |
http://127.0.0.1:8770 |
Your FluxBit instance base URL |
FLUXBIT_TOKEN |
— | The Bearer token you minted in Connect an agent |
License
MIT.
1 maintainer
Metadata
1 maintainer
Release files for fluxbit-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fluxbit_mcp-0.1.0.tar.gz | 6.1 kB | Without provenance | Details for fluxbit_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fluxbit_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for fluxbit_mcp-0.1.0-py3-none-any.whl |
Total release size: 12.7 kB
Release files / fluxbit_mcp-0.1.0.tar.gz
| Download URL | fluxbit_mcp-0.1.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dba86029ffcfdeba2add4a2dca23c768f5f8850e4d86d7eef88bea92e79a24de
|
|
BLAKE2b-256 checksum How to use checksums |
9d3c4bac12b57c4c7b579ff79ef5252502910e32951f8b09ffce044449dbb974
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.22 {"installer":{"name":"uv","version":"0.9.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / fluxbit_mcp-0.1.0-py3-none-any.whl
| Download URL | fluxbit_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c30346679a800efe0e75f593a7ff4e11c660caed31bf1ddf5060e276876676c2
|
|
BLAKE2b-256 checksum How to use checksums |
640f3baaa38ef49d9a4d6aef82e50e0c036d4b3b573aa0dc633f42d828a7e45a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.22 {"installer":{"name":"uv","version":"0.9.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for fluxbit-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
