Agentset + Perplexity: Complete MCP Integration

Agentset is a MCP server that RAG for your knowledge base connected to Agentset..

When integrated with Perplexity, you can:

• Search through indexed documents using RAG
• Retrieve specific document by ID
• Perform semantic search across knowledge base

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

What You'll Achieve

After completing this setup:

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

Prerequisites

Before starting, ensure you have:

• API key from Agentset dashboard
• Namespace identifier for knowledge base
• Perplexity installed and configured
• Compatible operating system (macOS App)

Installation

Step 1: Install Agentset

Configuration

Step 2: Configure Perplexity

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

Examples

Once configured, you can use Agentset in Perplexity:

Technical Documentation Search

undefined

Ask Perplexity: "How do I configure SSL certificates in our system?"

Expected Result: undefined

Code Example Retrieval

undefined

Ask Perplexity: "Show me examples of error handling in our codebase"

Expected Result: undefined

Policy and Procedure Lookup

undefined

Ask Perplexity: "What's our deployment approval process?"

Expected Result: undefined

Testing Your Setup

1. Launch Perplexity
2. Verify Agentset is available in the tools list
3. Test basic Agentset 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.

Agentset not appearing in Perplexity

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Agentset is integrated with Perplexity:

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

Need Help?

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