Protocol Extensions

The protocols array registers capabilities that share the server transport but are not application service routes. Connectum ships operational protocols for health and reflection; advanced consumers can implement the same registration contract for a custom gRPC service or HTTP fallback handler.

const server = createServer({
  services: [routes],
  protocols: [
    Healthcheck({ httpEnabled: true }),
    Reflection(),
  ],
});

Operational protocols

• Health checks own readiness/liveness state and platform probes.
• Server reflection owns schema discovery, tool usage, and the production exposure warning.

Advanced extension point

Creating a custom protocol owns ProtocolRegistration, ProtocolContext, HTTP handler behavior, registration timing, and examples. Add protocols before server.start() and before materializing an in-process transport; this is an explicit server extension boundary, not general request middleware.

Exact core types remain in ProtocolRegistration and the generated core API. Package setup belongs to the @connectum/healthcheck and @connectum/reflection module hubs.