beginner⏱️ 12-22 minutes📅 Updated August 2026

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

AgentOps + Witsy: Complete MCP Integration

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

When integrated with Witsy, 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 Witsy, 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 Witsy
  • 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
  • Witsy installed and configured
  • Compatible operating system (Desktop App)

Installation

Step 1: Install AgentOps

Configuration

Step 2: Configure Witsy

  1. Open Witsy 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 Witsy:

Agent Performance Debugging

undefined

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

Expected Result: undefined

Cost Analysis

undefined

Ask Witsy: "Get cost breakdown for trace abc123"

Expected Result: undefined

Performance Optimization

undefined

Ask Witsy: "Show slowest spans in recent traces"

Expected Result: undefined

Testing Your Setup

  1. Launch Witsy
  2. Verify AgentOps is available in the tools list
  3. Test basic AgentOps functionality

Troubleshooting

Common Issues

Server Start Failure

Symptoms: Error notification, Tools not listed

Cause: Incorrect command path or missing dependencies (Node/Python).

Solution:

  • Ensure node, npm, or python are in the system PATH seen by Witsy.
  • Try using absolute paths to executables.

Permission Denied

Symptoms: Witsy cannot read file, Operation blocked

Cause: OS security settings or MCP server restrictions.

Solution:

  • Check macOS privacy settings.
  • Ensure the MCP server is started with access to the correct directories.

AgentOps not appearing in Witsy

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that AgentOps is integrated with Witsy:

  • Explore all AgentOps capabilities through Witsy
  • Check out other MCP servers that work with Witsy
  • 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 Witsy

Need Help?

Join the MCP community for support and discussions

AgentOps + Witsy: MCP Setup Guide (2026)