AllVoiceLab + mcphub.nvim: Complete MCP Integration

AllVoiceLab is a MCP server that An AI voice toolkit with TTS, voice cloning, and video translation, now available as an MCP server for smarter agent integration..

When integrated with mcphub.nvim, you can:

• Access AllVoiceLab functionality through mcphub.nvim

This guide provides step-by-step instructions to set up AllVoiceLab in mcphub.nvim, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• AllVoiceLab will be fully integrated and operational
• You can use AllVoiceLab tools directly in mcphub.nvim
• All AllVoiceLab capabilities will be available for your workflows

Prerequisites

Before starting, ensure you have:

• mcphub.nvim installed and configured
• Compatible operating system (Neovim)

Installation

Step 1: Install AllVoiceLab

Configuration

Step 2: Configure mcphub.nvim

1. Locate your configuration file:

   • Windows: %LOCALAPPDATA%\mcphub\servers.json
   • macOS: ~/.config/mcphub/servers.json
   • Linux: ~/.config/mcphub/servers.json

2. Add server configuration:

{
  "mcpServers": {
    "allvoicelab": {
      "command": "allvoicelab",
      "args": [],
      "env": {
        
      }
    }
  }
}

3. Restart mcphub.nvim

Completely quit and restart mcphub.nvim to load the new configuration.

Examples

Once configured, you can use AllVoiceLab in mcphub.nvim:

Testing Your Setup

1. Launch mcphub.nvim
2. Verify AllVoiceLab is available in the tools list
3. Test basic AllVoiceLab functionality

Troubleshooting

Common Issues

Servers not showing in :McpHub

Symptoms: Empty server list, Configuration not loaded

Cause: Incorrect configuration file path or JSON syntax error

Solution:

• Verify servers.json exists in ~/.config/mcphub/ or .vscode/mcp.json in project root
• Check JSON syntax for errors (trailing commas, missing quotes)
• Run :checkhealth mcphub to diagnose issues

Tool execution fails

Symptoms: Error message when AI tries to use tool, No response

Cause: Server command failed or environment variables missing

Solution:

• Check server logs in :McpHub
• Verify "command" path is correct and executable
• Ensure required environment variables are set in the config

Chat plugin not recognizing tools

Symptoms: AI says it cannot perform the action, Tools not listed in chat

Cause: Integration issue with the specific chat plugin

Solution:

• Ensure you are using a supported version of the chat plugin
• Check mcphub.nvim documentation for plugin-specific setup instructions
• Restart Neovim to reload the integration

AllVoiceLab not appearing in mcphub.nvim

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check AllVoiceLab installation
• Restart mcphub.nvim
• Check logs for error messages

Next Steps

Now that AllVoiceLab is integrated with mcphub.nvim:

• Explore all AllVoiceLab capabilities through mcphub.nvim
• Check out other MCP servers that work with mcphub.nvim
• Join the MCP community for tips and support
• Consider contributing to AllVoiceLab development

Need Help?

• Search for AllVoiceLab documentation
• Check the mcphub.nvim MCP guide
• Join the MCP community discussions