Agentset + Rovo Dev CLI: Complete MCP Integration
Agentset is a MCP server that RAG for your knowledge base connected to Agentset..
When integrated with Rovo Dev CLI, 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 Rovo Dev CLI, 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 Rovo Dev CLI
- 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
- Rovo Dev CLI installed and configured
- Compatible operating system (Windows, macOS, Linux)
Installation
Step 1: Install Agentset
Configuration
Step 2: Configure Rovo Dev CLI
- Open Rovo Dev CLI settings
- Navigate to MCP server configuration
- Add Agentset server with appropriate settings
- Save and restart if needed
Examples
Once configured, you can use Agentset in Rovo Dev CLI:
Technical Documentation Search
undefined
Ask Rovo Dev CLI: "How do I configure SSL certificates in our system?"
Expected Result: undefined
Code Example Retrieval
undefined
Ask Rovo Dev CLI: "Show me examples of error handling in our codebase"
Expected Result: undefined
Policy and Procedure Lookup
undefined
Ask Rovo Dev CLI: "What's our deployment approval process?"
Expected Result: undefined
Testing Your Setup
- Run acli rovodev run to start interactive mode
- Ask for code generation or explanation
- Test integration with Jira/Confluence features
Troubleshooting
Common Issues
Authentication Failed
Symptoms: Cannot login, API token rejected
Cause: Invalid or expired API token
Solution:
- Regenerate API token in Atlassian profile
- Verify account has Rovo access
- Check network connectivity
- Re-run acli rovodev auth login
Beta Access Limited
Symptoms: Access denied, Beta not available
Cause: Beta capacity limits reached
Solution:
- Check Atlassian announcements for availability
- Join waitlist if available
- Verify account eligibility for beta access
Agentset not appearing in Rovo Dev CLI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Agentset installation
- Restart Rovo Dev CLI
- Check logs for error messages
Next Steps
Now that Agentset is integrated with Rovo Dev CLI:
- Explore all Agentset capabilities through Rovo Dev CLI
- Check out other MCP servers that work with Rovo Dev CLI
- Join the MCP community for tips and support
- Consider contributing to Agentset development
Need Help?
- Search for Agentset documentation
- Check the Rovo Dev CLI MCP guide
- Join the MCP community discussions