Upgrading

Versions before 0.1.3 had a bug where the bundled MCP server bin would exit silently when launched via the npm bin symlink, which is exactly how every MCP client invokes it. If you see no talonic_* tools despite correct config, you are hitting that bug.

The fix: point your args at @latest (or @0.1.3 explicitly) and fully restart the client:

"args": ["-y", "@talonic/mcp@latest"]

Using @latest is the recommended approach because it ensures you automatically receive new features, bug fixes, and improved tool descriptions on every client restart. If you need version stability for a production workflow, pin to a specific version like @0.1.6 instead.

After updating the args in your MCP client config, you must fully restart the client application. Simply starting a new conversation is not enough — the MCP server process must be terminated and re-spawned. On Claude Desktop, use Cmd+Q (macOS) or close from the system tray (Windows). On Cursor and VS Code-based clients, reload the window.

Verify the upgrade

// In a terminal, verify the latest version installs:
// npx -y @talonic/mcp@latest --version
// Expected output: 0.1.6 (or the latest published version)

// In your MCP client, verify tools are available:
// Ask the agent: "What version of Talonic MCP are you using?"
// Or call talonic_list_schemas — a successful response
// confirms the server is running the updated version.

When upgrading between minor versions, tool parameters and response shapes remain backward-compatible. New versions may add optional parameters to existing tools or introduce new tools, but they will not remove or change existing parameters. This means your existing agent workflows and saved schemas continue to work without modification after an upgrade.

If you are running a pinned version and want to check whether a newer version is available, run npm view @talonic/mcp version in a terminal. This shows the latest published version on npm without installing it. Compare this against your pinned version to decide whether to upgrade. The changelog in the npm package description summarises what changed between versions.

For teams with multiple developers using the Talonic MCP server, coordinate upgrades by updating the shared MCP config file or template. If different team members run different versions, tool descriptions and capabilities may vary, leading to inconsistent agent behaviour. Using @latest for all team members ensures everyone has the same tools and avoids version-related debugging sessions.