MCP server for Perplexity search
MCP server for Perplexity search. The mcp perplexity search mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
The functionality of this tool is now available in mcp-omnisearch, which combines multiple MCP tools in one unified package.
Everything the assistant can do here goes through one of these:
chat_completion — Generate chat completions using the Perplexity API with support for specialized prompt templatesSetup — The Setup tool exposed by this serverPublishing — The project uses changesets for version management. To publish:mcp-perplexity-search on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: PERPLEXITY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Perplexity Search's toolset — chat_completion, Setup, Publishing — is a fair guide to whether it matches your workflow. It is maintained by spences10; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| chat_completion | Generate chat completions using the Perplexity API with support for specialized prompt templates. |
| Setup | The Setup tool exposed by this server. |
| Publishing | The project uses changesets for version management. To publish: |
{
"mcpServers": {
"mcp-perplexity-search": {
"command": "npx",
"args": ["-y", "mcp-perplexity-search"],
"env": {
"PERPLEXITY_API_KEY": "your-perplexity-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PERPLEXITY_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.