MCPHub Neovim Setup Guide

This plugin centralizes MCP management for all Neovim AI tools.

Tools like Avante, CodeCompanion, and—I expect—whatever will come next.

It’s time to level-up your Neovim game with MCP.

Check out the video on YouTube

Course Update: Audio

If you subscribe to my newsletter then you know I’ve been “milking this one” for a while.

But it was a s*** ton of work.

So, one last time, if you don’t mind.

Lesson audio is here! 🎉

I’ve added AI narrations for all 96 lessons.

I even transcribed the math and code snippets.

Have a listen and let me know what you think.

No really, let me know. You can reply to this email!

Topics from this week’s video

• Introduction to MCP Hub

  • Enables access to MCP servers and acts as a marketplace.

  • Integrates with NeoVim tools through extensions.

• NeoVim Configuration (Dotfiles)

  • Explain the file structure: ~/.config/nvim/init.lua for main configuration.

  • Use of plugins/lazy.lua for plugin setups.

  • Explains nvc alias for quick access to the NeoVim configuration directory.

• Installation with Lazy (NeoVim Plugin Manager)

  • Install MCPHub.

  • Demonstrate how Lazy automatically installs and uninstalls plugins.

• Setting up MCP Hub with Avante (NeoVim Tool)

  • Configure MCP Hub as an extension within Avante.

  • Show how to open MCP Hub using the :MCPHub command.

  • Navigating MCP Hub:

    • l to expand, t to toggle.

    • h for back, l for forward, j for down, k for up (Vim keybindings).

    • Capital letters (e.g., M for marketplace) for navigation.

• Exploring the MCP Hub Marketplace

  • Searching for servers (e.g., “time” or “stocks”).

  • Highlight the time server as an example.

• Installing and Running MCP Servers

  • Automated Installation (via Avante):

    • Attempt to use Avante’s AI install option.

  • Manual Installation (Recommended):

    • Directly adding server configurations to ~/.config/mcphub/servers.json.

    • Demonstrate running an MCP server using Docker.

• Interacting with MCP Hub Servers

  • Using Avante:

    • How to trigger a tool call (e.g., asking “what time it is”) within Avante.

    • Issues encountered with Avante, such as rate limits and lack of clear cost tracking.

  • Using Code Companion:

    • Configure MCPHub as an extension within Code Companion.

    • Shows how to trigger MCP tool calls using @mcp prefix (e.g., @mcp What time is it?).

    • Difficulties with Code Companion configuration and tool integration.

• Cost Considerations

  • Importance of tracking costs associated with AI tool usage.

  • This demonstration cost $1 USD.

---

I’ve yet to see any problem, however complicated, which when you looked at it the right way didn’t become still more complicated.

Poul Anderson