MCP.Market

Overseer Nvim MCP server

by impossiblecode·io.github.impossiblecode/overseer-nvim-mcp·v0.2.3

Gives coding agents the user's own view and control of overseer.nvim tasks in Neovim

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars87 downloads/wk

Reviews

Write one

Nobody has reviewed Overseer Nvim yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Overseer Nvim tools (7, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • overseer_dispose

    Stop (if running) and remove a task from the list by id or name substring. Disposing a finished task is unguarded; a running one the user started is refused unless `force` is set. A name matching more than one task is an error.

  • overseer_list_tasks

    List running and completed overseer.nvim tasks (id, name, status), newest first. `origin` is 'agent' for tasks this server started and 'user' for the ones they started themselves; only clean up your own.

  • overseer_list_templates
  • overseer_restart

    Restart a task by id or name substring (stops it first if running). A name matching more than one task is an error listing the candidates; pass a numeric id instead. Running tasks the user started are refused unless `force` is set.

  • overseer_runwrite action
  • overseer_stop

    Stop a running task by id or name substring. Overseer stops the underlying nvim job, so the task's process tree is torn down rather than left orphaned. A name matching more than one task is an error listing the candidates. Running tasks the user started are refused unless `force` is set, since a substring like 'dev' can match theirs.

  • overseer_tail

Public scan report

scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it

1 medium
  • Code scan2 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 85 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    dist/overseer-nvim-mcp.mjs: …s("Cloudflare")) return false; try { new Function(""); return true; } catch (_) { ret…
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Overseer Nvim compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
14%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
87
more than 60% of 12,191 servers with a package

What its tools let an agent do: 6 read · 1 change

Install Overseer Nvim in Claude Code, Cursor or VS Code

Runs npx -y overseer-nvim-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add overseer-nvim-mcp -- npx -y overseer-nvim-mcp
Add to Cursor

What the publisher says

From the Overseer Nvim repository's README, as published. We do not edit it. Read it on GitHub

overseer-nvim-mcp

An MCP server that gives a coding agent the same control over overseer.nvim tasks that you have: list, tail, run, restart, stop, and dispose.

Why

Your agent's shell tool and your overseer task list are separate execution worlds. A dev server the agent starts in its own shell is invisible in the task list, can't be stopped from it, and orphans its process tree when the session ends. Tasks you start get proper teardown. This closes that gap: the agent's long-running commands become real overseer tasks.

Requirements

(tested against v2.1.0)

  • Neovim with overseer.nvim
  • Node >= 22
  • An MCP client running inside a Neovim terminal buffer

Install

The server speaks stdio and is started by your MCP client. The command is always the same:

npx -y overseer-nvim-mcp

The client must run inside a Neovim terminal buffer; that is where the $NVIM socket it inherits comes from. Tools appear at the next session start, since MCP servers connect at startup. If the tools never appear, the usual cause is that $NVIM did not reach the server's environment: the server registers nothing without it, and some clients strip the environment they pass to servers.

Claude Code

claude mcp add overseer -- npx -y overseer-nvim-mcp

Codex CLI

codex mcp add overseer -- npx -y overseer-nvim-mcp

Then add one line to the generated block in ~/.codex/config.toml:

[mcp_servers.overseer]
command = "npx"
args = ["-y", "overseer-nvim-mcp"]
env_vars = ["NVIM"]

The env_vars line is required. Codex passes stdio servers a fixed whitelist of variables (HOME, PATH, TERM and the like), $NVIM is not on it, and without it the server registers no tools.

Codex also won't reach for the server on its own; see Getting your agent to actually use it.

Antigravity CLI

In ~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "overseer": {
      "command": "npx",
      "args": ["-y", "overseer-nvim-mcp"]
    }
  }
}

That user-global file is the one to use: the CLI's non-interactive print mode (agy -p) loads MCP servers from it and from nowhere else; a workspace-level .agents/mcp_config.json is silently ignored there.

Antigravity also won't reach for the server on its own; see Getting your agent to actually use it.

Gemini CLI

gemini mcp add overseer npx -y overseer-nvim-mcp

Or in settings.json:

{
  "mcpServers": {
    "overseer": {
      "command": "npx",
      "args": ["-y", "overseer-nvim-mcp"]
    }
  }
}

opencode

In opencode.json:

{
  "mcp": {
    "overseer": {
      "type": "local",
      "command": ["npx", "-y", "overseer-nvim-mcp"]
    }
  }
}

mcphub.nvim (codecompanion.nvim, avante.nvim)

In mcphub's servers config:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Overseer Nvim: common questions

Is Overseer Nvim MCP server safe?
Mostly: it is graded B (80/100). Read the Overseer Nvim safety report
How do I install Overseer Nvim?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Overseer Nvim need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Overseer Nvim maintained?
The last commit was 85 days ago (2026-08-11). The latest release is v0.2.3.
How does Overseer Nvim compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 14% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.