Install the native BlockVectra MCP plugin in Antigravity

Install in one project

Run these commands from your project root:

mkdir -p .agents/plugins/blockvectra-docs
curl --fail --location https://raw.githubusercontent.com/blockvectra/mcp/antigravity-v0.1.0/plugin.json --output .agents/plugins/blockvectra-docs/plugin.json
curl --fail --location https://raw.githubusercontent.com/blockvectra/mcp/antigravity-v0.1.0/mcp_config.json --output .agents/plugins/blockvectra-docs/mcp_config.json

Start agy in that directory. For a first check, ask it to call search_docs with {"query":"Antigravity","lang":"en","limit":1}. Project-local loading and this single keyless documentation search were verified with Antigravity CLI 1.4.7.

The official plugin guide describes project-local and global installation. The commands above place the plugin in this project's .agents/plugins/ directory.

CLI-managed global installation

This walkthrough assumes Antigravity CLI is already installed and signed in. Install the BlockVectra plugin from its GitHub repository:

agy plugin install https://github.com/blockvectra/mcp

The plugin is named blockvectra-docs. It connects to https://docs.blockvectra.com/mcp over remote HTTP, so there is no local npm bridge to start or keep running. If you want to confirm what Antigravity recorded, the optional inventory command is:

agy plugin list --json

Check that the plugin appears as enabled and note its version and source. If the install command fails, fix that before relying on the plugin.

Check what the client loaded

For a CLI-managed installation, restart Antigravity, run /plugin to confirm blockvectra-docs is enabled, then /mcp to inspect the server and the tools it exposes. For the project-local setup, start Antigravity from that project directory and inspect /mcp.

Keep two levels of success separate. The lists in /plugin and /mcp confirm that the client registered and loaded the plugin; they do not prove the remote endpoint is reachable right now. The client's live server status shows whether the connection is up, and a tool has worked only when a call returns the data you asked for. Follow the client's normal tool permission prompts.

Run a keyless discovery check

Ask Antigravity to make two calls in plain language:

Call list_chains, then call read_doc with path=quickstart and lang=en.

A successful list_chains response confirms chain discovery. A successful read_doc response confirms documentation retrieval. Both are keyless. Connecting, reading docs, discovery, pricing, and status tools do not need an API key.

That does not make every RPC method keyless. Public methods vary by chain, so check the relevant chain's policy before assuming a call will run without credentials. Data API and account tools need your own key. Configure it only in your MCP client's private HTTP headers (x-api-key or Authorization); never put it in command arguments, tool arguments, or chat.

If /mcp does not list the server, check /plugin, the install output, and whether the client was restarted after install. If read_doc fails, check the path and lang arguments, then read the tool's error. For background and the full tool list, see the BlockVectra MCP server guide. Antigravity's own documentation covers plugins and MCP configuration.