MCP setup

MCP setup

The installer ships the MCP server together with the REST API.

The default MCP transport is stdio. Use the API URL and a dedicated API key for the connected product.

Important

REST success does not prove MCP readiness. MCP tools and payloads must match the same shipped version’s REST schemas and behavior.

Before relying on an integration, verify:

1. the MCP process starts;
2. the client can initialize the MCP session;
3. representative read tools return expected data;
4. representative write tools use the expected REST payload shape;
5. the integration uses a dedicated API key rather than the Admin key where practical.