Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TRANSPORTNoTransport backend (local-relay, future: tailscale)local-relay
RELAY_REGISTRY_DIRNoDirectory containing registration JSON files~/.local/share/opencode-relay
DISCOVERY_INTERVAL_MSNoHow often to refresh instance list (ms)30000
HEALTH_CHECK_TIMEOUT_MSNoTimeout for health-checking each instance (ms)3000
OPENCODE_SERVER_PASSWORDNoHTTP Basic auth password for opencode instances
OPENCODE_SERVER_USERNAMENoHTTP Basic auth usernameopencode

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
instancesA

List all connected opencode instances with their current status (busy/idle). Call this to see what machines are available.

sendB

Send a message to the most recent opencode session on an instance. Streams the response back in real-time. Set abort=true to stop a running task instead of sending a message.

readA

Read the last few messages from the most recent opencode session on an instance. Use this to see what has been happening without sending a new message.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing instances, reading session history, and sending messages. No overlap or ambiguity.

Naming Consistency4/5

All tool names are lowercase and concise, but 'instances' is a noun while 'read' and 'send' are verbs, creating a slight pattern inconsistency.

Tool Count5/5

Three tools cover the essential operations for interacting with opencode instances (list, read, send) without unnecessary bloat.

Completeness4/5

Core workflows are covered, but there is no tool to select a specific instance or start a new session, which are minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues