beginner⏱️ 12-22 minutes📅 Updated August 2026

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

AgentOps + Msty Studio: Complete MCP Integration

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

When integrated with Msty Studio, 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 Msty Studio, 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 Msty Studio
  • 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
  • Msty Studio installed and configured
  • Compatible operating system (Desktop (Windows), Desktop (macOS), Desktop (Linux), Web Application)

Installation

Step 1: Install AgentOps

Configuration

Step 2: Configure Msty Studio

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

Agent Performance Debugging

undefined

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

Expected Result: undefined

Cost Analysis

undefined

Ask Msty Studio: "Get cost breakdown for trace abc123"

Expected Result: undefined

Performance Optimization

undefined

Ask Msty Studio: "Show slowest spans in recent traces"

Expected Result: undefined

Testing Your Setup

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

Troubleshooting

Common Issues

MCP Server Not Connecting

Symptoms: Server shows disconnected status, Tool calls fail, Timeout errors

Cause: Invalid configuration or server not accessible

Solution:

  • Verify MCP server URL or command is correct
  • For STDIO servers, ensure Node.js and npx are installed
  • Check firewall settings allow connections
  • Review server logs in Toolbox dashboard
  • Test server independently outside Msty

Local Model Performance Issues

Symptoms: Slow response times, High memory usage, System freezes

Cause: Model size exceeds hardware capabilities

Solution:

  • Use smaller model variants (e.g., Llama 3 8B instead of 70B)
  • Enable quantization for reduced memory footprint
  • Close other applications to free resources
  • Consider using cloud models for complex tasks
  • Check system requirements for selected model

Privacy Mode Not Working

Symptoms: Data appears to be sent externally, Telemetry detected, Unexpected network activity

Cause: Cloud models or online MCP servers configured

Solution:

  • Ensure using only local models (Llama.cpp-based)
  • Configure STDIO MCP servers instead of HTTP/SSE
  • Disable internet connection to verify offline capability
  • Review Insights dashboard for token usage (should be zero for local)
  • Check Privacy settings are configured correctly

Turnstile Workflow Failures

Symptoms: Workflow stops mid-execution, Steps not triggering, Incorrect branching

Cause: Logic errors or MCP server issues

Solution:

  • Test each workflow step individually
  • Verify all MCP servers in workflow are connected
  • Review workflow logic and conditions
  • Check Turnstile logs for execution errors
  • Simplify complex workflows for debugging

Cross-Device Sync Problems

Symptoms: Settings not syncing, Conversations missing, Inconsistent state

Cause: Sync service issues or Aurum plan not active

Solution:

  • Verify Aurum plan is active and current
  • Check internet connection on all devices
  • Manually trigger sync from settings
  • Review sync logs for errors
  • Contact support if issues persist

AgentOps not appearing in Msty Studio

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that AgentOps is integrated with Msty Studio:

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

Need Help?

Join the MCP community for support and discussions

AgentOps + Msty Studio: MCP Setup Guide (2026)