Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_modelsA

List configured endpoints (with live health + what they're serving now) and the model pool.

Pool entries that are currently reachable are marked `available: true` with the endpoint name
and the served id. Unavailable ones are the menu to ask the user for (by name, on `host`).
request_modelA

What to relay to the user to bring up a model that is not currently running.

Returns the pool entry's `host`/`notes` (and a start command only if one is on file). If the
model is already up, says so instead.
register_modelA

Add or update a model in the pool (persisted to models.yaml).

Only `name` is required: it is fuzzy-matched against served ids (alphanumerics, case-folded,
substring), so `qwen3.8-27b` finds `unsloth/Qwen3.8-27B-GGUF:UD-Q4_K_XL`. `host` and `notes`
are what gets relayed when asking the user to bring it up. The rest are overrides:
`served_name` (exact id or glob) when fuzzy matching is ambiguous, `endpoint` to prefer one,
`context` as a fallback window when the backend doesn't report one, `bring_up` a start command
(goes stale quickly; usually leave empty).
register_endpointC

Add or update an inference endpoint (persisted to models.yaml) and probe it.

`base_url` is the server root that exposes `/v1/messages`, e.g. `http://127.0.0.1:8080`.
`backend` is one of llama.cpp | vllm | ollama | other (informational).
run_agentA

Delegate a task to an agent on a local model. Returns a job id immediately.

The agent is a headless Claude Code session (Read/Edit/Write/Glob/Grep/Bash, project
CLAUDE.md, same working tree) whose API calls go to the local endpoint. Write the task like a
brief for a capable but junior engineer: what to do, where, how to verify, and what to report.

Args:
  task: The brief. Be explicit; local models follow less implicit context than Claude.
  model: Pool name (see list_models) or a served model id/glob. Default from models.yaml.
  endpoint: Force a specific endpoint; with no `model`, uses whatever it is serving.
  cwd: Working directory (default: this server's cwd, i.e. the current project).
  isolation: "none" (work in cwd, like a normal subagent) or "worktree" (fresh git worktree
    on branch local-agent/<job>; kept only if the agent changed something, reported in
    job.worktree with a diffstat). Use worktree for risky/large edits you want to review as a diff.
  wait_s: If > 0, block up to this many seconds and return the result when done (else job id).
  permission_mode: acceptEdits (default) | bypassPermissions | default | plan.
  max_turns: Cap on agent turns (default from models.yaml).
  allowed_tools: Override auto-approved tools.
  system_prompt_append: Extra instructions appended to the Claude Code system prompt.
  resume_job: Continue a previous job's session (same model) with `task` as the next message.
  timeout_s: Wall-clock cap for the job.
wait_jobA

Block up to timeout_s seconds for a job to finish; returns its status/result either way.

job_statusB

Current status, last activity, files touched, and result (if finished) of a job.

list_jobsA

List jobs from this server session (newest last).

job_logB

Tail of a job's human-readable transcript (assistant text, tool calls, results).

cancel_jobB

Cancel a running job (kills the headless Claude session).

local_completeA

One-shot completion on a local model, no tools, no agent loop. Cheap offload for summaries, drafts, classification, translation, boilerplate. Returns the text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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/ccebelenski/localagents'

If you have feedback or need assistance with the MCP directory API, please join our Discord server