HAPI MCP Server

HAPI MCP Server is an MCP integration. HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants.

Hosted connection

The registry lists a streamable-http connection at https://{HAPI_FQDN}:{HAPI_PORT}/mcp. Replace the account-specific fields according to the maintainer’s instructions.

Packages and local setup

The published oci package is docker.io/hapimcp/hapi-cli:0.6.0. Its declared MCP transport is streamable-http.

The package declares HAPI_FQDN: Fully Qualified Domain Name for the HAPI server (used in MCP tool URLs); HAPI_HOME: Directory path for HAPI configuration and specs. Should be mounted as a volume in Docker; PROJECT_NAME: The name of the project/API (alternative to positional argument); HAPI_OPENAPI: OpenAPI spec URL or path (alternative to --openapi flag); HAPI_URL: Backend API base URL (alternative to --url flag); HAPI_PORT: Server port (alternative to --port flag) - this is the internal container port; HAPI_HEADLESS: Enable headless mode (alternative to --headless flag); HAPI_MCP: Enable MCP mode (alternative to --mcp flag); HAPI_DEV: Enable development mode (alternative to --dev flag); HAPI_CORS: Comma-separated allowed CORS origins (alternative to --cors flag); HAPI_CONFIG_FILES: Comma-separated configuration files (alternative to --filename flag); NODE_ENV: Node environment (development, production). 'development' enables verbose logging and debugging features..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.6.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.