Overview

The MCP server lets an agent such as Claude Code work in Fluorite for you. It can search the built-in nodes and presets, read community shaders, create and edit your shaders, render them to check the result, publish them, and file them into folders.

It can't delete or archive shaders, or delete folders.

Get a token

The server needs a token. Create a personal token at /settings/tokens, or an org API key if the agent should act for an organization. A draft preview token only lets it read. See Tokens.

A personal token works in your personal organization unless the agent names another one with org. The me_get tool lists the ones you can use.

Add the server

The server runs on your computer, so it can show the agent rendered images and upload images and videos from your computer for a shader to use. Replace flr_… with your token, then restart the agent.

Claude Code

claude mcp add fluorite -s user -e FLUORITE_TOKEN=flr_… -- npx -y @fluorite-studio/mcp

-s user makes it available in every project; drop it to add it to the current project only.

Codex

codex mcp add fluorite --env FLUORITE_TOKEN=flr_… -- npx -y @fluorite-studio/mcp

Cursor, Claude Desktop and other clients

Add this to the client's MCP config (.cursor/mcp.json, claude_desktop_config.json, or .mcp.json in a project):

{
  "mcpServers": {
    "fluorite": {
      "command": "npx",
      "args": ["-y", "@fluorite-studio/mcp"],
      "env": { "FLUORITE_TOKEN": "flr_…" }
    }
  }
}

It needs Node.js 18 or later. Rendering needs Chrome. Without it, run npx playwright install chromium once.

Next

• Building shaders: how an agent works, with an example.
• Tools: every tool and its arguments.