For Developers
Extend FluidGrids. Build custom nodes, automate via CLI, or integrate programmatically with our SDKs.
Start here
- CLI Reference: the
fluidgridsCLI,npm install -g @fluidgrids/cli - Node SDK: the TypeScript SDK,
npm install @fluidgrids/sdk - MCP Server: drive FluidGrids from Claude and other MCP clients,
npx -y @fluidgrids/mcp-server - Python SDK: on the roadmap, not on PyPI yet
APIs
- GraphQL API: endpoints, headers, types and subscriptions
- REST API: webhook, form and resume endpoints
- Webhooks: starting workflows from other systems, and signing requests
Tooling
- Browser Extension: on the roadmap
- VS Code Extension: on the roadmap
- Managed RAG
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.
| Tool | How to select the endpoint |
|---|---|
| CLI | FLUIDGRIDS_WORKSPACE_ENDPOINT, FLUIDGRIDS_GLOBAL_ENDPOINT and FLUIDGRIDS_OIDC_ISSUER; see CLI configuration |
| Node SDK | workspaceEndpoint / globalEndpoint in the constructor, or the same environment variables; see Node SDK configuration |
| MCP server | FLUIDGRIDS_WORKSPACE_ENDPOINT and FLUIDGRIDS_GLOBAL_ENDPOINT; see MCP environment variables |
For platform-level concerns (auth, RBAC, tags, billing), see Burdenoff Workspaces developer docs.