Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चA JetBrains plugin that bridges the Antigravity CLI
(agy) with JetBrains IDEs (IntelliJ IDEA, PhpStorm, WebStorm, PyCharm, GoLand,
and other IntelliJ-based IDEs) so the agent can see your active file, selection,
open tabs, and inspection diagnostics on demand.
Not the official Google extension. This is an independent, third-party plugin. Google's own Antigravity agent installs from JetBrains AI → Settings → Agents and requires IDE 2026.2.1+ — see Google's official setup guide. If that is what you are looking for, use it. This plugin serves a different purpose: it runs the Antigravity CLI (
agy) in an IDE terminal and feeds it editor context over MCP, on IDE 2023.2 and up, with no JetBrains AI dependency.
The plugin exposes four MCP tools to agy:
When you click the Open Antigravity CLI toolbar button, agy launches in
an IDE-embedded terminal already wired to the current project — no manual
configuration steps. By default the button focuses the existing Antigravity
terminal tab if one is open; toggle Always open a new tab in settings to
spawn a fresh session on every click.
agy (or
agy.exe on Windows) on $PATH, then in ~/.local/bin, /opt/homebrew/bin,
and /usr/local/bin. You can override the location in the plugin settings.nc are required.antigravity-companion-<version>.zip (see
Building from source if you don't have one).See Building from source.
Open Settings → Tools → Antigravity CLI Companion.
agy binary the plugin
should launch. Leave blank to auto-detect ($PATH + common install dirs).
The settings panel tells you which path it currently resolves to.agy session.agy under a non-xterm terminal name so it stops
emitting CSI Z, which the IDE's terminal emulator ignores. See
Prompt editing workaround. Turn it off if you
run ssh or containers from inside agy and need TERM passed through
unchanged.agy with --dangerously-skip-permissions, so it runs shell
commands and other tool calls without stopping to ask — the closest thing it
has to an auto mode. Only affects sessions started from this IDE: an agy
you launch in a plain terminal is unchanged, and nothing is written to
agy's own configuration. Two things still stop for you regardless — admin
escalation always prompts, and access outside the workspace root stays
governed by agy's own allowNonWorkspaceAccess setting. Takes effect for
the next session you open; terminal tabs already running keep the mode they
started with. Leave it off unless you are watching the session.agy sessions are
still supported regardless of how the action is triggered.No other configuration is required. The plugin manages
~/.gemini/config/mcp_config.json on its own and cleans up after itself when
projects close.
agy to see.⇧⌘A / Ctrl+Shift+A).agy running. Ask it about your code — when it
needs context it will call the plugin's MCP tools transparently.A useful first prompt: "What file am I looking at? Use ide_get_active_editor."
agy reads MCP server definitions from ~/.gemini/config/mcp_config.json. On
project open the plugin:
127.0.0.1:<random> (line-delimited MCP
over a plain TCP socket).jetbrains-mcp-bridge-<productCode>-<projectHash>.sh on Unix or .bat on
Windows — under ~/.gemini/antigravity-cli/. <productCode> is the
JetBrains IDE code (iu, ps, ws, py, go, …) so two IDEs opening
the same project don't collide. The script uses the IDE's bundled JBR to
run a tiny pure-Java stdio↔TCP relay, so agy (which speaks stdio MCP)
can reach the in-IDE TCP server with no external dependencies.mcp_config.json under
mcpServers.jetbrains-companion-<productCode>-<projectHash> (preserving
any other entries).On project close it removes the config entry and deletes the bridge script.
┌────────────────────┐ stdio ┌──────────────────┐ TCP ┌─────────────────┐
│ agy CLI (terminal) │ ─────────► │ bridge script │ ───────► │ Plugin MCP svr │
│ │ ◄───────── │ (JBR StdioBridge)│ ◄─────── │ (in JetBrains) │
└────────────────────┘ └──────────────────┘ └─────────────────┘
The "Open Antigravity CLI" button shows a notification "agy executable
not found".
Open Settings → Tools → Antigravity CLI Companion and set the path explicitly,
or install agy to one of the auto-detected locations.
agy answers "I don't have visibility into your IDE".
The plugin probably isn't registered. Check:
idea.log for MCP server listening on 127.0.0.1:<port>.~/.gemini/config/mcp_config.json contains a jetbrains-companion-* entry.agy log shows Connection refused or socket errors on startup.
The IDE (or that project) closed while agy was still running. Quit agy and
relaunch it from the toolbar button — the plugin re-registers a fresh port
each time a project opens.
mcp_config.json is corrupted.
Delete it; the plugin will recreate it on the next project open.
Editing in the middle of the agy prompt garbles the text.
Make sure Fix prompt editing in the IDE terminal is enabled under
Settings → Tools → Antigravity CLI Companion, then open a new Antigravity tab —
the terminal name is chosen when the session starts. See below for what is
actually going on.
agy is a charmbracelet (Bubble Tea) TUI whose renderer picks the cheapest
encoding for each cursor move: backspace for one column, CSI n D for a few,
and CSI Z — CBT, cursor backward tabulation — to jump back by tab stops.
JediTerm, the emulator behind both the classic and the reworked JetBrains
terminal, parses CSI Z but does not implement it: it falls through to the
default branch, logs Unhandled Control Sequence and does nothing. The cursor
silently stays put while agy believes it moved, so the next repaint — which
writes <new char><rest of line> and then walks the cursor back — lands several
columns too far right and paints the tail of the line over itself.
agy's own buffer is never wrong, which is why the text looks correct again the
moment you submit it. Switching terminal engines in Settings does not help
(TerminalStarterEx extends TerminalStarter, whose createEmulator() returns
a JediEmulator).
You can confirm the gap in any terminal — the * belongs at column 9:
printf 'ABCDEFGHIJKLMNOPQRSTUVWXYZ\r\033[17G\033[Z*\n'
A working terminal prints ABCDEFGH*JKLMNOPQRSTUVWXYZ; JetBrains prints
ABCDEFGHIJKLMNOP*RSTUVWXYZ.
agy enables the tab optimisation purely on TERM carrying an xterm prefix —
the terminfo database is never consulted, so cancelling cbt on an
xterm-named entry changes nothing. The plugin therefore launches agy under a
terminal name that is not xterm*: a private agyterm-256color entry
(literally xterm-256color under a different name, compiled into ~/.terminfo
on first use) so anything agy spawns still gets exactly the xterm key
encodings it expects, falling back to nsterm-256color from the standard
ncurses database when tic is unavailable. The byte cost is unmeasurable, and
alt-screen, kitty keyboard and bracketed paste all still negotiate.
The -256color suffix is load-bearing, not cosmetic. The IDE terminal exports
TERM=xterm-256color and no COLORTERM, so TERM is the only signal agy has
for colour depth. Its detector (charmbracelet/colorprofile) splits TERM on
- and matches the parts against a fixed table; a bare agyterm matches
nothing and drops agy to the 16-colour ANSI profile, where its greys and
slates collapse onto the nearest ANSI colour and the whole UI turns blue. Only
the first part is tested for the xterm prefix, so <name>-256color keeps the
full palette and keeps CSI Z suppressed. If you rename the entry, keep the
suffix.
agy's light/dark palette is a separate matter and is not something the plugin
sets: it comes from colorScheme in ~/.gemini/antigravity-cli/settings.json,
changed via /settings → Color Scheme. JediTerm does not answer OSC 11
background-colour queries, so agy cannot detect your IDE theme on its own —
pick the scheme that matches it.
The real fix belongs in JediTerm, where Tabulator.previousTab(int) is already
implemented in JediTerminal$DefaultTabulator and called by nothing.
JAVA_HOME must
point at it.platformVersion in gradle.properties.git clone https://github.com/matasarei/antigravity-companion.git
cd antigravity-companion
./gradlew buildPlugin
The signed (unsigned in dev) plugin archive will be at:
build/distributions/antigravity-companion-<version>.zip
Install it via Settings → Plugins → ⚙ → Install Plugin from Disk….
./gradlew runIde # launch a sandbox IDE with the plugin pre-loaded
./gradlew verifyPlugin # IntelliJ Plugin Verifier — static checks
./gradlew clean buildPlugin # full rebuild
./gradlew runIde is the fastest dev loop: it starts a fresh sandbox IDE,
side-loads the plugin, and tears down on exit. Edit code, rerun, repeat.
src/main/
├── java/dev/matasar/antigravity/bridge/
│ └── StdioBridge.java ← pure-Java stdio↔TCP relay
└── kotlin/dev/matasar/antigravity/
├── action/StartSessionAction.kt ← toolbar button
├── service/AntigravityCompanionService.kt ← MCP server + tool impls
├── settings/AntigravitySettings.kt ← persistent state
├── settings/AntigravitySettingsConfigurable.kt ← Settings panel
├── terminal/TerminfoCompat.kt ← JediTerm CSI Z workaround
└── startup/AntigravityStartupActivity.kt ← eager-init on project open
src/main/resources/
├── META-INF/plugin.xml ← plugin manifest
└── icons/ ← toolbar / plugin icons
build.gradle.kts, gradle.properties, settings.gradle.kts
\\wsl.localhost\<distro>\...), the plugin cannot spawn a Linux agy binary directly. The only supported workaround is to run the JetBrains IDE itself inside WSL2 (e.g. using JetBrains Gateway or WSLg) and install the plugin and agy inside WSL.agy
mid-conversation; agy calls back over MCP when it decides it needs IDE
state.jetbrains-companion-<productCode>-<projectHash> entry. A running agy in
workspace A will also see workspace B's tools in its catalog; only the live
project's bridge succeeds, but the duplicate tool names can confuse the
model.MIT — see LICENSE.
JetBrains IDE plugin that connects the Google Antigravity CLI (agy) to IntelliJ-based IDEs via MCP — gives the agent your active file, selection, open tabs, and inspection diagnostics on demand.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Antigravity Companion stdio पर लोकल चलता है।
पिछली जाँच 2026-10-28 को हुई। JetBrains IDE plugin that connects the Google Antigravity CLI (agy) to IntelliJ-based IDEs via MCP — gives the agent your active file, selection, open tabs, and inspection diagnostics on demand.