Perplexity MCP Server + Amazon Q CLI: 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 Amazon Q CLI, 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 Amazon Q CLI, 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 Amazon Q CLI
- 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
- Amazon Q CLI installed and configured
- Compatible operating system (Windows, macOS, Linux)
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 Amazon Q CLI
- Install Amazon Q CLI
Download and install Q CLI for your platform
Visit: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html
- Authenticate
Set up authentication with AWS Builder ID or IAM Identity Center
q auth
Note: Follow interactive authentication flow
- Verify Installation
Test Q CLI installation and configuration
q doctor
- Install MCP Server
Install the MCP server you want to integrate
Note: Ensure server is accessible from command line
- Configure MCP Integration
Add MCP server configuration to Q CLI
Note: Use q config commands to set server parameters
- Test Integration
Verify MCP server works with Q CLI
q chat "Use Perplexity MCP Server to help me"
Configuration Details
Configure MCP servers through Q CLI commands:
# Configure MCP server integration
q config set mcp.servers.perplexity-mcp-server.command "npx"
q config set mcp.servers.perplexity-mcp-server.args ""-y", "perplexity-mcp""
q config set mcp.servers.perplexity-mcp-server.env ""PERPLEXITY_API_KEY": "pplx-xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"PERPLEXITY_TIMEOUT_MS": "300000",
"PERPLEXITY_PROXY": "https://username:password@proxy-host:port",
"PORT": "3000",
"BIND_ADDRESS": "0.0.0.0",
"ALLOWED_ORIGINS": "https://yourdomain.com""
# Verify configuration
q config list mcp.servers
Examples
Once configured, you can use Perplexity MCP Server in Amazon Q CLI:
Real-Time Web Search
Search the web for current information and get ranked results
Ask Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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
- Run q doctor to verify system health
- Start Q CLI chat session
- Ask Q to list available MCP tools
- Test specific Perplexity MCP Server functionality
Test commands:
q doctor
q chat
q config list mcp.servers
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
Installation Failed
Symptoms: Q command not found, Installation errors
Cause: Incomplete installation or PATH issues
Solution:
- Verify installer completed successfully
- Check PATH environment variable includes Q CLI
- Try running q doctor for diagnostics
- Reinstall using platform-specific method
Authentication Problems
Symptoms: Auth errors, Cannot connect to AWS services
Cause: Invalid credentials or network issues
Solution:
- Run q auth to re-authenticate
- Verify AWS Builder ID or IAM credentials
- Check network connectivity to AWS
- Ensure proper AWS permissions are set
MCP Server Not Found
Symptoms: Server command not found, MCP tools unavailable
Cause: Server not installed or not in PATH
Solution:
- Verify MCP server installation
- Check server executable permissions
- Use absolute path in configuration
- Test server independently with direct command
Configuration Errors
Symptoms: Config commands fail, Settings not persisting
Cause: Invalid configuration syntax or permissions
Solution:
- Check Q CLI configuration file permissions
- Verify configuration syntax is correct
- Use q config list to review current settings
- Report issues with q issue command
Perplexity MCP Server not appearing in Amazon Q CLI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Perplexity MCP Server installation
- Restart Amazon Q CLI
- Check logs for error messages
Next Steps
Now that Perplexity MCP Server is integrated with Amazon Q CLI:
- Explore all Perplexity MCP Server capabilities through Amazon Q CLI
- Check out other MCP servers that work with Amazon Q CLI
- Join the MCP community for tips and support
- Consider contributing to Perplexity MCP Server development
Need Help?
- Search for Perplexity MCP Server documentation
- Check the Amazon Q CLI MCP guide
- Join the MCP community discussions