HAPI MCP Server

HAPI MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://{HAPI_FQDN}:{HAPI_PORT}/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The URL contains placeholders to fill in before connecting: {HAPI_FQDN} and {HAPI_PORT}.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/hapimcp/hapi-cli:0.6.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: HAPI_FQDN, HAPI_HOME, PROJECT_NAME, HAPI_OPENAPI, HAPI_URL, HAPI_PORT, HAPI_HEADLESS, HAPI_MCP, HAPI_DEV, HAPI_CORS, HAPI_CONFIG_FILES and NODE_ENV; set them in the client's configuration for this server. Required arguments: -p and serve.

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect