Data as of

Perplexity API Platform MCP Server for Cursor: Setup

The Perplexity API Platform MCP Server gives Cursor web search, conversational answers, research, and reasoning tools.

What you can do with Perplexity API Platform in Cursor

Pick it for Perplexity search, Sonar answers, deep research, and reasoning in a single MCP integration.

  • Produce detailed research through sonar-deep-research.
  • Handle analytical questions using sonar-reasoning-pro.

Before you start: Perplexity API Platform in Cursor

  • A Perplexity API key
  • npm/npx tooling for the local command
  • An MCP-compatible client
  • Network access to the configured Perplexity API endpoint

Use the package named in the README rather than the older config_hint package. HTTP deployment is also documented. PERPLEXITY_TIMEOUT_MS adjusts timeouts, and npx -yq is suggested for clients affected by installation output.

Perplexity API Platform Cursor configuration

  1. Choose Cursor configuration scope

    For Perplexity API Platform MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add Perplexity API Platform MCP Server to Cursor

    Use the modelcontextprotocol entry below in mcpServers. Keep Perplexity API Platform MCP Server's documented stdio connection fields and your other Cursor entries.

  3. Check Perplexity API Platform MCP Server in Cursor

    Perplexity API Platform MCP Server: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "modelcontextprotocol": {
      "command": "npx",
      "args": [
        "-y",
        "@perplexity-ai/mcp-server"
      ],
      "env": {
        "PERPLEXITY_API_KEY": "<Perplexity API key>"
      }
    }
  }
}

Perplexity API Platform tools available to Cursor

Perplexity API Platform's stored tool list documents 4 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

perplexity_search

Find perplexity_search under Perplexity API Platform in Cursor's MCP settings; inspect its arguments when the agent requests a call.

perplexity_ask

Find perplexity_ask under Perplexity API Platform in Cursor's MCP settings; inspect its arguments when the agent requests a call.

perplexity_research

Find perplexity_research under Perplexity API Platform in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Run detailed research with sonar-deep-research.

perplexity_reason

Find perplexity_reason under Perplexity API Platform in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Handle analytical reasoning with sonar-reasoning-pro.

Perplexity API Platform: full stored tool descriptions

Troubleshooting Perplexity API Platform in Cursor

  • Cursor must find npx @perplexity-ai/mcp-server (Node.js/npm) for Perplexity API Platform MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
  • Review PERPLEXITY_API_KEY for Perplexity API Platform MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
  • Perplexity API Platform MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires a Perplexity API key and connectivity to the API.
  • Known limitation: Long research requests can need higher timeout settings.
  • Known limitation: Some strict clients need quieter npx output to initialize successfully.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

Perplexity API Platform MCP Server — details. Cursor guide

Frequently asked questions

Cursor's Perplexity API Platform MCP Server entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's modelcontextprotocol example uses stdio.

Perplexity API Platform MCP Server's Cursor configuration invokes npx @perplexity-ai/mcp-server (Node.js/npm).

Cursor's Perplexity API Platform MCP Server example references PERPLEXITY_API_KEY. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Perplexity API Platform MCP Server's stored list contains 4 tools, including perplexity_search, perplexity_ask, perplexity_research. Compare those names with Cursor's connected tool list; the stored list is not a live check.

Yes. The README documents Docker and Node.js deployment, a /mcp endpoint, and loopback binding by default.

The documented precedence is PERPLEXITY_PROXY, then HTTPS_PROXY, then HTTP_PROXY. Without them it connects directly.