That is the point of pairing them: the connector holds a key, and what that key can reach is decided by DreamFactory's roles and identity passthrough, so an assistant is bounded by the same policy as any other client. Two setup traps are documented and both are easy to hit — the extension ships disabled until you enable it, and an NVM-managed Node can leave Claude Desktop running the wrong version.
The official MCP server for DreamFactory, a self-hosted enterprise data-access platform that puts governed APIs in front of any data source with role-based access and identity passthrough. This connects that platform to Claude.
- A Desktop Extension file from the repository's releases that installs into Claude Desktop by double-clicking, then prompts for your DreamFactory API key and service URL
- Access scoped by the DreamFactory service you point it at — the URL includes the service name, so one connection targets one governed service
- Role-based access and identity passthrough enforced by DreamFactory itself, not by the connector
- A Docker path — build the image and run it with the URL and key passed as `--env` arguments
A DreamFactory instance and an API key. Configuration is two environment variables: `DREAMFACTORY_URL`, which points at a specific service such as `https://example.dreamfactory.com/api/v2/<service-name>`, and `DREAMFACTORY_API_KEY`. Node 22.10.0 or newer is required — the README documents an NVM path problem where Claude Desktop picks up the wrong Node version, and gives a wrapper-script workaround. Install the DXT release, or clone and `npm install` then `npm run build` and point the config at `build/index.js`. After installing the extension you must flip its Disabled switch to Enabled before it works.