Skip to main content
Glama
Antigravity Mobile Command MCP Server

Antigravity Mobile Command MCP Server

by JacksonFuck

šŸš€ Antigravity Mobile Command

Transform your mobile device into a remote Mission Control for your coding environment.

Antigravity Mobile Command is an "Agentic Bridge" that leverages Google Antigravity's native Model Context Protocol (MCP) and Artifact system to provide a bi-directional, real-time feedback loop via Telegram.

Telegram Bot Preview

✨ Features

  • šŸ“± Prompt-to-Action Loop: Send coding tasks from your phone, approve plans with inline buttons

  • šŸ“ø Visual Verification: Auto-receive screenshots and recordings of UI changes

  • āœ… Interactive Governance: Approve or reject code diffs via Telegram buttons

  • 🚨 Error Awareness: Get notified of terminal crashes with full stack traces

  • šŸ“Š Live Status Ticker: Real-time progress updates without message spam

Related MCP server: mcp-telegram-claudecode

šŸ› ļø Quick Start

Prerequisites

Installation

# Clone the repository
git clone https://github.com/yourusername/antigravity-telegram.git
cd antigravity-telegram

# Install dependencies
pip install -e .

# Or with uv
uv pip install -e .

Configuration

  1. Copy the example environment file:

cp .env.example .env
  1. Edit .env with your credentials:

TELEGRAM_BOT_TOKEN=your_bot_token_from_botfather
AUTHORIZED_CHAT_IDS=your_chat_id
ARTIFACTS_PATH=~/.gemini/antigravity/artifacts

Running

Run both Telegram bot and MCP server:

python -m src.main

Run only the Telegram bot:

python -m src.main --mode bot

Run only the MCP server (for Antigravity integration):

python -m src.main --mode mcp

šŸ”Œ Antigravity MCP Integration

1. Add to MCP Config

Add the Telegram bridge to your Antigravity MCP configuration (~/.gemini/mcp_config.json):

{
  "mcpServers": {
    "telegram-bridge": {
      "command": "python",
      "args": ["-m", "src.main", "--mode", "mcp"],
      "cwd": "/path/to/antigravity-telegram",
      "env": {
        "TELEGRAM_BOT_TOKEN": "your_token",
        "AUTHORIZED_CHAT_IDS": "your_chat_id",
        "ARTIFACTS_PATH": "~/.gemini/antigravity/artifacts"
      }
    }
  }
}

2. Copy the Workflow

Copy the workflow file to your Antigravity workflows:

cp workflows/mobile-command.md ~/.agent/workflows/

3. Use from Telegram

  1. Start a chat with your bot on Telegram

  2. Send /start to verify the connection

  3. Send /prompt "Your coding task here"

  4. Approve plans and review changes from your phone!

šŸ“± Telegram Commands

Command

Description

/start

Show welcome message and verify connection

/prompt <text>

Send a coding task to Antigravity

/status

Check current execution status

/cancel

Cancel the current operation

/help

Show help message

šŸ”§ MCP Tools Available

The following tools are exposed to Antigravity for communication:

Tool

Description

send_telegram_message

Send messages to the user

request_plan_approval

Request approval for implementation plans

request_change_approval

Request approval for code changes

send_artifact

Send screenshots/recordings to Telegram

update_status

Update the status ticker message

notify_error

Send critical error notifications

await_user_response

Wait for user input

šŸ—ļø Architecture

ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”     ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”     ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│  šŸ“± Telegram    │◄───►│  šŸŒ‰ Python       │◄───►│  🌌 Antigravity │
│     App         │     │     Bridge       │     │     Agent       │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜     ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜     ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜
                               │
                               ā–¼
                        ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
                        │  šŸ“ Artifact     │
                        │     Watcher      │
                        ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

šŸ“ Project Structure

antigravity-telegram/
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ main.py              # Entry point
│   ā”œā”€ā”€ config.py            # Configuration management
│   ā”œā”€ā”€ bot/
│   │   ā”œā”€ā”€ handlers.py      # Telegram command handlers
│   │   ā”œā”€ā”€ keyboards.py     # Inline keyboard builders
│   │   └── message_queue.py # Async message queue
│   ā”œā”€ā”€ mcp_server/
│   │   ā”œā”€ā”€ server.py        # MCP server implementation
│   │   ā”œā”€ā”€ tools.py         # MCP tool definitions
│   │   └── state.py         # Approval state management
│   ā”œā”€ā”€ monitors/
│   │   ā”œā”€ā”€ artifacts.py     # Artifact directory watcher
│   │   └── terminal.py      # Terminal output monitor
│   └── utils/
│       └── formatting.py    # Message formatting
ā”œā”€ā”€ config/
│   └── mcp_config.json      # MCP config template
ā”œā”€ā”€ workflows/
│   └── mobile-command.md    # Antigravity workflow
ā”œā”€ā”€ .env.example
ā”œā”€ā”€ pyproject.toml
└── README.md

šŸ”’ Security

  • Only authorized chat IDs can interact with the bot

  • Bot tokens are stored in environment variables

  • Session files are gitignored

šŸ“ License

MIT License - see LICENSE for details.

šŸ¤ Contributing

Contributions are welcome! Please feel free to submit a Pull Request.


Built with ā¤ļø for the Antigravity community

Available Tools

17 tools
await_user_responseA

Wait for the user to respond with a message. Use when you need specific input or instructions from the user.

Inputs: prompt (required), timeout_seconds.

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.

Inputs: clear_after_read.

get_project_contextA

Get information about the current project context. Returns project path, file counts by type, git status, and settings.

Inputs: no named parameters.

list_project_filesA

List files and directories in the project. Use to explore project structure or find files matching a pattern.

Inputs: pattern, directory, recursive.

notify_errorA

Send a critical error notification to the user. Use when terminal commands fail or errors occur that need user attention.

Inputs: error_message (required), command, stack_trace.

read_project_fileA

Read the contents of a file from the current project. Use to report file contents back to Telegram or verify changes.

Inputs: file_path (required), end_line, start_line.

request_change_approvalA

Request approval for specific code changes. Use for reviewing important modifications before they are committed.

Inputs: change_summary (required), diff_preview.

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.

Inputs: plan_summary (required), task_name, files_affected.

run_terminal_commandA

Run a terminal command in the project directory. Returns stdout, stderr, and return code. Use for builds, tests, etc.

Inputs: command (required), timeout.

search_project_codeA

Search for code patterns in the project using grep. Returns matching files with line numbers and content snippets.

Inputs: query (required), file_types, max_results.

send_artifactA

Send an artifact (screenshot, recording, or file) to the user via Telegram. Use after capturing UI screenshots or generating visual content.

Inputs: artifact_path (required), caption.

send_code_updateA

Send a code update notification to Telegram. Use after making significant code changes to inform the user.

Inputs: summary (required), file_path (required), change_type (required), diff_preview.

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.

Inputs: message (required), priority.

set_project_contextA

Set the current project path for IDE operations. All file operations will be relative to this path.

Inputs: project_path (required).

update_statusA

Update the status ticker message. This edits the existing status message instead of sending a new one, reducing message spam.

Inputs: status_text (required), progress_percent.

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.

Inputs: timeout_seconds.

write_project_fileA

Write content to a file in the project. Creates parent directories if needed. Use for code modifications.

Inputs: content (required), file_path (required), create_dirs.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lower_snake_case, making the API predictable and easy to navigate.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables remote control of AI coding assistants (Claude Code/Codex) via Telegram, allowing you to manage long-running tasks, send commands, and receive notifications from anywhere. Supports unattended mode with smart polling for up to 7 days and multi-session management.
      8
      25 PyPI
      30
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote control of Claude Code through Telegram, letting users start or resume sessions, review tool calls with approve/deny buttons, and manage long-running work from a phone.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a Telegram account through the same commands as the terminal client: messaging, chat management, voice transcription, calls, stickers, and privacy settings.
      1
      MIT