beginner⏱️ 16-26 minutes📅 Updated June 2026

Step-by-step guide to integrate Agentset MCP server with Msty Studio. Includes search_knowledge_base and get_document.

Agentset + Msty Studio: Complete MCP Integration

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

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

Installation

Step 1: Install Agentset

Configuration

Step 2: Configure Msty Studio

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

Technical Documentation Search

undefined

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

Expected Result: undefined

Code Example Retrieval

undefined

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

Expected Result: undefined

Policy and Procedure Lookup

undefined

Ask Msty Studio: "What's our deployment approval process?"

Expected Result: undefined

Testing Your Setup

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

Agentset not appearing in Msty Studio

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Agentset is integrated with Msty Studio:

  • Explore all Agentset 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 Agentset 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

Agentset + Msty Studio: MCP Setup Guide (2026)