Docs
API 2026-05-27.dahlia Dashboard

Build with AI agents

Connect to Fluveo MCP

Use with AI

Add Fluveo MCP to Claude Code, Cursor, Codex, VS Code or any client.

The Fluveo MCP server is not available in production yet.

Before you start#

For OAuth, you need a Dashboard sign-in with the owner, admin or developer role in the store the agent will use. MCP sign-in with OAuth shows the consent page and how to revoke a connection.

For an agent key, you need a restricted test key (rk_test_...) made in the Dashboard under Settings > Developers > API keys, with This key is for an AI agent checked. Authentication shows how to make one.

Put the key in FLUVEO_MCP_KEY in the shell that starts your client. read -s takes the key without showing it on screen or saving it in the shell history.

Terminal
read -rs FLUVEO_MCP_KEY && export FLUVEO_MCP_KEY

Start the client from that same shell. Each command and file on this page names the variable, never the key, so no file holds a secret and you can commit it with your project.

Add Fluveo MCP to your client#

The Fluveo MCP server is not available in production yet.

Check the connection#

Ask the agent to call get_account_info. It answers the store the key belongs to, or the store you picked on the consent page. account_id starts with mch_, and livemode is false, because the server works in test mode only.

get_account_info (first fields)
{
  "account_id": "mch_...",
  "livemode": false,
  "permissions": { "account": "read" }
}

When get_account_info is not in the agent's tools, the key or the connection has no Read permission on Account. Tools lists every tool and the permission it needs.

When it does not connect#

The server answers a refused request with an HTTP status, and a 401 also carries a JSON body with a code.

AnswerWhyWhat to do
401 api_key_requiredThe request carried no key or token. With an agent key, FLUVEO_MCP_KEY was empty in the shell that started the client. With OAuth, the client has not signed in yet.Export the key in that shell and start the client again, or start the client's sign-in.
401 authorization_repeatedThe request carried two or more Authorization headers, so the server read none.Send exactly one: Bearer and an OAuth access token or an agent key.
401 invalid_tokenThe OAuth access token expired, or the connection was revoked or ended.Start the client's sign-in again, such as /mcp in Claude Code.
401 agent_key_requiredThe key is a secret, publishable or live key, or a restricted test key made without This key is for an AI agent.Make an agent key in the Dashboard with This key is for an AI agent checked, or sign in with OAuth.
401 api_key_invalidNo store has this key.Copy the key again from the Dashboard, or make a new one.
401 api_key_expiredThe key expired or was revoked.Make a new agent key in the Dashboard.
403The request came with a browser Origin the server does not allow.Connect from a client that runs outside the browser.
406The Accept header leaves out application/json.Send Accept: application/json, or no Accept header.

Security explains what the server refuses and why.

Next#