Developer changelog

Changes that affect code you write against OrgRelay: the connector spec, the developer kit, the self-test tool and the tools OrgRelay exposes as an MCP server. Product releases for business users are listed in the orgrelay.com changelog.

Compatibility rules are on the connector spec page: within orgrelay-connector/1 only backward-compatible changes are made, and a future version 2 will run alongside version 1 for at least 12 months.

#2026-11-12 · Developer kit update

• Every template now also ships with English comments and error messages under templates/en/. See code templates.
• The Java template gained a signed pushEvent() helper, so all four templates show event push. The Node.js, Python and Java helpers sign each retry afresh.
• The kit includes its MIT LICENSE file.
• With OrgRelay 1.4.0 or later, tools named logistics.*, purchase.* and ads.* are routed to the operations and procurement agents, as listed on standard tools.

#2026-11-09 · Developer kit 1.1.0, spec document 1.1.0

First release of the developer kit, shipped together with OrgRelay 1.1.0. The spec is orgrelay-connector/1; the document describing it is version 1.1.0. The kit is downloadable from code templates, and the four spec files are published individually under /spec/. It contains:

• Event push. Connectors can push signed events (X-OrgRelay-Signature, HMAC-SHA256, five-minute replay window) with a fixed retry schedule and de-duplication by id. See events.
• Sandbox connections. Owners can bind a connector in developer mode, call any tool by hand and watch the call log before promoting it. See the quickstart.
• Standard tool names for 14 domains, with input and output schemas in standard-tools.json. See standard tools.
• Logo field in the manifest: https:// or a data URI, 200 KB maximum, cached by OrgRelay at bind time.
• Self-test tool orgrelay-connector-check 1.1.0, checking tenant isolation (--token-b), idempotency (--write), information-leak checks, OAuth 2.1 client credentials, --json reports and the sign-event helper. See self-test tool.
• Templates in Node.js, Python, PHP and Java, each serving MCP and REST compatible mode from one process.

#MCP server tools

OrgRelay's own MCP server, used from Claude Code and Codex, exposes document search, table queries, alerts, tasks, approvals and skills. Changes to that tool list are recorded here when they happen. The current list is on the MCP overview.

#Where each change is documented

• Connector authors: quickstart, MCP transport, authentication, approvals and write tools and security requirements.
• Integrators connecting existing platforms: OpenAPI import, GraphQL import and third-party MCP.
• Staff using AI clients: Claude Code and enterprise MCP patterns.

#Deprecations

None.