jungle-grid-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUNGLE_GRID_API_KEY | Yes | Your Jungle Grid API key. Required for all API calls. | |
| JUNGLE_GRID_API_URL | No | URL of the Jungle Grid orchestrator. Defaults to https://api.junglegrid.dev | https://api.junglegrid.dev |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimate_jobA | Estimate routing, capacity source, and expected cost for a proposed Jungle Grid workload without submitting it. |
| submit_jobA | Submit a Jungle Grid workload for execution. This may start managed compute infrastructure and incur usage charges. |
| list_jobsA | List the authenticated user's Jungle Grid jobs, optionally filtered by status. Use this to find recent jobs before checking status, logs, or artifacts. |
| get_jobA | Retrieve current status and execution details for a specific Jungle Grid job belonging to the authenticated user. |
| get_job_logsB | Retrieve execution logs for a specific Jungle Grid job belonging to the authenticated user. |
| cancel_jobA | Cancel an existing Jungle Grid job. This may stop active execution and prevent further outputs. |
| list_artifactsA | List output artifacts associated with a specific Jungle Grid job. |
| get_artifactA | Retrieve download information for a specific output artifact from a Jungle Grid job. |
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 targets a distinct operation (submit, cancel, estimate, get status, get logs, list, get artifact, list artifacts) with no overlap. The separation between job management and artifact management is clear.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., cancel_job, get_artifact, list_jobs). The naming is predictable and easy to understand.
With 8 tools, the server provides a focused but complete set for managing Jungle Grid jobs. Each tool serves a necessary function without bloat or undersupply.
Covers the core job lifecycle (submit, get, list, cancel, estimate, logs, artifacts). Missing an update/retry tool for modifying job parameters, but the core workflow is well-supported.