prime-intellect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIME_API_KEY | Yes | Your Prime Intellect API key (starts with pit_) | |
| PRIME_MAX_TOTAL_USD | No | Hard cap on total spend in USD for a single pod | 40 |
| PRIME_MAX_HOURLY_USD | No | Hard cap on hourly spend in USD | 5 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_gpu_typesA | List every GPU type Prime Intellect currently offers (e.g. "H100_80GB", "A100_80GB"). Use this when the user is vague about what they want. Pass the result into list_availability or pod_quote. |
| list_availabilityA | List currently-available GPU pods that match the filters. Returns the SDK's GPUAvailability rows (cloud_id, gpu_type, gpu_count, prices, disk/vcpu/memory bounds, stock_status, ...). Use this to pick a target before pod_quote, or to show the user options. |
| get_wallet_balanceA | Return the current Prime Intellect wallet balance and recent billings. Use this to estimate how long a quoted pod can run, or to check why pod_create returned an insufficient-funds error. |
| pod_quoteA | Get a non-binding price quote + reserved provisioning payload. Returns a quote_token (TTL=60s) that you pass to pod_create with confirm=True to actually provision. This tool has NO side effects. The server picks the cheapest matching GPUAvailability row that satisfies the requested disk/vcpu/memory. If none matches, returns an error explaining what's available. |
| pod_createA | Provision a Prime Intellect GPU pod (or preview the provisioning). With confirm=False: returns a dry-run preview describing what would happen. With confirm=True: validates spend caps + quote freshness, then provisions. The server enforces:
On success, the pod is recorded in local state.json so pod_check_runaway can warn about overdue pods later. |
| pod_listA | List every pod the API key can see (active + provisioning + stopped). |
| pod_statusA | Get the current status (provisioning / active / failed) for a pod. With wait_for_ssh=True, blocks (polls every 5s) until ssh_connection is
available — that's when you can SSH in. Returns the SSH connection string
in |
| pod_terminateA | Destroy (terminate) a pod. Idempotent on already-deleted pods. Without confirm=True, returns a no-op preview so you can re-read your decision. |
| pod_check_runawayA | Return locally-tracked pods that have run past max_lifetime_hours OR whose accumulated cost is approaching PRIME_MAX_TOTAL_USD. Call this at the start of long-running sessions to catch forgotten pods. |
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 9 tools
Each tool has a unique and clearly distinct purpose, from wallet balance and GPU availability listing to pod creation, quoting, and termination. There is no overlap that could cause an agent to select the wrong tool.
Tool names follow a consistent pattern: utility functions use verb_noun (e.g., get_wallet_balance, list_availability) and pod operations all start with pod_ (e.g., pod_create, pod_terminate). The naming is predictable and easily understood.
With 9 tools covering wallet, GPU types, availability, pod lifecycle (create, list, status, quote, terminate), and runaway monitoring, the count is well-scoped for the server's purpose. Each tool earns its place with no redundancy.
The tool surface covers the full lifecycle of GPU pod management: discovering availability, quoting, creating, monitoring status, listing, terminating, and checking for runaway pods. The inclusion of wallet balance and wait-for-SSH functionality addresses common operational needs.