MCP: client setup

Documentation area · service not connected

No Hostbip MCP endpoint, callable tool catalogue or verified client configuration is connected in this source release.

Publish tested recipes, not assumed compatibility.

No MCP client integration has been tested against a Hostbip MCP server in this release.

What a published recipe must identify

Every future recipe must state the exact client version, supported transport, backend release, public service address, authentication flow and tested capabilities. A downloadable configuration must contain no customer tokens or secrets.

Transport and endpoint boundaries

A hosted integration should use the verified remote service address supplied by the backend. The developer portal displays instructions; it does not proxy arbitrary MCP destinations. Public service addresses use HTTPS hostnames. Internal Hostbip services use their registered Docker hostnames, never localhost or fixed-address shortcuts.

Troubleshooting a setup

Capture the time, public release identifier and a sanitized error code. Keep tokens and customer data out of diagnostics. Client-specific instructions will be published only after the relevant integration is tested.

Guides are editorial. Backend permissions and technical contracts remain authoritative.

Integration support ↗