subspace-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TZ | No | Container timezone for log timestamps (e.g. America/New_York) | |
| PORT | No | Port the server listens on | 9595 |
| LOG_LEVEL | No | Logging verbosity (debug, info, warn, error) | info |
| AUTH_REALM | Yes | Keycloak realm name used for both incoming clients and the MCP OAuth client | |
| API_CLIENT_ID | Yes | OAuth client ID for token introspection against your IdP | |
| TRMNL_DB_PATH | No | Path to SQLite database file | ./trmnl.sqlite |
| ACTIVE_VERSION | No | API version prefix (not fully implemented) | v1 |
| MCP_SERVER_URL | Yes | The resource server URL — incoming tokens must include this in their audience claim | |
| AUTH_SERVER_URL | Yes | Base URL of the Keycloak (or compatible) authentication server | |
| TRMNL_CLIENT_ID | No | OAuth 2.0 client ID provided by TRMNL for your plugin (required for TRMNL plugins) | |
| API_CLIENT_SECRET | Yes | OAuth client secret for token introspection | |
| WMATA_PRIMARY_KEY | No | WMATA API key for DC Metro arrival predictions and incidents (required for metro plugin) | |
| AERODATABOX_API_KEY | No | RapidAPI key for AeroDataBox (live flight status data) (required for flight plugin) | |
| TRMNL_CLIENT_SECRET | No | OAuth 2.0 client secret paired with TRMNL_CLIENT_ID (required for TRMNL plugins) | |
| TRMNL_IP_ALLOW_PRIVATE | No | Set to true to bypass TRMNL worker IP allowlist check (useful for local dev) | |
| TRMNL_FLIGHTS_CLIENT_ID | No | OAuth 2.0 client ID for the TRMNL flight tracker plugin (required for flight plugin) | |
| ACTIVITY_DISCORD_CLIENT_ID | No | Discord OAuth client ID for the activity token exchange endpoint (deprecated) | |
| TRMNL_FLIGHTS_CLIENT_SECRET | No | OAuth 2.0 client secret paired with TRMNL_FLIGHTS_CLIENT_ID (required for flight plugin) | |
| ACTIVITY_DISCORD_CLIENT_SECRET | No | Discord OAuth client secret (deprecated) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/subtype-space/subspace-trmnl'
If you have feedback or need assistance with the MCP directory API, please join our Discord server