beginner⏱️ 12-22 minutes📅 Updated August 2026

Step-by-step guide to integrate AgentOps MCP server with Perplexity. Includes auth and get_trace.

AgentOps + Perplexity: Complete MCP Integration

AgentOps is a MCP server that Provide observability and tracing for debugging AI agents with AgentOps API..

When integrated with Perplexity, you can:

  • Authorize with AgentOps API key
  • Retrieve trace information by ID
  • Get span information by ID

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

What You'll Achieve

After completing this setup:

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

Prerequisites

Before starting, ensure you have:

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

Installation

Step 1: Install AgentOps

Configuration

Step 2: Configure Perplexity

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

Examples

Once configured, you can use AgentOps in Perplexity:

Agent Performance Debugging

undefined

Ask Perplexity: "Show me traces for agent runs that failed today"

Expected Result: undefined

Cost Analysis

undefined

Ask Perplexity: "Get cost breakdown for trace abc123"

Expected Result: undefined

Performance Optimization

undefined

Ask Perplexity: "Show slowest spans in recent traces"

Expected Result: undefined

Testing Your Setup

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

AgentOps not appearing in Perplexity

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that AgentOps is integrated with Perplexity:

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

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with Perplexity

Need Help?

Join the MCP community for support and discussions

AgentOps + Perplexity: MCP Setup Guide (2026)