Server roadmap
ERPBridge Server is the runtime boundary between ERP APIs and MCP clients. This page tracks shipped capabilities and active development.
Shipped through v0.5.0-alpha.2​
| Area | Current capability | Technical reference |
|---|---|---|
| MCP middleware | Streamable HTTP and stdio transports, tool discovery, calls, and notifications over MCP 2025-11-25 with older-version negotiation. | Transports · MCP client guide |
| Tool registry | ERP registration, schema generation and validation, soft/hard delete, versioned tools, and 10-second reconciliation. | architecture · tool schema |
| Resilience | 15-second HTTP timeout, circuit breaker, and retry with jitter for network errors and 429/5xx responses. | connectivity |
| Caching | Optional exact-match cache with Redis or bounded in-memory storage, flush and stats endpoints, and per-tool flushOn invalidation. | caching |
| Observability | Structured logs, JSON output in production, Prometheus metrics, health checks, and per-component log levels. | REST API · environment variables |
| Security | Credential references resolved from environment variables, secret redaction in logs, scoped API tokens, and role-protected routes. | authentication · API tokens |
In flight​
Security and correctness hardening​
Work continues on protocol boundaries, credential handling, log redaction, and state hashing. These changes are intended to improve correctness and safety without changing the documented integration workflow.
Future direction​
- MCP specification upgrade: migrate to MCP 2026-07-28 with mcp-go v1.0.0-beta.1.
- Prebuilt connectors: provide connectors for commonly used ERP systems.
- Schema distribution: support a central registry or Git-based schema synchronization.