The Trench MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport protocol (stdio, http, or sse) | stdio |
| TRENCH_API_KEY | Yes | API key for Bearer token authorization | |
| TRENCH_API_URL | Yes | Base URL for the Trench simulation API |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test_api_connectionA | Test the connection to the Trench API server. Useful for debugging connectivity issues. |
| get_current_timeA | Get the current simulation time and real-world UTC time. |
| get_all_passesA | Get information about all passes defined in the scenario. Shows complete schedule of satellite passes over the ground station. |
| get_next_passA | Get information about the next upcoming satellite pass. Returns None if no future passes are scheduled. |
| wait_until_timeA | Wait until the simulation reaches a specific UTC time. Polls the simulation every 0.1 seconds until the target time is reached. Args: target_time_iso: Target UTC time in ISO format (e.g., "2025-09-15T17:30:00Z") |
| start_downlink_simpleA | Start a data downlink session with default parameters (no arguments required). Must be called during an active satellite pass. |
| stop_downlink_simpleA | Stop the current data downlink session (no arguments required). Returns complete downlink status including total data downloaded. |
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 7 tools
Each tool targets a distinct concern: connectivity, time, pass scheduling (all vs. next), waiting, and downlink start/stop. Although get_all_passes and get_next_pass are related, their names and descriptions make the difference immediately clear.
Tool names consistently follow a verb_noun pattern with snake_case, such as test_api_connection, get_all_passes, and start_downlink_simple. The pattern is predictable and uniform across the entire set.
Seven tools is an appropriate, focused scope for a satellite ground-station simulation/downlink server. Each tool covers a necessary operation without redundancy or bloat.
The tool set covers the full workflow: verifying connectivity, checking simulation time, discovering passes, waiting for the right moment, and starting/stopping downlinks. No critical dead ends are apparent for the stated domain.