Setup guide · 5 minutes
Connect the Livepeer Agent to Claude or Codex once. You log in with your email — no API key to paste, copy, or lose — and every image or video you make afterward runs on your own account.
Point your client at the Livepeer Agent's address. Pick your client below.
Open Settings → Connectors → Add custom connector, then paste this URL and save:
https://agent.livepeer.org/api/mcp
Claude Desktop handles the email login for you the first time you use a tool. Nothing else to configure.
In your terminal:
claude mcp add --transport http livepeer-agent \
https://agent.livepeer.org/api/mcpThe login opens automatically the first time you call a tool.
Open ~/.codex/config.toml and add this block. The mcp-remote bridge runs the browser sign-in for you:
[mcp_servers.livepeer_agent] command = "npx" args = ["-y", "mcp-remote", "https://agent.livepeer.org/api/mcp"]
Save the file and restart Codex. (npx comes with Node.js — install Node first if you don't have it.)
The first time you use a Livepeer tool, your browser opens the Livepeer sign-in page. Log in the way you normally do — email, or a provider like Google.
This is the whole point of the flow: you prove who you are once, and the client stores a session token behind the scenes. You never see or handle an API key. When the page says the login was captured, return to your client.
Back in the chat, ask:
“Call the me tool and tell me my account type.”
You want it to come back as a real account — not the keyless demo. That confirms the sign-in bound correctly and your usage will bill to you.
Ask for a quick, cheap image to prove end-to-end generation:
“Generate an image with flux-schnell: a single red maple leaf on white.”
You'll get back a link to a finished image in a few seconds. That render ran on the Livepeer network and drew a few tenths of a cent from your balance — you're live.
Quick reference for a healthy run — and how to read it if a step looks off.
| At this step | Healthy result | |
|---|---|---|
| Signing in | Browser lands on the Livepeer sign-in page, then a “login captured” message. | expected |
| The “me” check | Account type reads as a real / paid account. | expected |
| The “me” check | Says demo or “keyless”. | re-connect |
| Generating | A link to a finished image, plus a tiny cost. | expected |
| Generating | A payment / orchestrator error. | retry |
The three things people actually hit, and the one-line fix for each.
Your client can't reach the connector. Double-check the URL is exactly https://agent.livepeer.org/api/mcp (no trailing slash, no typo), then restart the client and try a tool again.
The client is sending no session — usually a duplicate, keyless copy of the connector registered alongside this one. Remove any other “Livepeer” entry, keep this one, and reconnect.
A model may be briefly unavailable. Ask for the same thing again, or try a different model (recraft-v4, nano-banana). If every model fails, the network is having a moment — wait a minute and retry.