Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MODELNoOllama model name (alias for MCP_CU_MODEL)gpt-oss:20b
OLLAMA_URLNoOllama server URL (alias for MCP_CU_OLLAMA_URL)http://127.0.0.1:11435
MCP_CU_MODELNoOllama model namegpt-oss:20b
MCP_CU_CONFIGNoPath to TOML config file
MCP_CU_MAX_CHARSNoMax characters of window text to extract2000
MCP_CU_OLLAMA_URLNoOllama server URLhttp://127.0.0.1:11435
MCP_CU_HEALTH_HOSTNoHTTP health host127.0.0.1
MCP_CU_HEALTH_HTTPNoEnable HTTP health endpointfalse
MCP_CU_HEALTH_PORTNoHTTP health port8765
MCP_CU_MIN_FREE_MBNoMinimum free RAM in MB before unloading model (0 = off)2048
MCP_CU_TIMEOUT_MAXNoMaximum timeout in seconds60
MCP_CU_TIMEOUT_MINNoMinimum timeout in seconds8
MCP_CU_AGENT_CU_CMDNoCommand for agent-cuagent-cu
MCP_CU_MEMORY_WATCHNoEnable background memory watchertrue
MCP_CU_SESSIONS_DIRNoDirectory for session files<project>/.sessions
MCP_CU_TIMEOUT_BASENoBase timeout in seconds10
MCP_CU_COLD_LOAD_EXTRANoExtra timeout when model is cold-loading45
MCP_CU_KEEP_ALIVE_IDLENoKeep-alive for idle single call3m
MCP_CU_AGENT_CU_TIMEOUTNoTimeout for agent-cu in seconds20
MCP_CU_AUTOSTART_OLLAMANoEnable Ollama auto-start (local URL only)true
MCP_CU_SNAPSHOT_DETAILSNoEnable extra agent-cu snapshot for Claude detailstrue
MCP_CU_AUTOSTART_TIMEOUTNoOllama auto-start timeout in seconds10
MCP_CU_SESSION_TTL_HOURSNoSession file TTL in hours24
MCP_CU_KEEP_ALIVE_SESSIONNoKeep-alive for active session10m
MCP_CU_MAX_QUESTION_CHARSNoMax characters for question300
MCP_CU_SYSTEM_PROMPT_FILENoPath to system prompt filebundled prompts/system_prompt.md
MCP_CU_TIMEOUT_PER_1K_CHARSNoTimeout addition per 1000 characters4
MCP_CU_MEMORY_WATCH_INTERVALNoMemory watcher interval in seconds30
MCP_CU_SESSION_ACTIVE_MINUTESNoMinutes to consider a session active10

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
look_at_screenA

Ask ONE short English question about what a window on this computer shows; get short JSON back (windows_seen, status, summary, confidence, details, model_used, duration_seconds, memory_mb). details is filled by code: project, session, branch, next_step, failures, files, background_tasks when found. Read-only: never clicks or types. Pass app when known. For multi-part checks call step by step (status first, then details). On error, follow error.suggestion. client and session_id are OPTIONAL. Without them every call is independent: the full screen is re-read, no 'what changed' is possible and no file is written. With them the server keeps context between calls (more accurate, shorter answers, plus changed_since_last). Reuse the same pair for one task; sending a new session_id replaces the old one for that client. keep_warm (optional bool) keeps the model loaded 10 min instead of 3 when you will ask again soon. Call release_model() when your task is done.

pingA

Heartbeat: checks that this bridge works end to end. Confirms the server is up, makes sure the local Ollama is reachable (auto-starts it if needed) and asks the model for 'pong'. No screen reading. Returns {ok, server, ollama, model_reply_ok, model, seconds, cold, error?}. The first ping may take 30-50 s if the model is cold (not loaded); later pings take a few seconds.

release_modelA

Unload the local model now and return freed memory_mb. Call it at the end of your task (after your last look_at_screen) so the RAM is free again. Safe to call when nothing is loaded.

healthA

Check the backend before/after errors: Ollama reachable, model pulled and loaded, memory, free RAM, current keep_alive policy, agent-cu installed. Call this first if look_at_screen returns OLLAMA_UNREACHABLE or MODEL_NOT_FOUND.

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 4 tools

Disambiguation4/5

look_at_screen and release_model are clearly distinct, and ping vs health are separated by intent (lightweight heartbeat vs detailed backend diagnostic). However, both ping and health check Ollama reachability and model status, so an agent could reasonably hesitate between them in a failure scenario.

Naming Consistency3/5

Naming mixes bare nouns (ping, health) with verb_noun forms (look_at_screen uses verb_preposition_noun, release_model is verb_noun). It stays readable, but there is no single predictable pattern across the four tools.

Tool Count4/5

Four tools is a reasonable, tightly scoped set for a read-only screen-inspection bridge, with three of them being support/lifecycle helpers. It is on the thin side since only one tool performs the core action, but nothing is redundant filler.

Completeness3/5

For a server literally named 'computer-use', the surface is observation-only: no clicking, typing, window enumeration, or targeted reads beyond a single look_at_screen. The read-only lifecycle (ping, health, release_model) is well covered, but the domain name promises interaction the tool set does not deliver.

Maintenance

ActivityMaintained
ResponsivenessNo issues