rhodium11-mcp
rhodium11-mcp
MCP server for Rhodium11. Exposes 21 tools for managing projects, schedules, orders, wallet, and feedback through any MCP-compatible AI agent.
Quick Start
With Claude Desktop / Claude Code
Add to your MCP config:
{
"mcpServers": {
"rhodium11": {
"command": "npx",
"args": ["-y", "rhodium11-mcp"],
"env": {
"RH11_API_KEY": "cak_your_key_here"
}
}
}
}With Cursor
Add the same configuration to your Cursor MCP settings.
Configuration
Variable | Required | Default | Description |
| Yes | — | Customer API key ( |
| No |
| API base URL |
Tools (21)
Account
Tool | Description |
| Get account info |
| Update profile (first_name, last_name, company) |
| Get current pricing rates |
| Get subscription info |
Wallet
Tool | Description |
| Get wallet balance (credits + USD) |
| Get transaction history (paginated) |
Projects
Tool | Description |
| List projects (with marketplace/region/active filters) |
| Create a new project |
| Get project details |
| Pause/resume a project |
| Archive (soft delete) a project |
| Get daily stats (execution, SERP, ARA, BR, SQR, ranks) |
| Recommended daily quantities for the keyword, with range and over-spend flag |
| Research candidate keywords before creating projects (max 100/call) |
Schedule
Tool | Description |
| Get project schedule |
| Set full per-day schedule |
| Quick-set uniform daily volumes |
Orders
Tool | Description |
| List orders (paginated) |
| Get order details |
| Report an issue (max 5 per order) |
Feedback
Tool | Description |
| Submit feedback (10-5000 characters) |
Authentication
Authentication is handled automatically. The server exchanges your RH11_API_KEY for a JWT on the first tool call, proactively refreshes before expiry, and retries once on 401 errors. No manual token management needed.
Configuration
Env var | Default | Purpose |
| (required) | Customer API key (starts with |
|
| Override for staging or self-hosted backends. |
|
| Length (in days) of the SFB lock window surfaced via |
sfb_lock_info on schedule responses
rh11_schedule_get, rh11_schedule_set, and rh11_schedule_quick_set augment the response with an sfb_lock_info block when scheduled SFB units fall inside the lock window. The backend (mpux-flask) freezes the next N days of SFB once a project has active SFB running — this field surfaces how many units are committed and the earliest date you can change SFB freely. Informational only; the backend remains the authority.
Development
npm install
npm run build
npm testLicense
MIT