Perplexity MCP Server + OpenCode: 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 OpenCode, 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 OpenCode, 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 OpenCode
- 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
- OpenCode installed and configured
- Compatible operating system (macOS, Linux, Windows)
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 OpenCode
-
Locate your configuration file:
-
Add server configuration:
Configure MCP servers in your `opencode.json` or `opencode.jsonc`:
```json
{
"mcp": {
"my-mcp": {
"type": "local",
"command": ["npx", "-y", "@modelcontextprotocol/server-everything"],
"environment": {
"API_KEY": "$API_KEY"
},
"timeout": 5000
},
"remote-server": {
"type": "remote",
"url": "https://mcp.example.com/sse",
"headers": {
"Authorization": "Bearer $API_TOKEN"
}
}
}
}
Disable a server temporarily:
{
"mcp": {
"my-mcp": {
"type": "local",
"command": ["npx", "-y", "mcp-server"],
"enabled": false
}
}
}
3. **Restart OpenCode**
Completely quit and restart OpenCode to load the new configuration.
## Examples
Once configured, you can use Perplexity MCP Server in OpenCode:
### Real-Time Web Search
Search the web for current information and get ranked results
**Ask OpenCode:** "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 OpenCode:** "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 OpenCode:** "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 OpenCode:** "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. Run opencode in terminal
2. Add "use the mcp_name tool" to your prompts
3. Verify tool execution and response
## 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 Loading
**Symptoms:** Server not appearing in tools, Timeout errors, Command not found
**Cause:** Invalid configuration, missing dependencies, or timeout too short
**Solution:**
- Verify command array is correct in opencode.json
- Check environment variables are set properly
- Increase timeout value if server takes longer to start
- Test MCP server command independently in terminal
#### Context Limit Exceeded
**Symptoms:** Context too large errors, Slow responses, Truncated output
**Cause:** Too many MCP servers adding to context
**Solution:**
- Disable unused MCP servers with enabled: false
- Use per-agent tool configuration to limit active MCPs
- Avoid MCP servers that add many tokens (e.g., GitHub MCP)
#### Remote Server Connection Failed
**Symptoms:** Cannot connect to remote MCP, Authentication errors
**Cause:** Invalid URL, missing headers, or network issues
**Solution:**
- Verify remote server URL is correct
- Check authorization headers are properly configured
- Ensure environment variables for tokens are set
#### Perplexity MCP Server not appearing in OpenCode
**Symptoms:** Server not listed, Tools not available
**Cause:** Configuration or installation issue
**Solution:**
- Verify configuration syntax
- Check Perplexity MCP Server installation
- Restart OpenCode
- Check logs for error messages
## Next Steps
Now that Perplexity MCP Server is integrated with OpenCode:
- Explore all Perplexity MCP Server capabilities through OpenCode
- Check out other MCP servers that work with OpenCode
- 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 [OpenCode MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions