Upgrade guide

The ERPBridge v0.3.0-alpha.1 compatibility contract shipped in the breaking @erpbridge/sdk v1.0.0 release.

MCP results are no longer flattened

client.mcp.callTool() and client.tools.<name>() now return McpToolResult, the official MCP CallToolResult envelope. The ERPBridge SDK does not parse text as JSON or move content blocks into a REST-shaped result field.

Before:

const result = await client.tools.list_employees({})
console.log(result.result)

After:

const result = await client.tools.list_employees({})
console.log(result.content)
console.log(result.structuredContent)

client.invoke() and client.registry.invoke() remain REST operations. They continue to return ToolResult with a result field.

Credentials are now active

The existing token and tokenEnv configuration fields now send bearer credentials when set. If your application passed these fields before, update it for this behavior. See Authentication for precedence, surface overrides, and the consume-only token lifecycle.

The default credential environment variable is now ERPBRIDGE_TOKEN. ERPBridge_TOKEN remains a compatibility fallback when the canonical variable is absent. Migrate deployments to the all-caps name.