robinhood-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBINHOOD_MCP_DB | No | Where durable jobs and the kill-switch state live. | ~/.robinhood-mcp/jobs.db |
| ROBINHOOD_MCP_MODULES | No | Comma-separated module names (market, orders, algo, portfolio, risk, journal, ops, dev), or `all`. Unset loads the default set. An unknown name fails startup. | the default set |
| ROBINHOOD_MCP_TICK_MS | No | Daemon supervisor tick interval, in milliseconds. | 5000 |
| ROBINHOOD_CRYPTO_API_KEY | Yes | API key issued by Robinhood when you register your public key at robinhood.com/account/crypto (web classic only). | |
| ROBINHOOD_CRYPTO_BASE_URL | No | Override the API host. There is no sandbox host to point this at. | https://trading.robinhood.com |
| ROBINHOOD_CRYPTO_BUY_ONLY | No | `1` rejects every sell order. | 0 |
| ROBINHOOD_CRYPTO_AUTONOMOUS | No | `1` executes immediately and ignores `confirm`. Spend caps still apply. | 0 |
| ROBINHOOD_CRYPTO_API_VERSION | No | API version to use: `v1` or `v2`. v2 adds fee-tier data. Any other value fails startup. | v1 |
| ROBINHOOD_CRYPTO_PRIVATE_KEY | Yes | Base64-encoded 32-byte Ed25519 seed matching the registered public key. Never a 64-byte expanded keypair, never PKCS#8. | |
| ROBINHOOD_CRYPTO_MAX_DAILY_USD | No | Cumulative per-process USD ceiling. In-memory; resets on restart. Unset means no cap. | |
| ROBINHOOD_CRYPTO_MAX_ORDER_USD | No | Hard per-order USD ceiling. Applies in every mode. Must be a positive number; fails closed if the USD value cannot be determined. | 100 |
| ROBINHOOD_CRYPTO_ENABLE_TRADING | No | Required for the trading server and the daemon. Must be exactly `1` for either to start; nothing else enables trading. | 0 |
| ROBINHOOD_CRYPTO_SYMBOL_ALLOWLIST | No | Comma-separated trading pairs, e.g. `BTC-USD,ETH-USD`. When set, only these may trade. Unset allows all pairs. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_setup_statusA | Report why this Robinhood server has no working credentials and what to set. Every other tool is unavailable until credentials are configured, so call this first if no trading or market-data tools are listed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly distinct: it reports setup status.
The single tool name 'get_setup_status' follows a clear verb_noun pattern, consistent with common MCP naming conventions. No inconsistencies are possible with only one tool.
A single setup-status tool is an extreme mismatch for a server named 'robinhood-mcp', which implies a full trading/market-data toolset. The description even acknowledges that other tools would exist but are unavailable, making the current surface trivially thin.
The server's apparent domain is Robinhood trading, but the only tool provides setup status and no actual trading or market data operations. This is severely incomplete and provides no way to accomplish any real task.