Antigravity Mobile Command MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARTIFACTS_PATH | No | Path to the artifacts directory | ~/.gemini/antigravity/artifacts |
| TELEGRAM_BOT_TOKEN | Yes | Your Telegram bot token from @BotFather | |
| AUTHORIZED_CHAT_IDS | Yes | Your Telegram chat ID(s) (comma-separated for multiple) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_telegram_messageA | Send a message to the user via Telegram. Use for status updates, informational messages, or any communication that doesn't require approval. |
| request_plan_approvalA | Request approval for an implementation plan before making changes. Use this before modifying more than 3 files or making significant changes. The user will see the plan summary and can approve or reject. |
| request_change_approvalA | Request approval for specific code changes. Use for reviewing important modifications before they are committed. |
| send_artifactA | Send an artifact (screenshot, recording, or file) to the user via Telegram. Use after capturing UI screenshots or generating visual content. |
| update_statusA | Update the status ticker message. This edits the existing status message instead of sending a new one, reducing message spam. |
| notify_errorA | Send a critical error notification to the user. Use when terminal commands fail or errors occur that need user attention. |
| await_user_responseA | Wait for the user to respond with a message. Use when you need specific input or instructions from the user. |
| get_pending_promptsA | Check for pending prompts from the Telegram user. Call this when the user asks you to check telegram or at the start of a session. Returns any queued prompts that the user sent via the Telegram bot. |
| wait_for_new_promptA | Wait efficiently for a new prompt to arrive from Telegram. Blocks until a prompt is found or timeout is reached. Use this in a loop to monitor for incoming tasks. |
| read_project_fileA | Read the contents of a file from the current project. Use to report file contents back to Telegram or verify changes. |
| write_project_fileA | Write content to a file in the project. Creates parent directories if needed. Use for code modifications. |
| list_project_filesA | List files and directories in the project. Use to explore project structure or find files matching a pattern. |
| search_project_codeA | Search for code patterns in the project using grep. Returns matching files with line numbers and content snippets. |
| run_terminal_commandA | Run a terminal command in the project directory. Returns stdout, stderr, and return code. Use for builds, tests, etc. |
| get_project_contextA | Get information about the current project context. Returns project path, file counts by type, git status, and settings. |
| set_project_contextA | Set the current project path for IDE operations. All file operations will be relative to this path. |
| send_code_updateA | Send a code update notification to Telegram. Use after making significant code changes to inform the user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Tools are largely distinct, with clear semantic purposes for each communication or file operation. Some overlap exists between messaging tools (send_telegram_message vs send_code_update) and between prompt-waiting tools (await_user_response vs wait_for_new_prompt), but descriptions clarify intended use cases.
All tool names follow a consistent verb_noun pattern in lower_snake_case, making the API predictable and easy to navigate.
At 17 tools, the set is slightly large, but each tool addresses a distinct need in the mobile command workflow, covering both communication and project operations. It feels heavy but not bloated.
The toolset covers the core lifecycle of receiving prompts, exploring modules, editing files, running commands, and sending updates/approvals. Minor gaps exist (e.g., no dedicated delete file) but can be worked around via terminal commands.