CryptoPilot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPTRADE_USER_ID | No | SnapTrade user ID (required for SnapTrade provider) | |
| SNAPTRADE_CLIENT_ID | No | SnapTrade client ID (required for SnapTrade provider) | |
| COINBASE_API_KEY_NAME | No | Coinbase API key name (required for Coinbase provider) | |
| SNAPTRADE_USER_SECRET | No | SnapTrade user secret (required for SnapTrade provider) | |
| SNAPTRADE_CONSUMER_KEY | No | SnapTrade consumer key (required for SnapTrade provider) | |
| COINBASE_API_PRIVATE_KEY | No | Coinbase API private key (required for Coinbase provider) | |
| SNAPTRADE_DEFAULT_ACCOUNT_ID | No | Optional default account ID for SnapTrade quotes |
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 |
|---|---|
| list_providersA | List configured portfolio data providers and their capabilities. |
| list_accountsA | List canonical accounts from one configured provider or all configured providers. |
| list_holdingsA | List canonical holdings for an account from a configured provider. |
| get_quoteA | Get a canonical market quote for a symbol from a configured provider. |
| get_provider_healthA | Check health for one configured provider or all configured providers. |
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 5 tools
Each tool has a clearly distinct purpose: health checking, quoting, account listing, holdings listing, and provider listing. No overlaps or ambiguities.
All tool names follow a consistent 'verb_noun' pattern using lowercase with underscores. Verbs are either 'get' or 'list', making the set predictable.
With 5 tools, the server is well-scoped for a crypto portfolio data provider. Each tool covers a necessary function without bloat or thinness.
The set covers core read operations (health, quotes, accounts, holdings, providers) but lacks trading or transaction capabilities, which may be needed for a full crypto pilot tool.