Agentset + MCPHub (mcp.nvim): Complete MCP Integration

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

When integrated with MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim)
• 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
• MCPHub (mcp.nvim) installed and configured
• Compatible operating system (Neovim 0.9+, Windows, macOS, Linux)

Installation

Step 1: Install Agentset

Configuration

Step 2: Configure MCPHub (mcp.nvim)

1. Open MCPHub (mcp.nvim) 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 MCPHub (mcp.nvim):

Technical Documentation Search

undefined

Ask MCPHub (mcp.nvim): "How do I configure SSL certificates in our system?"

Expected Result: undefined

Code Example Retrieval

undefined

Ask MCPHub (mcp.nvim): "Show me examples of error handling in our codebase"

Expected Result: undefined

Policy and Procedure Lookup

undefined

Ask MCPHub (mcp.nvim): "What's our deployment approval process?"

Expected Result: undefined

Testing Your Setup

1. Launch MCPHub (mcp.nvim)
2. Verify Agentset is available in the tools list
3. Test basic Agentset functionality

Troubleshooting

Common Issues

Plugin Not Loading or Command Not Found

Symptoms: :MCPHub command not recognized, Plugin not appearing in :PlugStatus, No errors but plugin inactive

Cause: Plugin not properly installed or configuration error

Solution:

• Verify plugin is added to plugin manager configuration
• Run plugin manager install command (:PackerInstall, :PlugInstall, or Lazy auto-install)
• Check for errors in :messages after sourcing config
• Ensure dependencies (plenary.nvim, nui.nvim) are installed
• Restart Neovim completely

MCP Server Won't Start

Symptoms: Server status shows "Error", Red indicator on server, Server immediately stops after starting

Cause: Invalid server configuration or missing dependencies

Solution:

• Verify npx is installed and in PATH: npx --version
• Check MCP server package exists: npx -y @modelcontextprotocol/server-filesystem --help
• Review server configuration in setup() - verify command and args
• Check server logs in MCPHub interface for detailed error messages
• Ensure required environment variables are set (e.g., GITHUB_TOKEN)
• Test server manually in terminal: npx -y @modelcontextprotocol/server-filesystem /path

UI Not Displaying Correctly

Symptoms: Blank window, Garbled text, Layout issues, Missing borders

Cause: Terminal or Neovim rendering issues

Solution:

• Verify Neovim version is 0.9 or higher: nvim --version
• Try different border style in ui.border config ("single", "double", "rounded")
• Check terminal supports Unicode and 256 colors
• Update nui.nvim dependency to latest version
• Test with different colorscheme to rule out theme conflicts

Integration with Avante/CodeCompanion Not Working

Symptoms: AI assistant not seeing MCP tools, Tool calls failing, Integration not recognized

Cause: Integration not enabled or incompatible versions

Solution:

• Verify integration is enabled in config: integrations.avante = true
• Ensure Avante.nvim/CodeCompanion.nvim is installed and loaded
• Check versions are compatible - update both plugins to latest
• Restart Neovim after enabling integration
• Check :checkhealth for integration-specific warnings

Marketplace Not Loading

Symptoms: :MCPHubMarketplace shows empty list, Network error in marketplace, Timeout loading servers

Cause: Network connectivity issues or marketplace service unavailable

Solution:

• Verify internet connectivity
• Check firewall allows HTTPS connections
• Try again later if marketplace service is temporarily down
• Review proxy settings if behind corporate firewall
• Check :messages for detailed network error messages

Project-Local Config Not Loading

Symptoms: .mcphub.json ignored, Project servers not appearing, Only global config loaded

Cause: Config file location or format issues

Solution:

• Verify .mcphub.json is in project root (same directory as .git)
• Check JSON syntax is valid using jsonlint or similar tool
• Ensure file name is exactly .mcphub.json (case-sensitive)
• Restart Neovim after creating/modifying project config
• Check file permissions are readable

Agentset not appearing in MCPHub (mcp.nvim)

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Agentset installation
• Restart MCPHub (mcp.nvim)
• Check logs for error messages

Next Steps

Now that Agentset is integrated with MCPHub (mcp.nvim):

• Explore all Agentset capabilities through MCPHub (mcp.nvim)
• Check out other MCP servers that work with MCPHub (mcp.nvim)
• Join the MCP community for tips and support
• Consider contributing to Agentset development

Need Help?

• Search for Agentset documentation
• Check the MCPHub (mcp.nvim) MCP guide
• Join the MCP community discussions