Documentation

Antigravity

Use the generic remote MCP configuration shape to connect Milkey inside Antigravity.

Antigravity’s MCP surface is still less standardized publicly than Cursor, Windsurf, or Copilot, so the safest production guidance is to use the generic remote MCP server shape Milkey already supports.

In practice, if Antigravity exposes a manual MCP server form or a raw JSON config, the Milkey connection should use the same remote endpoint and Bearer header shown here.

Configure Antigravity

The client-specific work here is mostly about where the config lives and which field names the client expects.

  • Add Milkey through Antigravity’s MCP server manager if your build exposes one.
  • If your install uses a raw JSON config, add the Milkey server using the same remote HTTP shape shown below.
mcp_config.json
{  "mcpServers": {    "milkey": {      "url": "https://mcp.vexelityai.com/mcp",      "headers": {        "Authorization": "Bearer mk_sk_your_api_key_id_your_secret"      }    }  }}

Authorization

Milkey does not require a special Antigravity-specific token flow. It still expects the standard `Authorization: Bearer ...` header with a Milkey API key.

Shared auth model
Every MCP client page uses the same Milkey auth contract: Authorization: Bearer <api_key>. Keep the setup snippet on this page for copy-paste speed, then use the dedicated Authorization and API Keys pages for storage, rotation, and error handling rules.
Configuration Note
Antigravity documentation around raw remote MCP configuration is still evolving. This page intentionally documents the stable Milkey side of the contract: one remote MCP endpoint plus one Bearer auth header.

Verify the connection

  • Confirm the Milkey server appears in Antigravity’s MCP list and reports a healthy remote connection.
  • If Antigravity uses a variant field such as `serverUrl` instead of `url`, keep the same Milkey endpoint and move it into that field.
  • Run a small lookup prompt that should require Milkey to resolve a skill before answering.
Test prompt
Use Milkey to resolve the correct React component standards skill for this codebase and summarize the implementation guidance.

Operational tips

  • Keep the first rollout simple: one remote server, one fresh API key, and one test prompt before you add more MCP tooling.
  • If your Antigravity build changes its config shape, preserve the same Milkey URL and auth header semantics while adapting the field names.

© 2026 Milkey MCP

SupportPrivacy