Skip to main content
Glama
Zythenth

Antigravity MCP Bridge

by Zythenth

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGY_PATHNoCaminho do CLI oficialagy
MAX_COPY_BYTESNoMáximo de bytes copiados (256 MiB)268435456
MAX_COPY_FILESNoMáximo de arquivos selecionados para a cópia10000
MAX_PROMPT_CHARSNoTamanho máximo do prompt50000
MAX_QUEUED_TASKSNoTarefas aguardando20
EVENT_BUFFER_SIZENoEventos mantidos em memória2000
MAX_CHANGED_FILESNoMáximo de arquivos alterados para revisão e integração100
MAX_RETAINED_TASKSNoTarefas persistidas retidas100
COPY_RETENTION_HOURSNoPrazo de retenção das cópias finalizadas168
MAX_CONCURRENT_TASKSNoProcessos simultâneos1
FORBIDDEN_DIRECTORIESNoDiretórios bloqueados, separados por `;` no Windows
BRIDGE_STATE_DIRECTORYNoDiretório privado de tarefas e sessões~/.antigravity-mcp-bridge
DEFAULT_TIMEOUT_SECONDSNoPrazo máximo por execução1800

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
antigravity_healthB

Inspect installed agy version, authentication and supported capabilities.

antigravity_list_modelsB

List model IDs actually returned by agy models for this account.

antigravity_get_modelA

Return the default model selected for subsequent bridge tasks. Null means agy chooses its own default.

antigravity_usageA

Consolidate final CLI usage by retained task, session and requested model. Resumed task counters are session deltas, not repeated cumulative totals. Missing counters stay null. This does not report account quota or billing; disclose partial or unavailable usage to the user.

antigravity_list_project_filesB

List tracked and untracked files excluding Git ignore and local exclude matches.

antigravity_set_modelA

Persist an exact model ID from agy models as the bridge default. Null persists Auto (agy default), overriding BRIDGE_DEFAULT_MODEL. Does not alter agy global settings.

antigravity_runB

Copy non-ignored project files to a temporary directory and run agy --sandbox there. includePaths narrows copied files or folders. Returns a taskId; source is unchanged.

antigravity_resumeC

Continue a completed session in its existing isolated copy.

antigravity_previewC

Return A/M/D files, per-file line statistics, totals, binary markers, patch, SHA-256 and client-reported test evidence with stale markers. Requires a finished task.

antigravity_read_patchA

Read at most 50000 UTF-16 units of the current patch, optionally selecting a changed path. Bind every read to the full preview hash. Follow nextOffset until hasMore is false. Use preview with includePatch false for metadata.

antigravity_read_resultA

Read the final CLI result serialized as JSON in bounded chunks. Returns ready false while active. Keep contentSha256 for subsequent requests and reconstruct the JSON by concatenating text.

antigravity_verifyB

Check actual artifacts and ground Codex review quotes in file lines. Requires criteria defined before the task. A CLI SUCCESS or unsupported claim is not verification; client review remains client-reported.

antigravity_testA

Start an asynchronous continuation that executes an exact command through agy run_command. Captures actual output, exit status and file fingerprints. Optionally permits up to three repair retries. No Docker or host execution fallback. Use the returned taskId for events, result, review and integration.

antigravity_record_testA

Record a test already executed by the client in the isolated copy. Bind command, exit code and output to the reviewed patch. These are client-reported results; the bridge does not execute or independently verify the command. Do not include secrets in output.

antigravity_integrateA

Request human confirmation through MCP form elicitation, then apply the reviewed patch. Requires the SHA-256 from antigravity_preview. Clients without form elicitation cannot integrate; no tool argument substitutes for user confirmation.

antigravity_discardA

Delete the copy and baseline of a finished task, including resumed tasks sharing that copy. Active copies are refused. The source project is preserved.

antigravity_cleanupA

Remove finished copies older than COPY_RETENTION_HOURS. Active copies are preserved.

antigravity_statusB

Return task metadata, status, process ID and isolated copy path when available.

antigravity_tasksA

Recover task IDs and metadata from local bridge state, including tasks from earlier server processes.

antigravity_eventsB

Read live normalized agy events after a sequence cursor. Includes original agy event payloads.

antigravity_resultA

Return terminal result, usage and error once the task finishes. Use antigravity_preview for the patch.

antigravity_cancelA

Cancel a queued task or terminate its local agy process.

antigravity_sessionsA

List conversation IDs recovered from local persisted tasks. agy does not advertise a session-list command.

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

Disambiguation4/5

Tools generally target distinct lifecycle stages (run/resume/cancel, preview/read_patch/read_result, test/verify/integrate), but several reading/status tools have adjacent purposes. The descriptions help separate result vs read_result and preview vs read_patch, though an agent could still confuse them.

Naming Consistency4/5

All tools consistently use the antigravity_ prefix with snake_case, which makes the set predictable. Most names are verb_noun or verb_noun-phrase, but some are noun-only query tools (usage, status, tasks, events, result, sessions), a minor deviation from a strict pattern.

Tool Count3/5

23 tools is heavy for a single MCP server and sits in the borderline 16-25 range. The domain is complex, but several output-reading and status tools could be consolidated, making the surface feel somewhat over-scoped.

Completeness4/5

The surface covers model selection, task lifecycle, file listing, patch/result reading, testing, verification, integration, and cleanup. Minor gaps exist, such as no explicit authentication/login tool or direct source-file read outside task artifacts, but core workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues