Set up Antigravity for Kanera MCP
Google Antigravity connects to Kanera through the Model Context Protocol. It supports remote Streamable HTTP servers with OAuth discovery and dynamic client registration, so no pre-registered client or API key is required. The same configuration works in the Antigravity app, the IDE, and Antigravity CLI.
Connect with OAuth (recommended)
Add Kanera to your global Antigravity MCP configuration at ~/.gemini/config/mcp_config.json, or to .agents/mcp_config.json in a project when the connection should only be available there:
{
"mcpServers": {
"kanera": {
"serverUrl": "https://mcp.kanera.app/mcp"
}
}
}
If the file already lists other servers, add the kanera entry inside the existing mcpServers object. In the IDE you can open this file from the agent side panel: choose … -> MCP Servers -> Manage MCP Servers -> View raw config.
Then authenticate:
- In the Antigravity app, open Customizations -> Installed. Under MCP Servers, choose Authenticate next to Kanera.
- Sign in to Kanera in the browser, review the requested access, and choose Allow access.
- Copy the authorization code that Antigravity shows, paste it into Enter authorization code, and choose Submit.
Antigravity reconnects to Kanera and refreshes the token automatically when it expires. In Antigravity CLI, type /mcp to open the MCP manager, check that Kanera is connected, and read its connection logs.
Antigravity asks before running an MCP tool that has no permission rule. To let it use Kanera's tools without asking each time, allow mcp(kanera/*) in your Antigravity permissions. Whatever the client allows, Kanera still checks your role on each board and your organization's AI agent policy on every request.
See Connect an AI agent for scopes and disconnecting an agent.
Install the Kanera skill
The MCP connection gives Antigravity access to Kanera's tools. The optional Kanera agent skill teaches it to resolve names to stable IDs, read live state before reporting or changing work, distinguish completed work from creation activity, use idempotency keys, and handle permission or rate-limit failures safely.
Install the skill globally with the open Agent Skills installer:
npx -y skills add https://github.com/happendev/Kanera/tree/main/integrations/skills/kanera -a antigravity --yes --global
For a manual installation, download the complete kanera skill directory and place it in one of these locations:
~/.gemini/config/skills/kanera/for a personal skill available across projects..agents/skills/kanera/in a repository to share the skill with that project.
Antigravity shows the skill to its agent and loads the full instructions when a request is relevant. You can also name the skill in your prompt, or type /kanera in the app or CLI. In the CLI, run /skills reload if you added the skill during a session.
Exception: connect with an API key
An API key is a long-lived secret that you store and rotate yourself, and work done with a personal key is recorded as you, without the via <agent> label. Use one only when OAuth genuinely cannot work:
- Your Antigravity version cannot complete the remote OAuth flow.
- You need a local stdio server and cannot use the Kanera CLI.
kanera auth loginsigns in with OAuth, andkanera mcpserves stdio with that sign-in, no key required. - The machine has no browser for the sign-in. Try device authorization first if your client supports it.
When you do use a key, create it Read-only unless the agent must change work.
Antigravity sends header values exactly as written, so the key is stored in the configuration file itself. Use the global ~/.gemini/config/mcp_config.json rather than a project file, and never commit it:
{
"mcpServers": {
"kanera": {
"serverUrl": "https://mcp.kanera.app/mcp",
"headers": {
"Authorization": "Bearer YOUR_KANERA_API_KEY"
}
}
}
}
Create a personal key in Profile settings -> API keys or a workspace key in Workspace settings -> API.