Integrations — FluxFiles
Integrations
Drop-in adapters for your stack
Official adapters embed FluxFiles natively in the frameworks and editors you already use.
Server-side packages
Mint tokens from your backend — or hand one to an AI agent
These aren't UI adapters — they issue the JWTs that scope what a FluxFiles UI (any of the adapters above, or the standalone iframe) is allowed to do. No PHP required to issue tokens. The MCP server works the other way round: it hands one of those scoped tokens to an AI agent, which can then do only what the token allows.
Mint FluxFiles tokens from any JS backend (Express, Next.js, Nuxt) with @fluxfiles/node — byte-compatible with the PHP core. No PHP required to issue tokens.
Mint FluxFiles tokens from any Python backend (FastAPI, Django, Flask) with fluxfiles-token — byte-compatible with the PHP core. No PHP required to issue tokens.
Let Claude Desktop, Claude Code or any MCP client list, search and read your files with @fluxfiles/mcp — bounded by the scoped JWT you mint. Write and trash tools stay off unless you enable them.