Perplexity Integration for AI Agents

Perform real-time web research and retrieve AI-synthesized answers backed by online sources. Combine search and reasoning capabilities to support information gathering and analysis.

v1.0.03 toolsAPI KeyGitHub Report an issue

Open in ChatGPTChatGPT

Open in ClaudeClaude

Playground

VS Code

Connected to Perplexity via MewCP.

Encrypted at rest, isolated from the model

Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.

Try asking

Everything Perplexity can do

Tools3

search

write

Search the web using Perplexity AI. Returns an LLM-generated response with citations from online sources. Use this for queries that need current information, news, or factual answers with references.

get_models

write

List all available models from Perplexity AI, including both online and offline models.

health_check

write

Check server readiness and basic connectivity.

Missing a tool, or found a bug?

Perplexity MCP Server is open source. Tell the MewCP maintainers.

Open GitHub Issues

Connect Perplexity to your agent

One endpoint, the same key, whichever client you use.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON

{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

01Open Claude Desktop → Settings → Developer → "Edit Config"
02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
03Save the file, then quit Claude Desktop completely and reopen it
04Start a new conversation — your tool will be available

One endpoint. Every service.

Any agent

One Gateway

Firecrawl

API Key

Web Scrapper

No auth

Github

OAuth

Perplexity

API Key

Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you

Separate connections74 tool definitions ~6.7k tokensWith MewCP4 meta-tools ~1.5k tokens

Built for AI agents

Perplexity runs through a gateway that holds the credentials, scopes the access and records every call.

Managed credentials

Perplexity API keys are encrypted at rest and never shown again after you save them.
One credential per end user, not one shared key across your users.
Rotate a key without touching your agent's config.

Credentials stay out of context

Perplexity credentials are resolved at the gateway and attached to the outbound call.
The agent sees tool results, never a token.
Revoke an account and the next call stops working — no redeploy.

Scoped access, fully logged

Choose exactly which Perplexity tools an agent is allowed to call.
Every call is logged with its outcome, latency and which account it ran as.
Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

One endpoint for every server

Reach Perplexity through the same MCP endpoint as the rest of your toolset.
Tools are discovered on demand, so 3 tools do not fill the context window.
Stateless: no sessions to keep alive and no reconnect logic.

Ready to connect Perplexity?

Managed auth, hosted MCP servers, and every Perplexity tool your agent needs.

Free to start.

Everything Perplexity can do

Tools3

search

write

Search the web using Perplexity AI. Returns an LLM-generated response with citations from online sources. Use this for queries that need current information, news, or factual answers with references.

get_models

write

List all available models from Perplexity AI, including both online and offline models.

health_check

write

Check server readiness and basic connectivity.

Connect Perplexity to your agent

One endpoint, the same key, whichever client you use.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON

{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

01Open Claude Desktop → Settings → Developer → "Edit Config"
02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
03Save the file, then quit Claude Desktop completely and reopen it
04Start a new conversation — your tool will be available

Built for AI agents

Perplexity runs through a gateway that holds the credentials, scopes the access and records every call.

Managed credentials

Perplexity API keys are encrypted at rest and never shown again after you save them.
One credential per end user, not one shared key across your users.
Rotate a key without touching your agent's config.

Credentials stay out of context

Perplexity credentials are resolved at the gateway and attached to the outbound call.
The agent sees tool results, never a token.
Revoke an account and the next call stops working — no redeploy.

Scoped access, fully logged

Choose exactly which Perplexity tools an agent is allowed to call.
Every call is logged with its outcome, latency and which account it ran as.
Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

One endpoint for every server

Reach Perplexity through the same MCP endpoint as the rest of your toolset.
Tools are discovered on demand, so 3 tools do not fill the context window.
Stateless: no sessions to keep alive and no reconnect logic.