Fix: tool names now fit the Kiro 64-character limit
The Kiro host rejected this server's tools with API Error: 400 Tool name(s) exceed Kiro API limit of 64 characters - 9 of 14 tools failed because the marketplace-plugin-composed name mcp__plugin_<pluginName>_<serverKey>__<namespace>_<tool> ran past 64 chars.
This release shortens the FastMCP mount namespaces and the plugin's mcpServers key, dropping the composed prefix from 39 to 32 chars. All 14 tools now clear the limit (worst case 61).
Tool name changes (action may be required)
If you script against tool names or have them pinned, the bare tool names have changed namespace prefixes:
| Old prefix | New prefix |
|---|---|
accounts_* |
acct_* |
transactions_* |
txn_* |
identity_* |
id_* |
For example accounts_list_accounts -> acct_list_accounts, transactions_get_transactions -> txn_get_transactions, identity_get_me -> id_get_me.
The marketplace plugin name stays nz-akahu-mcp, so existing installs keep working with no reinstall and no change to the severity1-marketplace repo. The PyPI package, uvx nz-akahu-mcp invocation, and all tool behavior are unchanged.
Also
- Added a regression guard asserting every composed plugin-path tool name fits the 64-char cap.
- Synced
uv.lockto the released version.
Full changelog: v0.1.3...v0.1.4