Agentset + Amazon Q CLI: Complete MCP Integration

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

When integrated with Amazon Q 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 Amazon Q 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 Amazon Q 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
• Amazon Q CLI installed and configured
• Compatible operating system (Windows, macOS, Linux)

Installation

Step 1: Install Agentset

Configuration

Step 2: Configure Amazon Q CLI

1. Install Amazon Q CLI

Download and install Q CLI for your platform

Visit: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html

2. Authenticate

Set up authentication with AWS Builder ID or IAM Identity Center

q auth

Note: Follow interactive authentication flow

3. Verify Installation

Test Q CLI installation and configuration

q doctor

4. Install MCP Server

Install the MCP server you want to integrate

Note: Ensure server is accessible from command line

5. Configure MCP Integration

Add MCP server configuration to Q CLI

Note: Use q config commands to set server parameters

6. Test Integration

Verify MCP server works with Q CLI

q chat "Use Agentset to help me"

Configuration Details

Configure MCP servers through Q CLI commands:

# Configure MCP server integration
q config set mcp.servers.agentset.command "agentset"
q config set mcp.servers.agentset.args ""
q config set mcp.servers.agentset.env ""AGENTSET_API_KEY": "as_1234567890abcdef",
        "AGENTSET_NAMESPACE_ID": "ns_workspace123",
        "AGENTSET_TENANT_ID": "tenant_abc123""

# Verify configuration
q config list mcp.servers

Examples

Once configured, you can use Agentset in Amazon Q CLI:

Technical Documentation Search

undefined

Ask Amazon Q CLI: "How do I configure SSL certificates in our system?"

Expected Result: undefined

Code Example Retrieval

undefined

Ask Amazon Q CLI: "Show me examples of error handling in our codebase"

Expected Result: undefined

Policy and Procedure Lookup

undefined

Ask Amazon Q CLI: "What's our deployment approval process?"

Expected Result: undefined

Testing Your Setup

1. Run q doctor to verify system health
2. Start Q CLI chat session
3. Ask Q to list available MCP tools
4. Test specific Agentset functionality

Test commands:

q doctor

q chat

q config list mcp.servers

Troubleshooting

Common Issues

Installation Failed

Symptoms: Q command not found, Installation errors

Cause: Incomplete installation or PATH issues

Solution:

• Verify installer completed successfully
• Check PATH environment variable includes Q CLI
• Try running q doctor for diagnostics
• Reinstall using platform-specific method

Authentication Problems

Symptoms: Auth errors, Cannot connect to AWS services

Cause: Invalid credentials or network issues

Solution:

• Run q auth to re-authenticate
• Verify AWS Builder ID or IAM credentials
• Check network connectivity to AWS
• Ensure proper AWS permissions are set

MCP Server Not Found

Symptoms: Server command not found, MCP tools unavailable

Cause: Server not installed or not in PATH

Solution:

• Verify MCP server installation
• Check server executable permissions
• Use absolute path in configuration
• Test server independently with direct command

Configuration Errors

Symptoms: Config commands fail, Settings not persisting

Cause: Invalid configuration syntax or permissions

Solution:

• Check Q CLI configuration file permissions
• Verify configuration syntax is correct
• Use q config list to review current settings
• Report issues with q issue command

Agentset not appearing in Amazon Q CLI

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Agentset installation
• Restart Amazon Q CLI
• Check logs for error messages

Next Steps

Now that Agentset is integrated with Amazon Q CLI:

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

Need Help?

• Search for Agentset documentation
• Check the Amazon Q CLI MCP guide
• Join the MCP community discussions