fluo MCP.
Set up auth from your agent.
Give Claude — and any MCP-compatible client — what it needs to wire up authentication: create apps, fetch API keys, configure providers. One URL, no dashboard.
https://mcp.fluo.dev/mcp What is this? An open standard that lets AI assistants use external tools.
The fluo MCP server exposes the fluo management API as tools an agent can call. Tell your agent to use fluo for authentication and it can create an account, spin up an app, and hand back the API key — all without you opening the dashboard.
Connect a client. Point it at the URL, add your token.
Claude Code
One command in your terminal.
claude mcp add --transport http fluo https://mcp.fluo.dev/mcp \
--header "Authorization: Bearer pat_..." Cursor · Windsurf · Zed
Add to your MCP config.
{
"mcpServers": {
"fluo": {
"url": "https://mcp.fluo.dev/mcp",
"headers": { "Authorization": "Bearer pat_..." }
}
}
} Claude.ai & ChatGPT
One-click OAuth connect is coming. For now, use any client that supports custom headers (above) with your personal access token.
No token yet? Your agent can call create_account first, then re-add the connector with the token it returns.
Tools. Everything the dashboard does.
Example prompts. Just ask.
Protocol. The technical details.
Troubleshooting.
Ask your agent to call create_account with your email — it returns a token (pat_…). You can also mint more with issue_token. Treat it like a password.
The Authorization header is missing or the token is wrong. Make sure the client sends Authorization: Bearer pat_… and that you copied the full token.
Any client that supports remote MCP over HTTP with custom headers: Claude Code, Cursor, Windsurf, and Zed. One-click OAuth for Claude.ai and ChatGPT is on the way.
The agent can store the client IDs and credentials via update_app, but creating the OAuth client in the Google Cloud Console or Apple Developer portal still has to be done by a human.