Let your agent
keep itself funded
Colossus MCP lets your agent self-manage its credits and keys, with full control.
The process
Five tools, one loop.
An agent runs the whole cycle on the same code the dashboard uses.
01/05
Credits accrue
colossus_get_balanceA share of every trading fee, split across holders, every hour.
The agent creates a key
colossus_create_keyOne Colossus key that spends the balance live at the gateway. Nothing to top up, ever.
It watches the spend
colossus_get_key_statusEvery request is charged at the price OpenRouter states, and the balance is the quota.
Leaked, so it replaces it
colossus_create_keyA new secret; the old one stops in the same statement. The credit never moved.
Or it pulls the plug
colossus_revoke_keyOne call stops the key on the next request. The balance stays exactly where it is.
Register the endpoint, then run /mcp inside Claude Code. It marks the server as needing sign-in the moment our server answers 401, and opens the browser for you.
claude mcp add --transport http --scope user colossus https://colossus.network/api/mcp/mcp # pick colossus, then Authenticate--scope user is the point: credits belong to your account, not to one repository, so the agent can top itself up wherever it is working. Drop it to limit the connection to the current project.
Codex treats streamable-HTTP servers as first class and handles dynamic client registration and PKCE itself. Add the server, then log in once.
codex mcp add colossus --url https://colossus.network/api/mcpcodex mcp login colossus
# the same thing, written by hand[mcp_servers.colossus]url = "https://colossus.network/api/mcp"
The ChatGPT desktop app and the IDE extension read this same config, so signing in once covers all three.
Cursor takes a bare URL and does discovery, registration, PKCE and token storage on its own. No auth block, no header.
{ "mcpServers": { "colossus": { "url": "https://colossus.network/api/mcp" } }}
- 1Save the file. Cursor reloads MCP servers on save.
- 2Open Cursor Settings → MCP and find Colossus in the list.
- 3Click to sign in. The browser opens on the Colossus consent screen.
Use .cursor/mcp.json inside a repo instead if you want the connection scoped to one project.