KnowMan MCP server for Google Antigravity

What you need before you start

You need a KnowMan account, an API key, and Node 22 or newer. Create the key in the web app under Settings > Connections > Connect an AI agent. See KnowMan MCP.

On the Antigravity side you need access to mcp_config.json. Antigravity supports MCP, an open standard that lets AI agents connect to local tools and remote APIs.

Add the server to mcp_config.json

Antigravity keeps MCP config in two places. The global file ~/.gemini/config/mcp_config.json applies to all your projects. The workspace file <workspace>/.agents/mcp_config.json applies to one workspace. In the IDE, open MCP Servers, click Manage MCP Servers, then View raw config to edit the file. See Antigravity MCP docs.

The root object holds an mcpServers map. Each entry specifies exactly one transport property, command for a local stdio server or serverUrl for a remote one. Paste the knowman entry from the config block above, which uses command, args, and env for the stdio transport. The schema is documented in the Antigravity MCP docs.

In the Antigravity App, manage servers in the MCP Servers section of the Customizations page. The Copy Config File Path button in the section header shows the file location. See Antigravity MCP docs.

Sign in once with knowman login

You can skip pasting a key. Run npx -p @knowman/mcp knowman login once. It opens a browser sign-in and saves a credential that the CLI and the MCP server share, so you can drop the env block from the config. See KnowMan MCP.

If you prefer a key, create one in the web app under Settings > Connections > Connect an AI agent, then set it as the KNOWMAN_API_KEY environment variable. See KnowMan MCP.

Verify the connection

In the CLI, type /mcp in the prompt panel and press Enter to open the MCP Manager Overlay. It shows status rings for active, disconnected, or loading servers, and you can reload server configurations or inspect connection logs there. See Antigravity MCP docs.

In the App, click More actions (⋮) next to the server and choose Restart, Disable, or Delete as needed. In the IDE, tools from an installed server are automatically available to the editor. Then ask the assistant to search my KnowMan for something, or to save a URL. See Antigravity MCP docs and KnowMan MCP.

Use the hosted remote server instead

Antigravity also supports remote host MCP servers. Remote servers must use the Streamable HTTP transport, set with the serverUrl key. The url key works as an alias. The legacy HTTP+SSE transport and the httpUrl field are not supported. See Antigravity MCP docs.

KnowMan runs a hosted server at https://api.knowman.io/mcp over Streamable HTTP. It accepts OAuth sign-in or an API key sent as Authorization: Bearer <key>. See KnowMan MCP.

If something goes wrong

For long-running tools, raise the entry's timeoutSeconds. The Antigravity docs show an example that raises a remote server's timeout to 600 seconds, or 10 minutes. See Antigravity MCP docs.

In the App, More actions (⋮) next to a server offers Restart, Disable, or Delete. In the CLI, the MCP Manager Overlay can manually reload server configurations or inspect real-time connection logs. See Antigravity MCP docs.

The KnowMan tools

Once connected, the server exposes tools documented in the KnowMan MCP repo. kb_search finds saved items by keyword or meaning and returns titles, URLs, and metadata. kb_ask answers a question with citations. kb_get_item returns the readable content of one item.

kb_save saves a URL to the Inbox or the Knowledge Base, with an optional note. kb_recent lists recently saved items. kb_memories lists saved claims, decisions, and playbooks. For background, see an MCP server for your knowledge base.