Installation
The full ERPBridge SDK facade requires Node.js >= 20 for built-in fetch
and AbortSignal. The package ships dual ESM + CJS builds with type
declarations for both. Each release has signed provenance; see
@erpbridge/sdk on npm.
Browser applications can use the ESM build for the MCP client and exact-name
tool proxy. Browser support does not include the REST surfaces. The ERPBridge
/mcp/ endpoint must allow the frontend origin and MCP protocol request
headers. It must also expose Mcp-Session-Id.
Install
- npm
- pnpm
npm install @erpbridge/sdk
pnpm add @erpbridge/sdk
Subpath imports
The package exposes four entry points:
| Subpath | Contents |
|---|---|
@erpbridge/sdk | Everything: the client facade, REST factories, and types |
@erpbridge/sdk/client | The createClient facade and ErpbridgeClient type |
@erpbridge/sdk/rest | The REST surface factories (createLogsApi, createRegistryApi, ...) |
@erpbridge/sdk/types | Shared types and the typed error hierarchy |
import { createClient } from '@erpbridge/sdk'
import { createLogsApi } from '@erpbridge/sdk/rest'
import { NotFoundError } from '@erpbridge/sdk/types'
Server requirements
The ERPBridge SDK connects to ERPBridge Server on its default port 8080.
See the server quickstart to start a server. The
server can run in open mode, so the ERPBridge SDK connects anonymously. In
authenticated mode, configure a token as described in
Authentication.