beginner⏱️ 10-20 minutes📅 Updated June 2026

Step-by-step guide to integrate APIWeaver MCP server with MCPHub (mcp.nvim). Includes dynamic api registration and multi-protocol support.

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

APIWeaver is a MCP server that An MCP server that dynamically creates MCP servers from web API configurations. This allows you to easily integrate any REST API, GraphQL endpoint, or web service into an MCP-compatible tool that can be used by AI assistants like Claude..

When integrated with MCPHub (mcp.nvim), you can:

  • Register and configure APIs at runtime without server restart
  • Support for REST APIs, GraphQL endpoints, and web services
  • Multiple authentication methods for different API requirements

This guide provides step-by-step instructions to set up APIWeaver in MCPHub (mcp.nvim), including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

  • APIWeaver will be fully integrated and operational
  • You can use APIWeaver tools directly in MCPHub (mcp.nvim)
  • All APIWeaver capabilities will be available for your workflows
  • Access to 6 different tools

Prerequisites

Before starting, ensure you have:

  • MCPHub (mcp.nvim) installed and configured
  • Compatible operating system (Neovim 0.9+, Windows, macOS, Linux)

Installation

Step 1: Install APIWeaver

Configuration

Step 2: Configure MCPHub (mcp.nvim)

  1. Open MCPHub (mcp.nvim) settings
  2. Navigate to MCP server configuration
  3. Add APIWeaver server with appropriate settings
  4. Save and restart if needed

Examples

Once configured, you can use APIWeaver in MCPHub (mcp.nvim):

Register REST API with Authentication

Add a REST API with Bearer token authentication

Ask MCPHub (mcp.nvim): "Register the JSONPlaceholder API (https://jsonplaceholder.typicode.com) with GET and POST methods"

Expected Result: API registered successfully with auto-generated tools for posts, users, and comments endpoints

GraphQL Endpoint Integration

Connect to a GraphQL API for data querying

Ask MCPHub (mcp.nvim): "Register the GitHub GraphQL API with authentication and create tools for repository queries"

Expected Result: GraphQL endpoint configured with query tools for repositories, issues, and user data

API Testing and Validation

Test API connectivity before integration

Ask MCPHub (mcp.nvim): "Test connection to the Stripe API with my API key before registering it"

Expected Result: Connection test successful with API schema validation and endpoint verification

Multi-API Workflow

Integrate multiple APIs for complex workflows

Ask MCPHub (mcp.nvim): "Register both Twitter API and SendGrid API to create a workflow for social media monitoring and email alerts"

Expected Result: Both APIs registered with tools for tweet monitoring, email sending, and automated workflow execution

Testing Your Setup

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

Troubleshooting

Common Issues

API Registration Failed

Symptoms: Registration errors, Invalid API configuration, Connection timeouts

Cause: Incorrect API URL, authentication issues, or network problems

Solution:

  • Verify API endpoint URL is accessible
  • Check authentication credentials are valid
  • Test API manually with curl or Postman first
  • Ensure network connectivity and firewall settings

Authentication Not Working

Symptoms: 401 Unauthorized, 403 Forbidden, Auth token invalid

Cause: Incorrect authentication method or invalid credentials

Solution:

  • Verify authentication method matches API requirements
  • Check API key/token is not expired
  • Confirm header format and parameter names
  • Test authentication with API documentation examples

Transport Mode Not Connecting

Symptoms: Connection refused, Transport errors, Client not recognizing server

Cause: Incorrect transport configuration or port conflicts

Solution:

  • Use streamable-http for modern clients
  • Check port is not in use: netstat -an | grep :8000
  • Verify host/port settings match client configuration
  • Try different transport modes (stdio/http/sse)

Python Dependencies Missing

Symptoms: Import errors, Module not found, Package installation failures

Cause: Missing Python packages or virtual environment issues

Solution:

  • Install requirements: pip install -r requirements.txt
  • Create virtual environment: python -m venv apiweaver-env
  • Activate environment before installation
  • Upgrade pip: python -m pip install --upgrade pip

API Schema Generation Failed

Symptoms: Tool generation errors, Schema parsing failures, Endpoint mapping issues

Cause: Unsupported API format or incomplete API documentation

Solution:

  • Provide OpenAPI/Swagger specification if available
  • Start with simple GET endpoints first
  • Manually configure complex APIs step by step
  • Check API documentation for required parameters

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

APIWeaver not appearing in MCPHub (mcp.nvim)

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

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

  • Explore all APIWeaver 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 APIWeaver development

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with MCPHub (mcp.nvim)

Need Help?

Join the MCP community for support and discussions

APIWeaver + MCPHub (mcp.nvim): MCP Setup Guide (2026)