Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGY_OBSERVER_CLINoAbsolute path to the official `agy` CLI executable to invoke (the desktop IDE cannot substitute for the CLI).
AGY_OBSERVER_ENABLEDNoExecution gate for model runs. When set to "0" model execution is disabled; set to "1" (and restart the MCP server) to allow agy_run to invoke the Antigravity CLI after confirming costs, working directory and execution authorization.0
AGY_OBSERVER_STATE_DIRNoAbsolute path to the private state directory where each run's status.json, events.jsonl and transcript.md are stored in plaintext.
AGY_OBSERVER_WORKSPACENoAbsolute path to the (recommended empty) workspace directory used when running the CLI.

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
agy_runA

Send one authorized request. participant: gemini/claude/codex (never client gpt); channel: antigravity/claude_code/codex_cli as supported. Default Gemini via Antigravity stays compatible. A channel override needs its explicit model; Claude requires Opus. Missing CLI/login fails without fallback/retry. May incur cost.

agy_historyA

List local history summaries and task previews. Use agy_status for full prompts and replies.

agy_statusB

Read one run's current or terminal status from the configured artifact directory.

agy_cancelA

Request cancellation of an active run owned by this server instance.

agy_discussion_createA

Create a local peer collaboration task with complementary duties and 1..8 attempt budget. No model call.

agy_discussion_readA

List task summaries when discussion_id is omitted; otherwise read roles, attributed messages, decisions, memory_versions, budget_versions, context manifests and linked runs. Memory/budget expected version is the history length (0 initially). No model call.

agy_project_readA

Read durable project memory, full current plan, independent participant views and lifetime usage across linked discussions. Omit project_id to list local projects. version reads a previous checkpoint; query searches bounded public excerpts; sources retrieves 1..12 exact discussion_id#message_id originals. No model call; sealed initial judgments are not exposed. Discussion history has separate message pagination. Provider sessions are not resumed or authenticated by this memory layer.

agy_project_updateA

Create/update a lasting project checkpoint. Create with expected_version=0, name and goal; otherwise read current version first. memory uses facts/disagreements/next_steps {text,sources} and positions {participant,view,reason,sources}, with project-qualified source strings discussion_id#message_id (successful, revealed, linked messages). Whole memory <=4500 UTF-16 units; plan <=4000 and needs plan_sources. Empty plan explicitly clears it. status=active/paused/completed controls project lifecycle; pausing blocks NEW calls, does not cancel active ones. Completed projects need explicit active update to resume. Checkpoints have no round/version-count expiry. capture_discussion_id retries local synchronization of an already linked task, never models. No automatic retries, model calls or credential migration.

agy_project_linkB

Explicitly link a local discussion to one lasting project. Binding is immutable and cannot cross another project. Default on_demand=true authorizes individually requested turns without a fixed lifetime round budget; it does not start any turn/loop or bypass client approvals, CLI limits or cancellation. Existing spent attempts remain usage records. on_demand=false retains that task's old budget. Save exact legacy snapshot before paging. Local client memory/plan updates are checkpointed into the project; model views retain actual provenance. Create a new normal discussion and link it to reuse the project across topics/sessions; archived discussions stay archived. No model call.

agy_discussion_memoryA

Replace the client-maintained working memory with a versioned snapshot, not inferred consensus. No model call. Read first; expected version is 0 initially. Linked project discussions also checkpoint this memory into their persistent project. memory has facts/disagreements/next_steps lists of {text,sources:[message ids]}, and positions list of {participant,view,reason,sources}. Each source must be a successful message; each position needs that participant's own source. At most 8 rows/section and 4500 UTF-16 units total. Keep disagreements and reasons, never invent verification. Full snapshot and current plan enter later discussion prompts; initial judgments stay isolated. Pending/closed tasks reject edits.

agy_discussion_extendA

Explicitly add 1..8 attempts to selected task remotes, at most 32 total per remote. Council keys are selected gemini/claude/codex; peer tasks use reviewer. Read first; expected version is 0 initially. Records before/after limits and reason; preserves spent attempts, roles, routes, memory and plan versions. Does not call/retry models, reopen archived tasks or start a loop. Failure/cancellation still consumes an attempt. Pending calls block changes; initial budget defaults stay unchanged.

agy_discussion_noteA

Submit a client proposal/question/answer/challenge/revision/feedback/decision/summary. An answer must reference the peer question. Decisions require reply_to and accepted/rejected/deferred; summary closes the task. Client authorship is not authenticated. No model call.

agy_discussion_turnA

Yield ONE authorized peer turn using bounded shared context. Instruction is optional; the peer may initiate questions or proposals, including the first turn. Failure/cancellation consumes an attempt; no automatic turns/retries. May incur cost and CLI side effects.

agy_discussion_recoverB

Reconcile interrupted messages or failed delivery with linked terminal runs. A failed message is restored only from a verified matching successful run, retaining recovery audit. Never retries models or refunds attempts.

agy_council_createA

Create a task with 2..4 selected participants including client gpt; defaults remain gpt/gemini/claude. Optional codex is an independent Codex CLI participant. routes maps each remote participant to {channel, model}; Claude requires Opus. Snapshots prevent implicit route/model changes. Unlinked tasks start with 1..8 attempts per remote (default 2, including initial judgment); explicitly link a lasting project with agy_project_link for on-demand collaboration without a lifetime round cap; agy_discussion_extend can explicitly add more without a model call. Prefer project for new projects: client first READS relevant files/docs, supplies stage/materials (source + observed contents)/success_criteria/constraints/unknowns, total <=3000 UTF-16 units. Collect all selected project understandings, reveal, then select roles with agy_council_assign_roles. Do not also preassign roles. Without project, legacy roles map remains supported. No model call or arbitrary project file reading.

agy_council_assign_rolesA

After project understanding/reveal, choose complementary roles for this task's selected participants (gpt is client, codex is external), then assign them. Each spec needs role (<=80), focus/output (<=200 each), reason (<=300 UTF-16 units). Initial sources must include all selected initial understandings. Explain choice/tradeoffs in rationale, preserve unresolved differences. No peer endorsement is inferred. Revision needs current expected_role_version, sources and rationale; may update project brief fields. Appends history and generates role prompts, never rewrites old contributions or budgets. Client applies GPT prompt; no new GPT call, model call or automatic turn.

agy_council_noteC

Submit GPT/client public contribution. During collect use initial with honest context declaration (not authenticated). Later revision needs reason+references; support needs grounds+references; plan needs sources+expected version; summary archives without consensus. No model call.

agy_council_roundB

Explicitly call up to two selected remote participants via their stored channels (default first two task remotes). No call is made for client gpt. Codex CLI may be selected independently. Separate attempt budgets; no retries/loop. Collect uses only original material, disallows leading focus, and keeps replies sealed. Later batch shares a pre-call snapshot with full current plan, current task memory and each participant's own last successful contribution. Recent history/questions remain bounded; consult context manifests. May incur cost; CLI tools are not forcibly disabled.

agy_council_revealB

Publish all three successful initial judgments together and enable shared discussion. No model call. Sealing is workflow isolation, not a local access-control boundary.

agy_infoA

Report non-secret configuration, version, and execution gate; does not inspect CLI authentication.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 20 tools

Disambiguation3/5

The set has several parallel read/note/create/execute tools across discussion, council, project, and run workflows. Descriptions help distinguish them, but an agent must carefully choose between similar pairs such as discussion_note vs council_note, discussion_read vs project_read, and discussion_create vs council_create.

Naming Consistency4/5

Nearly all tools use a consistent agy_ prefix and snake_case resource/action naming, e.g. agy_discussion_read, agy_council_round, agy_project_update. A few names are noun-only or less action-explicit, such as agy_run, agy_history, agy_status, and agy_info, but the overall pattern is predictable.

Tool Count3/5

At 20 tools, the surface is heavy and sits in the borderline range. The domain is genuinely complex, but the count is inflated by two parallel workflows (discussion and council) with analogous operations, making the set feel broader than necessary.

Completeness4/5

The surface covers creation, reading, notes, turns/rounds, recovery, extension, memory, project linkage, status, cancellation, and configuration. Coverage is strong, with only minor lifecycle gaps such as explicit deletion/archival controls beyond summary or status transitions.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues