HAPI MCP Server
HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants
Streamable HTTP / SSE endpoint. Add to any MCP client that supports remote servers.
https://{HAPI_FQDN}:{HAPI_PORT}/mcp{
"mcpServers": {
"hapi-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/hapimcp/hapi-cli:0.6.0"
],
"env": {
"HAPI_FQDN": "localhost",
"HAPI_HOME": "/app/.hapi",
"PROJECT_NAME": "<project_name>",
"HAPI_OPENAPI": "<hapi_openapi>",
"HAPI_URL": "<hapi_url>",
"HAPI_PORT": "3030",
"HAPI_HEADLESS": "true",
"HAPI_MCP": "true",
"HAPI_DEV": "<hapi_dev>",
"HAPI_CORS": "<hapi_cors>",
"HAPI_CONFIG_FILES": "<hapi_config_files>",
"NODE_ENV": "production"
}
}
}
}HAPI_FQDNFully Qualified Domain Name for the HAPI server (used in MCP tool URLs)
HAPI_HOMEDirectory path for HAPI configuration and specs. Should be mounted as a volume in Docker
PROJECT_NAMEThe name of the project/API (alternative to positional argument)
HAPI_OPENAPIOpenAPI spec URL or path (alternative to --openapi flag)
HAPI_URLBackend API base URL (alternative to --url flag)
HAPI_PORTServer port (alternative to --port flag) - this is the internal container port
HAPI_HEADLESSEnable headless mode (alternative to --headless flag)
HAPI_MCPEnable MCP mode (alternative to --mcp flag)
HAPI_DEVEnable development mode (alternative to --dev flag)
HAPI_CORSComma-separated allowed CORS origins (alternative to --cors flag)
HAPI_CONFIG_FILESComma-separated configuration files (alternative to --filename flag)
NODE_ENVNode environment (development, production). 'development' enables verbose logging and debugging features.
AI-powered trading strategy development: backtesting, market data, and portfolio analysis
Feature flagging and A/B testing platform with AI-first experimentation workflows.
Query Meta Ads performance data — accounts, campaigns, ad sets, ads, metrics & settings.