MCP Server Perplexity vs Fetch
A side-by-side look at the MCP Server Perplexity and Fetch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Perplexity for search & data extraction work as a local process; choose Fetch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Perplexity when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PERPLEXITY_API_KEY. - You want tools like
ask_perplexity.
Choose Fetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 48/100 · Fair | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | PERPLEXITY_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 96 | 91,512 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 1 | 1 |
| Full listing | View MCP Server Perplexity | View Fetch |
Tools & capabilities
MCP Server Perplexity tools 1
ask_perplexityRequest chat completion with citations from Perplexity
Fetch tools 1
fetchFetches a URL from the internet and extracts its contents as markdown.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server Perplexity
{
"mcpServers": {
"tanigami-mcp-server-perplexity": {
"command": "uvx",
"args": [
"mcp-server-perplexity"
],
"env": {
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE"
}
}
}
}
Fetch
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}
Frequently asked questions
MCP Server Perplexity is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick MCP Server Perplexity for search & data extraction work and Fetch for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server Perplexity is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Fetch is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add tanigami-mcp-server-perplexity and fetch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Perplexity has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 96 GitHub stars. Fetch has 80/100 (Excellent) with 5 views, 0 installs and 91,512 GitHub stars.