# Perplexity MCP Server for Google Antigravity

Use Perplexity's hosted [Model Context Protocol (MCP) server](/guides/getting-started-integrations-mcp-server) to give Google Antigravity's agent access to Perplexity search, answers, research, and reasoning. The server runs remotely, so you do not need to install a local package.

## Configure Perplexity MCP in Google Antigravity

:::::steps
::::step{title="Create a Perplexity API key"}
:::card{title="Generate API Key" href="https://console.perplexity.ai/project/keys" icon="key" cta="Get Key" horizontal="true" arrow="true"}
Create an API key in the Perplexity API Portal.
:::
::::

::::step{title="Open the global MCP configuration"}
Open or create `~/.gemini/config/mcp_config.json`. Google Antigravity also supports a workspace-level `.agents/mcp_config.json`, but the global file is the safer place for a configuration containing your API key.

:::callout{intent="warning"}
Never commit or share API keys. Do not place a literal key in `.agents/mcp_config.json`, because workspace configuration may be committed or shared.
:::
::::

:::step{title="Add the hosted Perplexity server"}
Add the `perplexity` entry under `mcpServers`. If the file already contains other servers, merge this entry into the existing object.

```json theme={null}
{
  "mcpServers": {
    "perplexity": {
      "serverUrl": "https://api.perplexity.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PERPLEXITY_API_KEY"
      }
    }
  }
}
```

Replace `YOUR_PERPLEXITY_API_KEY` with your key. Antigravity requires `serverUrl` for remote Streamable HTTP MCP servers; `url` and `httpUrl` are not supported.
:::

:::step{title="Verify the connection and permissions"}
Save the file and reopen Antigravity if the server does not appear. In MCP management, confirm that the Perplexity server exposes these tools:

- `perplexity_search`
- `perplexity_ask`
- `perplexity_research`
- `perplexity_reason`

By default, unconfigured MCP tools run in **Ask** permission mode, so Antigravity requests your approval before running them. You can change tool permissions in Antigravity's policy configuration after confirming the connection works.
:::
:::::

:::callout{intent="note"}
Google's public documentation lists `Perplexity Ask` in the [Antigravity MCP Store](https://antigravity.google/docs/mcp#supported-mcp-servers). That Store listing has not been independently verified here. The manual configuration above connects directly to Perplexity's hosted MCP server and does not depend on the Store listing.
:::

## MCP tool access vs. Perplexity API calls

This setup lets the **Antigravity agent** call Perplexity through MCP while it works on your project. It does not add Perplexity API calls to the application you are building.

- For more MCP clients, local-server options, billing, and troubleshooting, see the [Perplexity MCP server guide](/guides/getting-started-integrations-mcp-server).
- To call Perplexity from your application code, start with the [Perplexity API quickstart](/guides/getting-started-quickstart).

For other Antigravity MCP settings, see [Google's MCP configuration reference](https://antigravity.google/docs/mcp#mcp-configuration-structure).

## Related pages

- [Perplexity with AG2](./resources-getting-started-integrations-ag2.md)
- [Perplexity with Agno](./resources-getting-started-integrations-agno.md)
- [Perplexity with AnythingLLM](./resources-getting-started-integrations-anythingllm.md)
- [Perplexity with CAMEL-AI](./resources-getting-started-integrations-camel.md)
- [Perplexity with Claude Code](./resources-getting-started-integrations-claude-code.md)
- [Perplexity with Composio](./resources-getting-started-integrations-composio.md)
- [Perplexity with Cursor](./resources-getting-started-integrations-cursor.md)
- [Perplexity with Haystack](./resources-getting-started-integrations-haystack.md)
- [Perplexity web search in Hermes](./resources-getting-started-integrations-hermes.md)
- [Perplexity with LangChain](./resources-getting-started-integrations-langchain.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.