Roadmap
This page is the status index for the ERPBridge family. Use it to distinguish shipped capabilities, active work, and future ideas.
Status labels
- Shipped means the capability is available in the current documentation release.
- In flight means work is active but may change before release.
- Future means the direction is recorded, not a delivery commitment.
At a glance
Shipped coreERPBridge ServerMCP and REST middleware, registry, resilience, caching, observability, and security.View server roadmap →Shipped CLIbridgectlAPI, tool, cache, log, context, token, completion, and agent-skill workflows.View bridgectl roadmap →SDK v1.1.0 shippedERPBridge SDKTyped MCP client, exact-name tool proxy, REST wrappers, and operational APIs.View SDK roadmap →
Release lines
ERPBridge Server and bridgectl are released together. The SDK uses its own package version so client updates can ship independently.
| Product | Current release | Release source |
|---|---|---|
ERPBridge Server + bridgectl | v0.5.0-alpha.2 | ERPBridge releases |
@erpbridge/sdk | v1.1.0 | SDK releases · npm package |
Where to start
- Evaluating ERPBridge: run the server quickstart.
- Connecting an ERP: follow the onboarding guide.
- Automating operations: read the bridgectl skill usage guide.
- Embedding it in an application: use the SDK quickstart.
Influence the roadmap
- Report bugs and request features in GitHub Issues.
- Review release changes in the ERPBridge changelog.
- Use the project milestone list on GitHub to see planned sequencing.