For Developers
Extend FluidGrids. Build custom nodes, automate via CLI, or integrate programmatically with our SDKs.
Start here
- CLI Reference —
fluidgridsCLI commands - Node SDK — TypeScript SDK for workflow automation
- Python SDK — Python SDK for workflow automation
- MCP Server — drive FluidGrids from Claude and other MCP clients
All four are built from source today; none is on a package registry yet. Each page shows the current install path.
Tooling
- Browser Extension — Chrome extension for page actions against the current tab
- VS Code Extension — workflow management inside VS Code
- Doctor (E2E) — backend E2E test suite
- Backend Service —
wspace-workflow-svcintegration guide
Building on the platform
- Custom Nodes — building reusable workflow nodes
- Node Property Panels — UI blocks for node configuration
- Examples — code snippets and patterns
Selecting an environment
All developer tooling defaults to production. How you point a tool at alpha or a local stack depends on which tool it is:
| Tool | How to select the endpoint |
|---|---|
| CLI | FLUIDGRIDS_API_URL, the -u/--url flag, or fluidgrids config set url |
| Node SDK | baseUrl in createClient, or FLUIDGRIDS_ENDPOINT |
| Python SDK | endpoint= in FluidGridsConfig, or FLUIDGRIDS_ENDPOINT |
| Browser & VS Code extensions | BURDENOFF_ENV=local|alpha|prod |
| MCP server | FLUIDGRIDS_GRAPHQL_URL and FLUIDGRIDS_API_URL |
For platform-level concerns (auth, RBAC, tags, billing), see Burdenoff Workspaces developer docs.