Perplexity▌
by ppl-ai
Empower your workflows with Perplexity Ask MCP Server—seamless integration of AI research tools for real-time, accurate
Unlock real-time, web-wide research for Claude with Sonar API integration via MCP. Perplexity Ask MCP Server enables natural-language queries by connecting Claude to Perplexity’s Sonar, bringing fresh internet search capabilities directly into your AI workflows. The system is designed for easy expansion and can also be used with compatible apps like Cursor. Ideal for users seeking accurate, up-to-date information in conversational settings, the server’s flexible architecture empowers seamless integration of advanced research tools with your favorite AI platforms.
github stars
★ 2.0K
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Research tasks requiring cited sources
- / Getting current information beyond training data
- / AI assistants that need web-grounded responses
capabilities
- / Query Perplexity AI with natural language questions
- / Get chat completions with source citations
- / Access web-informed AI responses
what it does
Integrates Perplexity's AI search API to get chat responses with source citations. Requires a Perplexity API key and may timeout on long queries.
about
Perplexity is an official MCP server published by ppl-ai that provides AI assistants with tools and capabilities via the Model Context Protocol. Empower your workflows with Perplexity Ask MCP Server—seamless integration of AI research tools for real-time, accurate It is categorized under search web.
how to install
You can install Perplexity in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Perplexity is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Perplexity API Platform MCP Server
The official MCP server implementation for the Perplexity API Platform, providing AI assistants with real-time web search, reasoning, and research capabilities through Sonar models and the Search API.
Available Tools
perplexity_search
Direct web search using the Perplexity Search API. Returns ranked search results with metadata, perfect for finding current information.
perplexity_ask
General-purpose conversational AI with real-time web search using the sonar-pro model. Great for quick questions and everyday searches.
perplexity_research
Deep, comprehensive research using the sonar-deep-research model. Ideal for thorough analysis and detailed reports.
perplexity_reason
Advanced reasoning and problem-solving using the sonar-reasoning-pro model. Perfect for complex analytical tasks.
[!TIP] Available as an optional parameter for perplexity_reason and perplexity_research:
strip_thinkingSet to
trueto remove<think>...</think>tags from the response, saving context tokens. Default:false
Configuration
Get Your API Key
- Get your Perplexity API Key from the API Portal
- Replace
your_key_herein the configurations below with your API key - (Optional) Set timeout:
PERPLEXITY_TIMEOUT_MS=600000(default: 5 minutes) - (Optional) Set custom base URL:
PERPLEXITY_BASE_URL=https://your-custom-url.com(default: https://api.perplexity.ai) - (Optional) Set log level:
PERPLEXITY_LOG_LEVEL=DEBUG|INFO|WARN|ERROR(default: ERROR)
Claude Code
claude mcp add perplexity --env PERPLEXITY_API_KEY="your_key_here" -- npx -y @perplexity-ai/mcp-server
Or install via plugin:
export PERPLEXITY_API_KEY="your_key_here"
claude
# Then run: /plugin marketplace add perplexityai/modelcontextprotocol
# Then run: /plugin install perplexity
Cursor, Claude Desktop & Windsurf
We recommend using the one-click install badge at the top of this README for Cursor.
For manual setup, all these clients use the same mcpServers format:
| Client | Config File |
|---|---|
| Cursor | ~/.cursor/mcp.json |
| Claude Desktop | claude_desktop_config.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
{
"mcpServers": {
"perplexity": {
"command": "npx",
"args": ["-y", "@perplexity-ai/mcp-server"],
"env": {
"PERPLEXITY_API_KEY": "your_key_here"
}
}
}
}
VS Code
We recommend using the one-click install badge at the top of this README for VS Code, or for manual setup, add to .vscode/mcp.json:
{
"servers": {
"perplexity": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@perplexity-ai/mcp-server"],
"env": {
"PERPLEXITY_API_KEY": "your_key_here"
}
}
}
}
Codex
codex mcp add perplexity --env PERPLEXITY_API_KEY="your_key_here" -- npx -y @perplexity-ai/mcp-server
Other MCP Clients
Most clients can be manually configured to use the mcpServers wrapper in their configuration file (like Cursor). If your client doesn't work, check its documentation for the correct wrapper format.
Proxy Setup (For Corporate Networks)
If you are running this server at work—especially behind a company firewall or proxy—you may need to tell the program how to send its internet traffic through your network's proxy. Follow these steps:
1. Get your proxy details
- Ask your IT department for your HTTPS proxy address and port.
- You may also need a username and password.
2. Set the proxy environment variable
The easiest and most reliable way for Perplexity MCP is to use PERPLEXITY_PROXY. For example:
export PERPLEXITY_PROXY=https://your-proxy-host:8080
If your proxy needs a username and password, use:
export PERPLEXITY_PROXY=https://username:password@your-proxy-host:8080
3. Alternate: Standard environment variables
If you'd rather use the standard variables, we support HTTPS_PROXY and HTTP_PROXY.
[!NOTE] The server checks proxy settings in this order:
PERPLEXITY_PROXY→HTTPS_PROXY→HTTP_PROXY. If none are set, it connects directly to the internet. URLs must includehttps://. Typical ports are8080,3128, and80.
HTTP Server Deployment
For cloud or shared deployments, run the server in HTTP mode.
Environment Variables
| Variable | Description | Default |
|---|---|---|
PERPLEXITY_API_KEY | Your Perplexity API key | Required |
PERPLEXITY_BASE_URL | Custom base URL for API requests | https://api.perplexity.ai |
PORT | HTTP server port | 8080 |
BIND_ADDRESS | Network interface to bind to | 0.0.0.0 |
ALLOWED_ORIGINS | CORS origins (comma-separated) | * |
Docker
docker build -t perplexity-mcp-server .
docker run -p 8080:8080 -e PERPLEXITY_API_KEY=your_key_here perplexity-mcp-server
Node.js
export PERPLEXITY_API_KEY=your_key_here
npm install && npm run build && npm run start:http
The server will be accessible at http://localhost:8080/mcp
Troubleshooting
- API Key Issues: Ensure
PERPLEXITY_API_KEYis set correctly - Connection Errors: Check your internet connection and API key validity
- Tool Not Found: Make sure the package is installed and the command path is correct
- Timeout Errors: For very long research queries, set
PERPLEXITY_TIMEOUT_MSto a higher value - Proxy Issues: Verify your
PERPLEXITY_PROXYorHTTPS_PROXYsetup and ensureapi.perplexity.aiisn't blocked by your firewall. - EOF / Initialize Errors: Some strict MCP clients fail because
npxwrites installation messages to stdout. Usenpx -yqinstead ofnpx -yto suppress this output.
For support, visit community.perplexity.ai or file an issue.
FAQ
- What is the Perplexity MCP server?
- Perplexity is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Perplexity?
- This profile displays 30 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Web Research & Information Gathering
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Content Monitoring & Alerts
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Data Extraction & Aggregation
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
API-less Integration
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Implementation Guide▌
Prerequisites
- ›Claude Desktop or Cursor with MCP support
- ›Understanding of web scraping ethics and robots.txt
- ›Rate limiting awareness to avoid overwhelming target sites
- ›Knowledge of legal restrictions on data collection
Time Estimate
20-40 minutes including configuration and testing
Installation Steps
- 1.Install web automation MCP server via npm or pip
- 2.Configure allowed domains and rate limits in MCP config
- 3.Test with simple fetch: 'Get content from example.com'
- 4.Progress to extraction: 'Extract all product prices from this page'
- 5.Set up monitoring: 'Check this URL daily for changes'
- 6.Parse structured data: 'Create CSV from this table'
- 7.Respect robots.txt and rate limits always
Troubleshooting
- ⚠403 Forbidden: Website blocks bots—respect their wishes, use official API instead
- ⚠Rate limit errors: Slow down requests, add delays between fetches
- ⚠Stale data: Target site changed HTML structure—update selectors
- ⚠Timeout errors: Site is slow or blocking—increase timeout, try different user agent
- ⚠JavaScript-rendered content: Use headless browser MCP servers for dynamic sites
Best Practices▌
✓ Do
- +Check robots.txt and respect crawl rules
- +Rate limit requests: 1-2 requests/second maximum
- +Use official APIs when available instead of scraping
- +Identify your bot with descriptive user agent
- +Cache results to minimize repeated requests
- +Handle errors gracefully with retries and fallbacks
- +Validate extracted data for accuracy
✗ Don't
- −Don't scrape sites that explicitly forbid it (robots.txt, ToS)
- −Don't overwhelm servers with rapid requests—use rate limiting
- −Don't scrape personal data without consent and legal basis
- −Don't ignore copyright on extracted content
- −Don't assume HTML structure is stable—handle changes
- −Don't use scraped data for commercial purposes without permission
💡 Pro Tips
- ★Use CSS selectors or XPath for robust data extraction
- ★Set up monitoring alerts for extraction failures (structure changed)
- ★Implement exponential backoff for retries on failures
- ★Store raw HTML for reprocessing if extraction logic changes
- ★Combine with data analysis tools for insights from extracted data
- ★Consider using official APIs or RSS feeds as more stable alternatives
Technical Details▌
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
- HTTP/HTTPS
- WebSocket (for real-time sites)
- Puppeteer/Playwright (for JavaScript sites)
Compatibility
- Static HTML sites
- JavaScript-rendered SPAs (with headless browser)
- REST APIs
- GraphQL endpoints
When to Use This▌
✓ Use When
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid When
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.
Integration▌
- →Scheduled monitoring with change detection
- →Multi-source data aggregation pipelines
- →Fallback to web scraping when API rate limits hit
- →Headless browser for JavaScript-heavy sites
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.6★★★★★30 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
Strong directory entry: Perplexity surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Aisha Haddad· Dec 24, 2024
We evaluated Perplexity against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Yash Thakker· Nov 19, 2024
Perplexity has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Aisha Lopez· Nov 15, 2024
We wired Perplexity into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Sakshi Patil· Nov 11, 2024
Useful MCP listing: Perplexity is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Dhruvi Jain· Oct 10, 2024
According to our notes, Perplexity benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Yuki Kapoor· Oct 6, 2024
Perplexity is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Chaitanya Patil· Oct 2, 2024
Perplexity reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Oshnikdeep· Sep 17, 2024
We wired Perplexity into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Zara Robinson· Sep 17, 2024
Useful MCP listing: Perplexity is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 30