nicobailon/pi-mcp-adapter v2.36.0

on GitHub

Pi can now configure TypeSafe semantic search directly with /mcp jev setup, including choosing which MCP servers may share tool metadata. Once a valid TypeSafe key is available, semantic search works across enabled MCP tools by default and gives clearer reasons when no tool matches. Windows users get reliable regex safety checks through both native and Java backends, and contributors can run npm test again on hardened Node versions. Large tool catalogs also show one clean interactive advisory instead of duplicated console warnings.

Highlights

• Set up TypeSafe semantic search from Pi with /mcp jev setup.
• Search every enabled MCP tool automatically when a TypeSafe key is available.
• Use regex safety checks reliably on Windows with both native and Java backends.
• Get clearer, non-duplicated guidance when tool catalogs are large or semantic search finds no match.

Full changelog

Highlights

• Set up TypeSafe semantic search from Pi with /mcp jev setup.
• Search every enabled MCP tool automatically when a TypeSafe key is available.
• Use regex safety checks reliably on Windows with both native and Java backends.
• Get clearer, non-duplicated guidance when tool catalogs are large or semantic search finds no match.

Added

• /mcp jev setup checks for a TypeSafe credential, lets you restrict which MCP servers may share semantic-search data, saves the project policy, and reloads Pi automatically.

Changed

• A valid TypeSafe key now enables semantic search across every enabled MCP tool by default, while script evaluation remains opt-in. Search now explains when an allowlist permits no servers, when permitted servers have no cached tools, and when none of the available tools match the request.

Fixed

• Regex safety checks on Windows resolve recheck's native executable and JAR fallback correctly. recheck is intentionally pinned to 4.6.0-beta.3 until a stable fixed release is available. Thanks to @LCubero for reporting #623, and @Kristinita and @makenowjust for the upstream reproduction and fix.
• Large direct-tool advisories now use Pi's renderer in interactive sessions, avoiding raw console output and duplicate warnings. Thanks to @grivper for issue #633.
• Windows contributors can run npm test again; the runner now launches npm through cross-spawn so hardened Node versions can execute npm.cmd. Thanks @insuffer for the fix.