Connecting to Claude
This page is the technical setup guide for using Fluent with Claude Desktop and Claude Code.
If you want the plain-language overview first, start here:
Today, the documented path is Fluent OSS. Fluent Cloud setup docs will be published when the cloud product is ready.
Claude Desktop
Fluent OSS
- Generate the config automatically:
bash
npm run scaffold:mcp -- --client claude --track oss \
--base-url http://127.0.0.1:8788- Or write the config directly to a file:
bash
npm run scaffold:mcp -- --client claude --track oss \
--base-url http://127.0.0.1:8788 \
--out ~/.claude/fluent.mcp.json- The generated config includes your bearer token (resolved from
~/.fluent/):
json
{
"mcpServers": {
"fluent": {
"url": "http://127.0.0.1:8788/mcp",
"headers": {
"Authorization": "Bearer <your-oss-token>"
}
}
}
}- Restart Claude Desktop to pick up the new server.
Claude Code
Fluent OSS
bash
npm run scaffold:mcp -- --client claude --track oss \
--base-url http://127.0.0.1:8788Verifying the Connection
Once connected, ask Claude:
"What are my Fluent capabilities?"
Claude will call fluent_get_capabilities and show you:
- Contract version
- Available, enabled, and ready domains
- Onboarding state
- Profile summary
- Tool discovery hints
First Use
If no domains are enabled yet:
"Enable the meals domain"
Claude will call fluent_enable_domain, begin onboarding, and walk you through setting your preferences. The same flow works for Health and Style.
Troubleshooting
Tools not appearing
- Reconnect the MCP server in Claude settings
- Verify Fluent is running:
curl http://127.0.0.1:8788/health - Check your bearer token is correct
Stale tools after endpoint change
If you change the Fluent endpoint:
- Reconnect the MCP server
- Re-authorize if prompted
- Remove stale credentials for the old endpoint if Claude keeps showing the previous tool set