Repository navigation
Releases: feigeCode/navop-mcp
Release list
v0.3.2
What's changed
The Navop host sanitises its internal dotted tool ids into function-calling safe
names before advertising them on tools/list (sftp.upload becomes
sftp_upload). The CLI still matched names exactly, so every convenience
command and navop call failed with tool_not_found against any host released
after that change.
- Dotted ids are accepted again.
navop sftp upload,navop db query,
navop tool schema ssh.execandnavop tool call ssh.execall resolve to the
name the host actually advertises. Both spellings keep working, so older hosts
that still advertise dotted names are unaffected. - Calls use the advertised name. The CLI now sends the exact wire name, so
collision-suffixed entries such assftp_upload_2are addressed correctly. navop statusreports the runtime again.navop.runtime_statuswas
matched by exact name too, which leftruntime: nulland empty
toolGroups/disabledToolGroups- the disabled groups never showed up.
Non-existent tools now name their wire form indetails.requiredClientTool.
Upgrade with npm install -g @navop/[email protected].
v0.3.1
What's changed
Fixes MCP clients that were configured by a Navop build released before the
0.1.x argument removal.
- Legacy
mcppositional is accepted again. Those builds write
npx -y @navop/mcp@latest mcp --discovery <path>into client configs. Since
0.2.0 this package is the bridge and rejects that positional with
invalid_argumentsbefore any JSON-RPC handshake, so clients that only watch
"process started" showed the server as connected with an empty tool list. The
launcher now accepts and ignores a leadingmcp; any other unexpected
argument is still rejected with the usage error. - Regression test for the legacy argument in
test/cli.test.mjs. - Published as
@navop/[email protected],@navop/[email protected],@navop/[email protected].
Existing installations need no config edit: update the package and the old
configuration connects. The corrected argument list (-y,
@navop/mcp@latest, --discovery, <path>) is also what current Navop builds
should generate.
v0.3.0
What's changed
Support for the new configurable MCP approval window in Navop, and clearer
behaviour when a confirmation is not answered in time.
- Default request timeout raised to 60s (was 10s), split from the 10s
socket/connect deadline. A tool waiting on an approval dialog in Navop no
longer trips the client timeout and tears down the connection. - New
approval_timeouterror (exit code 10): the server's structured
approval_timeoutcode is passed through fromcallToolinstead of being
collapsed into a generictool_failed, with a message pointing at the
Navop approval settings. - Help text for
--timeoutnotes that it may need to be raised while a
tool waits on an approval dialog. - Published as
@navop/[email protected],@navop/[email protected],@navop/[email protected].
Requires the matching Navop desktop build with the configurable
approval_timeout_ms server setting.
Navop JavaScript packages v0.2.1
中文
更新内容
- 优化 Navop Agent Skill 的数据库操作指引:优先使用
navop db ...等领域命令,仅在没有对应领域命令时使用底层navop tool call。 - 补充写操作和布尔参数示例,明确
--allow-write true等参数必须携带显式值,减少自动化调用中的参数错误。 - 改进领域 CLI 的参数映射与帮助行为,并增加数据库写 SQL 到
db.exec的覆盖测试。
修复与调整
- 提升 Navop 桌面运行时启动或重启期间的连接稳定性:CLI 和 MCP bridge 会重新读取 discovery 信息,避免因短暂的旧端点或连接切换而直接失败。
- 增强 MCP 客户端和 stdio bridge 对分段读取、连续消息、连接关闭及启动竞态的处理与测试覆盖。
- 调整 npm 发布工作流,使部分包已经发布后的重试可以安全跳过现有精确版本并继续发布剩余包。
English
Changes
- Improves database guidance in the Navop Agent Skill: prefer domain commands such as
navop db ..., and use low-levelnavop tool callonly when no domain command exists. - Adds explicit examples for write operations and boolean arguments, clarifying that options such as
--allow-write truerequire a value and reducing invalid automated calls. - Improves domain CLI argument mapping and help behavior, with coverage for routing write-capable SQL to
db.exec.
Fixes
- Makes connections more resilient while the Navop desktop runtime is starting or restarting: the CLI and MCP bridge re-read discovery information instead of failing on a transient stale endpoint or connection transition.
- Strengthens MCP client and stdio bridge handling for partial reads, consecutive messages, connection closure, and startup races, with expanded test coverage.
- Makes the npm release workflow safely rerunnable by skipping package versions that already exist and continuing with the remaining packages.
Full Changelog: v0.2.0...v0.2.1
Navop JavaScript packages v0.2.0
中文
更新内容
- 发布新的三包基线架构:
@navop/client提供共享认证连接层,@navop/cli提供全局navop命令和 Agent Skill,@navop/mcp专注 MCP stdio 桥接。 - Navop Skill 要求通过
npm install -g @navop/cli@latest安装 CLI,并使用navop命令按需发现状态、命令帮助和实时 Schema。 - 增加 SSH、SFTP、Redis、MongoDB、SQL 数据库、连接/会话和可见终端的 Bash 工作流示例。
- Skill 避免在每轮模型上下文中携带完整 Navop MCP 工具目录,可减少重复工具定义与 Token 开销,同时保留 Navop 的 Tool Exposure、权限、审批、会话和审计边界。
修复与调整
- 移除旧组合包的 CLI/MCP 入口耦合以及
onetclidiscovery 兼容路径,以 Navop 作为当前基线。 - 更新 CI、打包和发布流程,按
@navop/client、@navop/cli、@navop/mcp的依赖顺序验证和发布。
English
Changes
- Introduces the new three-package baseline:
@navop/clientfor shared authenticated connectivity,@navop/clifor the globalnavopcommand and Agent Skill, and@navop/mcpfor the MCP stdio bridge. - Navop Skill now installs the CLI with
npm install -g @navop/cli@latestand usesnavopcommands to discover status, command help, and live schemas on demand. - Adds Bash workflows for SSH, SFTP, Redis, MongoDB, SQL databases, connections/sessions, and visible terminals.
- Keeps the complete Navop MCP tool catalog out of recurring model context when using the Skill workflow, reducing repeated tool-definition and Token overhead while retaining Navop Tool Exposure, permissions, approvals, sessions, and auditing.
Fixes
- Removes the former combined CLI/MCP package coupling and the legacy
onetclidiscovery path for the Navop baseline. - Updates CI, packaging, and release automation to verify and publish
@navop/client,@navop/cli, and@navop/mcpin dependency order.
Full Changelog: v0.1.2...v0.2.0
@navop/mcp v0.1.2
Full Changelog: v0.1.1...v0.1.2
v0.1.1
v0.1.0
Full Changelog: https://github.com/feigeCode/navop-mcp/commits/v0.1.0