AgentMode + Perplexity: Complete MCP Integration

AgentMode is a MCP server that Connect to dozens of databases, data warehouses, Github & more, from a single MCP server. Run the Docker image locally, in the cloud, or on-premise..

When integrated with Perplexity, you can:

• Execute SQL queries across connected databases
• Interact with GitHub repositories and issues
• Connect to data warehouses like Snowflake, BigQuery

This guide provides step-by-step instructions to set up AgentMode in Perplexity, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• AgentMode will be fully integrated and operational
• You can use AgentMode tools directly in Perplexity
• All AgentMode capabilities will be available for your workflows
• Access to 3 different tools

Prerequisites

Before starting, ensure you have:

• API key from AgentMode dashboard
• Workspace identifier
• Perplexity installed and configured
• Compatible operating system (macOS App)

Installation

Step 1: Install AgentMode

Configuration

Step 2: Configure Perplexity

1. Open Perplexity settings
2. Navigate to MCP server configuration
3. Add AgentMode server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use AgentMode in Perplexity:

Multi-Database Analytics

undefined

Ask Perplexity: "Show me user engagement metrics from both databases"

Expected Result: undefined

GitHub Issue Management

undefined

Ask Perplexity: "Create issues for users with failed payments"

Expected Result: undefined

Data Pipeline Monitoring

undefined

Ask Perplexity: "Check status of yesterday's data pipeline runs"

Expected Result: undefined

Testing Your Setup

1. Launch Perplexity
2. Verify AgentMode is available in the tools list
3. Test basic AgentMode functionality

Troubleshooting

Common Issues

Connector Fails to Start

Symptoms: Status remains "Inactive" or shows error, Red dot indicator

Cause: Command not found or missing dependencies in the environment.

Solution:

• Test the command in a regular terminal window to ensure it works.
• Use absolute paths for all executables (e.g., use /opt/homebrew/bin/node instead of node).
• Check if the server requires specific environment variables.

Permission Errors

Symptoms: "Access denied" responses, Server crashes on file access

Cause: macOS permissions blocking access to specific folders.

Solution:

• Ensure Perplexity (or the terminal running the server) has Full Disk Access in macOS System Settings if accessing sensitive directories.
• Verify PerplexityXPC is correctly installed.

Tools Not Visible

Symptoms: Perplexity does not attempt to use the tool, Hallucinated responses

Cause: Connector not selected as a source.

Solution:

• Start a NEW thread.
• Explicitly select the connector in the "Sources" menu before sending the prompt.

AgentMode not appearing in Perplexity

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check AgentMode installation
• Restart Perplexity
• Check logs for error messages

Next Steps

Now that AgentMode is integrated with Perplexity:

• Explore all AgentMode capabilities through Perplexity
• Check out other MCP servers that work with Perplexity
• Join the MCP community for tips and support
• Consider contributing to AgentMode development

Need Help?

• Search for AgentMode documentation
• Check the Perplexity MCP guide
• Join the MCP community discussions