Hardcoding mcp__neovim__vim_* in the agent/skill prose was wrong on
two counts: (1) the prefix was flat-out incorrect — a plugin-shipped
.mcp.json server is namespaced mcp__plugin_<plugin>_<key>__, not
mcp__<key>__; (2) hardcoding any fully-qualified MCP tool name in
prose is fragile — it depends on registration method and topology
(metamcp aggregation injected/removed a segment).
- frontmatter tools:/allowed-tools: use the correct prefix wildcard
mcp__plugin_nvim-agentic-companion_neovim__* (the allowlist needs a
real pattern; one place; stable with plugin name + .mcp.json key)
- all prose now names tools by leaf (vim_command, vim_health, …) and
tells the agent to match those against its actual runtime toolset
rather than assume a prefix
oleks
9a9d477d5c