Perplexity MCP Server + Amp: Complete MCP Integration
Perplexity MCP Server is a MCP server that The official MCP server implementation for Perplexity API Platform. Provides real-time web search, deep research, and advanced reasoning capabilities through Sonar AI models and the Search API..
When integrated with Amp, you can:
- Direct web search using Perplexity Search API with ranked results
- General-purpose AI with real-time web integration for everyday questions
- Comprehensive research with thorough analysis and citations
This guide provides step-by-step instructions to set up Perplexity MCP Server in Amp, including configuration, examples, and troubleshooting.
What You'll Achieve
After completing this setup:
- Perplexity MCP Server will be fully integrated and operational
- You can use Perplexity MCP Server tools directly in Amp
- All Perplexity MCP Server capabilities will be available for your workflows
- Access to 4 different tools
Prerequisites
Before starting, ensure you have:
- Node.js 18+
- npm or npx
- Perplexity API key
- Your Perplexity API key for authentication with Sonar models
- Amp installed and configured
- Compatible operating system (macOS, Linux, Windows (WSL))
Installation
Step 1: Install Perplexity MCP Server
Install using npm:
npx -y perplexity-mcp
Verify installation:
Server starts and connects to MCP client
Configuration
Step 2: Configure Amp
-
Locate your configuration file:
-
Add server configuration:
Configure MCP servers in VS Code/Cursor settings.json:
```json
{
"amp.mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest", "--headless", "--isolated"]
},
"semgrep": {
"url": "https://mcp.semgrep.ai/mcp"
},
"sourcegraph": {
"url": "${SRC_ENDPOINT}/.api/mcp/v1",
"headers": {
"Authorization": "token ${SRC_ACCESS_TOKEN}"
}
},
"linear": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.linear.app/sse"]
}
}
}
Or add servers via CLI:
# Add HTTP-based server
amp mcp add sourcegraph --header "Authorization=token your-token" https://sourcegraph.example.com/.api/mcp/v1
# Add SSE-based server
amp mcp add linear https://mcp.linear.app/sse
# OAuth login for authenticated servers
amp mcp oauth login my-server \
--server-url https://example.com/.api/mcp/v1 \
--client-id your-client-id \
--client-secret your-client-secret \
--scopes "openid,profile,email"
3. **Restart Amp**
Completely quit and restart Amp to load the new configuration.
## Examples
Once configured, you can use Perplexity MCP Server in Amp:
### Real-Time Web Search
Search the web for current information and get ranked results
**Ask Amp:** "Search for the latest Model Context Protocol updates and announcements"
**Expected Result:** Ranked search results with titles, URLs, snippets, and metadata about MCP developments
### Quick Factual Queries
Get immediate answers to questions with web-backed accuracy
**Ask Amp:** "What are the system requirements for running Claude Desktop?"
**Expected Result:** Accurate, sourced answer with current system requirements and download links
### Deep Technical Research
Comprehensive analysis of complex technical topics
**Ask Amp:** "Research the differences between WebSocket, SSE, and HTTP polling for real-time applications"
**Expected Result:** Detailed comparison with citations, use cases, performance considerations, and recommendations
### Complex Problem Analysis
Advanced reasoning for technical decision-making
**Ask Amp:** "Analyze whether I should use Redis, Memcached, or PostgreSQL for caching in my Node.js application"
**Expected Result:** Step-by-step reasoning with trade-off analysis, benchmarks, and contextual recommendations
## Testing Your Setup
1. Launch Amp
2. Verify Perplexity MCP Server is available in the tools list
3. Test basic Perplexity MCP Server functionality
## Troubleshooting
### Common Issues
#### API Key Invalid or Missing
**Symptoms:** 401 Unauthorized errors, Authentication failed messages, API key not found
**Cause:** PERPLEXITY_API_KEY environment variable not set or invalid
**Solution:**
- Verify API key is set: echo $PERPLEXITY_API_KEY
- Obtain valid key from https://www.perplexity.ai/account/api
- Ensure key is exported in shell: export PERPLEXITY_API_KEY="pplx-xxx"
- Check for typos or extra whitespace in key value
#### Connection Timeout
**Symptoms:** Request timeout errors, Server not responding, Long delays with no response
**Cause:** Network issues or timeout too short for deep research queries
**Solution:**
- Increase timeout: export PERPLEXITY_TIMEOUT_MS=900000
- Check internet connectivity
- Verify firewall allows outbound HTTPS to api.perplexity.ai
- For deep research, expect longer response times (2-5 minutes)
#### Proxy Configuration Errors
**Symptoms:** Connection refused, Proxy authentication failed, Network unreachable in corporate environment
**Cause:** Incorrect or missing proxy configuration for enterprise networks
**Solution:**
- Set proxy: export PERPLEXITY_PROXY=https://user:pass@proxy:port
- Alternative: export HTTPS_PROXY=https://proxy:port
- Verify proxy credentials are correct
- Contact IT if proxy blocks API requests
#### NPX Installation Fails
**Symptoms:** npx command not found, Package download errors, Permission denied
**Cause:** Node.js not installed or npm registry issues
**Solution:**
- Install Node.js 18+ from https://nodejs.org
- Clear npm cache: npm cache clean --force
- Try with explicit version: npx -y perplexity-mcp@latest
- Check npm registry connectivity
#### Strip Thinking Parameter Not Working
**Symptoms:** Response contains <think>...</think> tags, Excessive context token usage
**Cause:** strip_thinking parameter not passed correctly
**Solution:**
- Include strip_thinking: true in perplexity_reason calls
- This removes internal reasoning from responses
- Reduces token usage while preserving final answers
#### MCP Server Not Connecting
**Symptoms:** Server not appearing in tools, Connection timeout, Authentication errors
**Cause:** Invalid configuration, missing credentials, or network issues
**Solution:**
- Verify server URL and command are correct
- Check environment variables are set properly
- For OAuth servers, run amp mcp oauth login
- Review amp logs for error messages
#### Tool Execution Fails
**Symptoms:** MCP tools available but not working, Error messages during execution
**Cause:** Server dependencies missing or permission issues
**Solution:**
- Verify required environment variables are configured
- Check amp.permissions settings for tool restrictions
- Test MCP server independently
- Review server-specific documentation
#### Permission Denied
**Symptoms:** Tool blocked by permission system, Ask prompts for every action
**Cause:** Permission rules restricting MCP tool usage
**Solution:**
- Review amp.permissions in settings.json
- Add allow rules for trusted MCP servers
- Use amp permissions edit to modify rules
#### Perplexity MCP Server not appearing in Amp
**Symptoms:** Server not listed, Tools not available
**Cause:** Configuration or installation issue
**Solution:**
- Verify configuration syntax
- Check Perplexity MCP Server installation
- Restart Amp
- Check logs for error messages
## Next Steps
Now that Perplexity MCP Server is integrated with Amp:
- Explore all Perplexity MCP Server capabilities through Amp
- Check out other MCP servers that work with Amp
- Join the MCP community for tips and support
- Consider contributing to Perplexity MCP Server development
## Need Help?
- Search for [Perplexity MCP Server documentation](https://www.mcpstack.org)
- Check the [Amp MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions