Perplexity MCP server for AI agents

Live

BEARER TOKEN

WEB SEARCH

AI

Perplexity gives your agent web-grounded answers: search the web, get cited Sonar answers, run the Agent API on research tasks, create embeddings, and evaluate content against yes or no questions.

  • Per-user credentials: each call uses the actual user's access token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Perplexity
agent · Acme Q3
Run
Find recent news about Acme Corp's funding.
S
perplexity_chat_completion
141ms
Research agent
Acme Corp announced a $40M Series B 3 weeks ago. The answer cites 5 sources, including the company's press release.
Sources: 5 cited web pages
perplexity
5 citations
18:29
Message Claude...

Tools your research agent reaches for on Perplexity, scoped per user.

CALL ANY TOOL
17 tools for web search in Perplexity: search the web, get Sonar answers with citations, run sync and async completions, run and cancel Agent API responses, create embeddings, evaluate content, and list custom skills.
perplexity_answer_decisions
Answer decisions
Evaluate named yes/no, multiple-choice, and scoring questions against a piece of content. Returns an answers object keyed by question name (probability for noul, chosen option for choice, level for score), plus the model and token usage. Use this for classification, moderation, routing, and rubric scoring over text; use perplexity_chat_completion for open-ended answers.
Parameters
Name
Type
Required
Description
model
string
Required
Decision model: pplx-decider-v1.2 (larger) or pplx-decider-flash-v1.2 (faster, cheaper). Aliases pplx-decider-latest and pplx-decider-flash-latest also work.
questions
object
Required
Questions as a JSON object mapping a name you choose to a question. Each question has a type of noul (yes/no, with instructions), choice (with criteria mapping option names to descriptions), or score (with criteria listing level descriptions). Example: {"is_bug":{"type":"noul","instructions":"Is this a bug report?"},"area":{"type":"choice","criteria":{"billing":null,"settings":null}}}
state
string
Required
The content every question refers to: plain text, or a JSON object or array serialized as a string. Example: Customer wrote: the app crashes every time I open settings.
perplexity_cancel_agent_response
Cancel agent response
perplexity_chat_completion
Chat completion
perplexity_create_agent_response
Create agent response
perplexity_create_async_chat_completion
Create async chat completion
perplexity_create_contextualized_embeddings
Create contextualized embeddings
perplexity_create_embeddings
Create embeddings
perplexity_get_agent_response
Get agent response
perplexity_get_async_chat_completion
Get async chat completion
perplexity_get_skill
Get skill
perplexity_get_skill_download_url
Get skill download url
perplexity_list_agent_response_files
List agent response files
perplexity_list_async_chat_completions
List async chat completions
perplexity_list_models
List models
perplexity_list_skill_revisions
List skill revisions
perplexity_list_skills
List skills
perplexity_search
Search
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Perplexity tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["perplexity"], toolNames: [
    "perplexity_search",
    "perplexity_chat_completion",
    "perplexity_create_agent_response"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find recent news about Acme Corp's funding with citations" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["perplexity"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find recent news about Acme Corp's funding with citations" }],
  tools,
});

// Execute the tool call with the user's vaulted Perplexity access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["perplexity"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find recent news about Acme Corp's funding with citations" }],
  tools,
});

// Tool call runs with the user's vaulted Perplexity access token
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["perplexity"] }, pageSize: 100,
});

const agent = new Agent({
  name: "research_agent",
  model: "gemini-2.5-pro",
  instruction: "Perplexity tools scoped to this user",
  tools,
});

await agent.run("Find recent news about Acme Corp's funding with citations");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Perplexity tool. Click to copy, paste into your agent, done.
Search and answers
Copy the prompt
Copied
Search the web for agent authentication platforms launched this year.
Copy the prompt
Copied
Find recent news about Acme Corp's funding with citations.
Copy the prompt
Copied
Submit an async research question on EV battery suppliers.
Agent API
Copy the prompt
Copied
Run the Agent API on a comparison of 3 CRM vendors.
Copy the prompt
Copied
Check whether my agent response has finished.
Copy the prompt
Copied
List the files my last agent response generated.
Embeddings and evaluation
Copy the prompt
Copied
Create embeddings for these 100 support articles.
Copy the prompt
Copied
Does this blog post mention pricing? Answer yes or no.
Copy the prompt
Copied
List the custom skills in our Perplexity project.
SEE HOW AUTH WORKS
Each user connects their own Perplexity access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Perplexity
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Perplexity
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Perplexity
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Perplexity
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other AI and search connectors.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
GTM and RevOps Teams
Sales call prep agent
Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.
Test other agents
See the same per-user auth pattern across other AI and search connectors.
GTM
Competitive intelligence briefing agent
Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.
SALES
Sales call prep agent
Read tomorrow's calls from Google Calendar, mine Granola notes and Attio history, and deliver each rep a prep brief in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Perplexity access token looks fine in a demo. In production every search and answer looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Perplexity today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Perplexity as the user or through a shared access token?
As the user. Each user connects their own Perplexity access token once, and Scalekit sends it with every call. Audit logs attribute every search and agent run to that user, not a shared service account.
Where is the Perplexity access token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Perplexity?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example perplexity_search and perplexity_chat_completion without the Agent API tools. No Perplexity tool deletes data. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Perplexity access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Does the agent get sources with each answer?
Yes. perplexity_chat_completion returns the Sonar answer with citations and search results, and perplexity_search returns ranked results with page titles, URLs, snippets, and dates.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""perplexity"": {
""url"": ""https://mcp.scalekit.com/perplexity"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.perplexity]
url = ""https://mcp.scalekit.com/perplexity""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""perplexity"": {
""url"": ""https://mcp.scalekit.com/perplexity"",
""type"": ""http""
}
}
}