More reliable MCP tool setup and sessions

Saber MCP now starts tool sessions reliably when API operations contain schema constraints that the MCP converter cannot represent directly.

What changed

• Unsupported OpenAPI not constraints no longer prevent an MCP server from registering its tools.
• The upstream Saber API still validates the complete request contract when a tool is called.
• Stateful MCP sessions now use bounded memory, reducing the risk of long-lived sessions consuming excessive resources.

The update applies automatically to hosted Saber MCP sessions. No client change is required.

Learn more

• Saber MCP
• MCP basic usage
• Signals API reference