Antigravity and other MCP clients

Antigravity

Add https://api.usepalim.com/mcp as a remote MCP server. Antigravity starts the OAuth flow on first use; this flow does not require an API key.

Generic clients with an API key

Clients without OAuth can send the key created on the setup page as a header:

x-api-key: palim_...

This applies to clients such as n8n MCP Client and custom JSON-RPC integrations. Send initialize first and carry the mcp-session-id header returned by the server on subsequent stateful HTTP calls.

n8n

Use an MCP Client node or the MCP Client credentials available in your n8n version:

Transport: Streamable HTTP.
Server URL: https://api.usepalim.com/mcp.
Authentication: custom header.
Header name: x-api-key.
Header value: your palim_... API key.

Store the key in n8n credentials, not directly in a workflow field or prompt. The client must perform MCP initialization and carry the returned mcp-session-id on subsequent stateful requests.

Raw JSON-RPC

The first request is an initialize call to /mcp with Content-Type: application/json, Accept: application/json, text/event-stream, and the x-api-key header. Carry the mcp-session-id from the response into later requests, then send notifications/initialized before calling a method such as tools/list.

Do not start with a tool call

One POST to tools/call without a preceding initialize request and the session ID is not a complete MCP handshake.

Tune agent behavior

Add the Palim base instruction to the system prompt of your n8n agent node, Antigravity project, or custom client. See Prompts and personalization for the instruction and technical reliability test. The prompt does not replace initialize, authentication, or session headers.

Clients without header support

An already connected agent can use palim_create_connection_url to create a connection URL. Each account can have at most five active connection tokens. There is currently no public management or revocation interface. Treat the URL like a password and prefer OAuth or x-api-key whenever possible.

Compatibility check

A client is generally compatible if it supports remote MCP over Streamable HTTP and allows either OAuth or custom HTTP headers. Visible tool names and the way a connector is enabled for a chat vary by product.