AI Galaxy Compute MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_GALAXY_STATE_DIR | No | Directory for state files (optional) | |
| AI_GALAXY_ACCESS_KEY | No | Your access key for AI Galaxy | |
| AI_GALAXY_SECRET_KEY | No | Your secret key for AI Galaxy | |
| AI_GALAXY_CREDENTIALS_FILE | No | Path to a JSON file containing access_key and secret_key (permissions 0600) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| balanceA | Read-only account balance and credit summary. |
| catalogA | List compact current CPU specs and GPU offers; no billable action. |
| plan_rentalB | Select and quote compute, storing a private signed plan; never creates. |
| rentB | Create exactly one instance from a stored plan. Billable; confirm must be true. |
| get_instanceA | Get redacted instance/connection status, optionally waiting until running. |
| plan_releaseA | Quote release for an instance created by this MCP; does not release. |
| releaseA | Release an MCP-owned instance. Destructive; confirm must be true. |
| cleanup_kept_diskB | Permanently release any retained disk for an MCP-created instance. |
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 8 tools
Each tool addresses a distinct operation: read-only queries (balance, catalog), planning (plan_rental, plan_release), lifecycle (rent, release, get_instance), and disk cleanup (cleanup_kept_disk). No two tools overlap in purpose.
Tools mix naming conventions: some are single words (balance, catalog, release, rent) while others use verb_noun (cleanup_kept_disk, get_instance, plan_release, plan_rental). The pattern is not uniform, causing some inconsistency.
With 8 tools, the set covers account info, catalog browsing, instance planning, creation, status, deletion, and disk cleanup. The number is appropriate for the domain without feeling sparse or bloated.
The set covers core instance lifecycle and billing but lacks a way to list all instances (only get_instance for a specific one) and no update operations. This leaves some gaps for workflow automation, though not severe.