Connect with AI

Let Codex, Claude, Cursor, or any MCP-capable agent operate Fluere with you.

Fluere MCP gives your AI assistant a guided way to onboard accounts, add Token Supply, manage CRD, create consumer API keys, inspect usage, and follow settlement status. The page is public so you can send it to an agent before you create an account.

Step 1: Add Fluere MCP

Paste this no-token MCP server entry into Codex, Claude Desktop, Cursor, or another MCP client. This step only installs the tool connection; it does not require a Fluere account or Agent Access token.

{
  "mcpServers": {
    "fluere": {
      "url": "https://fluere.io/api/mcp/fluere"
    }
  }
}

Install prompt

Send this prompt before Fluere is connected. After the agent adds the connection, restart your AI Agent, IDE, or desktop client so Fluere is available.

You are helping me connect Fluere to this AI workspace.

Use the Fluere connection configuration shown on this page to add Fluere to my AI environment.

Use customer-facing language. Do not mention internal tool names, access credentials, connection details, or configuration syntax unless I explicitly ask.

Do not try to create my Fluere account yet. After Fluere is added, tell me to restart my AI Agent, IDE, or desktop client. After restart, I will send the onboarding prompt.

Two-step prompt flow

Step 2: Continue onboarding

After restart, send this second prompt. The agent should guide the user through account setup, email verification, permission, Token Supply, CRD, and API key tasks in customer-facing language.

Now continue Fluere onboarding. Do not assume I am already signed in.

Use customer-facing language. Do not mention internal tool names, access credentials, connection details, or configuration syntax unless I explicitly ask.

Help me:
1. Create or find my Fluere account.
2. Ask for my email verification code when needed.
3. Complete the permission step so you can continue managing Fluere for me.
4. Add Token Supply from my provider key, run the quality check, and explain the agreement before I sign.
5. Check my CRD balance, model prices, usage records, settlements, and withdrawal status.
6. Help me buy CRD, create or rotate a consumer API key, and manage account settings only after I confirm.

For sensitive actions such as buying CRD, signing a supply agreement, disabling a key or source, changing payout details, or withdrawing funds, stop and ask for my explicit confirmation before calling the tool.

Step 3: Agent Access configuration

After OTP verification, the agent should store the returned agentAccessToken and update the MCP server headers for future account management calls.

{
  "mcpServers": {
    "fluere": {
      "url": "https://fluere.io/api/mcp/fluere",
      "headers": {
        "Authorization": "Bearer <agentAccessToken>"
      }
    }
  }
}

Sensitive operations require confirmation

Buying CRD, payment authorization, withdrawals, signing agreements, disabling keys or sources, and changing payout details are not background actions. The agent must explain the impact and wait for your explicit approval before continuing.