mcphub.nvim MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

Verified marketplace of MCP servers with one-command install
Full MCP feature support: tools, resources, templates, prompts
OAuth PKCE + API key auth
Integration with Avante.nvim, CodeCompanion.nvim, CopilotChat.nvim
Project-local config merging, JSON5 config syntax

Démo en direct

Aperçu en pratique

mcphub-nvim.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "mcphub-nvim": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/ravitemer/mcphub.nvim"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "mcphub-nvim": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/ravitemer/mcphub.nvim"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "mcphub-nvim": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/ravitemer/mcphub.nvim"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcphub-nvim": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/ravitemer/mcphub.nvim"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "mcphub-nvim",
      "command": "TODO",
      "args": [
        "See README: https://github.com/ravitemer/mcphub.nvim"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "mcphub-nvim": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/ravitemer/mcphub.nvim"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add mcphub-nvim -- TODO 'See README: https://github.com/ravitemer/mcphub.nvim'

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcphub.nvim

How to use MCP servers from Neovim via Avante or CodeCompanion

👤 Neovim devs ⏱ ~20 min intermediate

Quand l'utiliser : You live in Neovim and don't want to switch to VS Code for MCP access.

Prérequis

Neovim 0.10+ — brew install neovim
Avante.nvim or CodeCompanion.nvim installed — Via your plugin manager (lazy.nvim/packer)
mcphub.nvim + its Node dependency — See ravitemer.github.io/mcphub.nvim for install snippet

Déroulement

Install via plugin manager

Add ravitemer/mcphub.nvim to your lazy.nvim config with opts = { ... }.✓ Copié

→ :MCPHub opens the management UI
Install a server from the marketplace

:MCPHub marketplace — search 'github' and install.✓ Copié

→ Server starts, tools registered
Use via Avante

In Avante chat, ask a question — Avante picks up MCP tools.✓ Copié

→ Tool calls visible in Avante output

Résultat : MCP tools usable inside your editor, no context switch.

Pièges

Node not on PATH inside Neovim — Use an absolute path in config or ensure Neovim inherits your shell env

How to set up project-local MCP servers that merge with global

👤 Polyglot devs with different tooling per project ⏱ ~15 min intermediate

Quand l'utiliser : One project needs postgres MCP, another needs a bespoke internal MCP.

Déroulement

Create .mcphub.json5 at project root

Define project-specific servers in .mcphub.json5.✓ Copié

→ Servers auto-load when you open the project
Verify merge

:MCPHub status — see which servers are global vs project.✓ Copié

→ Merged view

Résultat : Context-aware tool loadout per project.

Pièges

Committing secrets in .mcphub.json5 — Use env var references, gitignore the file if it must contain tokens

How to iterate on a custom MCP server from Neovim

👤 MCP server authors ⏱ ~15 min advanced

Quand l'utiliser : You're building a server and want fast iteration.

Déroulement

Enable dev mode

Add your server with dev=true in mcphub config.✓ Copié

→ Hot-reload on file save
Iterate

Edit server code; mcphub restarts it transparently.✓ Copié

→ Updated tools without Neovim restart

Résultat : Tight dev loop inside Neovim.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

mcphub-nvim + github

Use GitHub MCP from Neovim via Avante chat

Install github MCP via marketplace, then ask Avante to show PRs assigned to me.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
(plugin) :MCPHub	Commands: status, marketplace, install, logs	Manage servers	free
(plugin) marketplace-install	server_name	Quickly add a vetted MCP	free
(integration) Avante/CodeCompanion/CopilotChat tools	Chat prompts	Normal chat usage	1 LLM call + tool calls

Coût et limites

Coût d'exécution

Quota d'API: None (plugin itself)
Tokens par appel: Adds a tools list to Avante/CC prompts
Monétaire: Free (MIT)
Astuce: Disable unused marketplace servers — each one adds tools to your prompt budget.

Sécurité

Permissions, secrets, portée

Portées minimales : Whatever each installed MCP needs

Stockage des identifiants : Env var references in mcphub config

Sortie de données : Per downstream MCP

Ne jamais accorder : Don't commit .mcphub.json5 with inline secrets

Marketplace entries are community-submitted — verify publisher before installing.

Dépannage

Erreurs courantes et correctifs

mcphub fails to start Node subprocess

Neovim's PATH may not include Node. Set vim.env.PATH or use absolute path.

Vérifier : :!which node

Avante doesn't see MCP tools

Check Avante adapter version — older versions don't support MCP. Update.

Marketplace shows empty list

Network/firewall blocking marketplace URL. Check :MCPHub logs.

OAuth flow stuck in browser

Copy the URL from :MCPHub logs and paste manually; localhost redirect may not fire from Neovim context.

Alternatives

mcphub.nvim vs autres

Alternative	Quand l'utiliser	Compromis
CodeCompanion.nvim (native)	You want LLM chat without MCP management	No marketplace, no OAuth flows
VS Code MCP	You prefer VS Code	Not Neovim

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills