Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xysq.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use the xysq MCP server in Google Antigravity — Google’s agent-first IDE — so the agent can call xysq tools for memory and identity-aware context. Antigravity is built on a VS Code fork and supports remote MCP servers over HTTP with bearer-token auth.
Antigravity launched in late 2025 and its official MCP docs are still thin. The setup below works as of the current release, but field names and paths may change. If something below doesn’t match what you see in your Antigravity install, prefer Antigravity’s in-app Manage MCP Servers UI as the source of truth.

​
Before You Connect

Sign in to your xysq account at app.xysq.ai.

​
Step 1 — Generate Your API Key

  1. After logging in, click the Connect Agent button.
  2. Select any tab that exposes API keys (Cursor, Codex, etc — the key format is identical).
  3. Click Generate API Key. Copy the xysq_... key — it won’t be shown again.

​
Step 2 — Open Antigravity’s MCP Config

You can edit the config file directly, or use the in-app UI. Config file path:
OSPath
macOS / Linux~/.gemini/antigravity/mcp_config.json
Windows%USERPROFILE%\.gemini\antigravity\mcp_config.json
UI alternative: open the MCP Store panel → Manage MCP Servers → View raw config (or Add server).

​
Step 3 — Add the xysq Entry

Paste this into mcp_config.json (create the file if it doesn’t exist): 
{
  "mcpServers": {
    "xysq": {
      "serverUrl": "https://api.xysq.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Replace YOUR_API_KEY with the key from Step 1. For safer secret handling, export the token and reference it: 
export XYSQ_API_KEY=xysq_...

{
  "mcpServers": {
    "xysq": {
      "serverUrl": "https://api.xysq.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${XYSQ_API_KEY}"
      }
    }
  }
}
Antigravity uses serverUrl (matching Windsurf), not url. Don’t paste a Cursor-style schema verbatim.

​
Step 4 — Restart Antigravity

There’s no documented hot-reload — restart the IDE so it picks up the new MCP entry. After restart, open the MCP Store / Manage MCP Servers panel and confirm xysq shows as connected. OAuth refresh tokens (if used) are auto-stored at ~/.gemini/antigravity/mcp_oauth_tokens.json and refresh in the background.

​
Step 5 — Use It

In any agent chat, try memory-aware prompts: 
Remember that I prefer tabs over spaces.
What's my current project context?
The agent will invoke xysq tools through the MCP connection.

​
Pinning Antigravity to a team vault

To scope the connection to a specific team, change the URL: 
{
  "mcpServers": {
    "xysq-acme": {
      "serverUrl": "https://api.xysq.ai/mcp/team/YOUR_TEAM_ID",
      "headers": {
        "Authorization": "Bearer ${XYSQ_API_KEY}"
      }
    }
  }
}
Find YOUR_TEAM_ID in Team Settings at app.xysq.ai. Team-pinned connections route all memory actions to the team vault and disable personal-only tools.

​
Troubleshooting

ProblemFix
xysq doesn’t appear in Manage MCP ServersRestart Antigravity. The IDE doesn’t hot-reload mcp_config.json.
serverUrl not recognisedYou may have a Cursor-style schema using url. Antigravity expects serverUrl.
Auth fails with 401Confirm XYSQ_API_KEY is exported in the shell that launched Antigravity (or paste the literal token into the config).
OAuth re-promptsDelete ~/.gemini/antigravity/mcp_oauth_tokens.json and re-authenticate from scratch.
UI shows different field namesTrust the UI — Antigravity’s config schema is still evolving. The UI reflects the current release.

​
Next: install the Skill

The MCP connection gives Antigravity the tools. The xysq Skill teaches it how to use them. Install the skill →