nicobailon/pi-mcp-adapter v2.30.0

on GitHub

pi-mcp-adapter 2.30.0 makes MCP integrations easier to compose and less fragile in edge cases. Other Pi extensions can now inspect one runtime MCP server without getting access to the full MCP configuration. OAuth setup also works with providers that publish authorization metadata at a custom URL. This release also fixes provider-safe namespace names, installed token CLI loading, raw server-scoped tool calls, and Windows request-header cleanup.

Highlights

• Other extensions can safely inspect one runtime MCP server without seeing the whole MCP config.
• OAuth setup works better with providers that publish authorization metadata at a custom URL.
• MCP tool names are safer for providers, including servers with non-ASCII names.
• Token CLI commands and Windows request-header cleanup are less fragile in installed packages and long-running sessions.

Full changelog

Highlights

• Other extensions can safely inspect one runtime MCP server without seeing the whole MCP config.
• OAuth setup works better with providers that publish authorization metadata at a custom URL.
• MCP tool names are safer for providers, including servers with non-ASCII names.
• Token CLI commands and Windows request-header cleanup are less fragile in installed packages and long-running sessions.

Added

• Added a fail-closed API for child extensions to inspect one selected runtime MCP server without exporting configured servers or persisting the registration. (#453)
• Added oauth.authServerMetadataUrl for servers whose authorization-server metadata cannot be discovered through MCP protected-resource metadata. Thanks to @fmoda3 for #458.

Fixed

• Namespace proxy tool names now use provider-safe characters without making encoded-looking server names collide with non-ASCII server names. Thanks to @nyankosama for PR #463.
• npm-installed token CLI commands now load their credential, config, and utility helpers from the published JavaScript build instead of package-local TypeScript files. Thanks to @Qhilm for #456.
• Server-scoped MCP calls now resolve raw upstream tool names before normalized fallbacks without weakening ambiguity checks. Thanks to @MikeLP for #452.
• Windows request-header command cleanup now treats an already-exited process (taskkill exit code 128) as successful cleanup. Thanks to @peterxcx for #457.