Transports

ERPBridge uses MCP over two transports and provides direct HTTP endpoints for tooling.

1. Streamable HTTP

The MCP Streamable HTTP transport is best for remote clients, web apps, and Postman.

• Base URL: http://localhost:8080/mcp/
• Handshake: POST /mcp/ with a JSON-RPC initialize request
• Specification: MCP 2025-11-25, with negotiation of older supported protocol versions
• Session management: Mcp-Session-Id header
• CORS: enabled by default for browser and desktop clients

2. stdio

The client starts erpbridge-server as a child process and communicates over standard input/output. Best for local agents (Claude Desktop, Cursor, IDE integrations).

Start the stdio transport

erpbridge-server --stdio

3. Direct API

These internal endpoints support management, monitoring, and the bridgectl CLI. They do not require an MCP handshake. See the REST API reference.

Choose a transport

Client type	Transport	How to connect
Postman / web	Streamable HTTP	http://localhost:8080/mcp/
Claude / Cursor	stdio	erpbridge-server --stdio
Scripts / CI	Direct API	http://localhost:8080/api/

Choose a transport

Use Streamable HTTP when you need to inspect requests in a browser or Postman. Use stdio for local agent integrations.

For session management, Postman collections, and protection limits, see the Connectivity and transport guide.