{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-hap-mcp","slug":"hap-mcp","name":"HAP-MCP","type":"mcp","url":"https://github.com/mingdaocloud/hap-mcp.git","page_url":"https://unfragile.ai/hap-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-hap-mcp__cap_0","uri":"capability://tool.use.integration.zero.code.application.exposure.as.mcp.tools","name":"zero-code application exposure as mcp tools","description":"Automatically exposes HAP-built no-code applications as Model Context Protocol (MCP) tools that AI agents can discover and invoke. The MCP server acts as a bridge layer that introspects HAP application schemas (workflows, data models, API endpoints) and translates them into standardized MCP tool definitions with proper input/output schemas, enabling agents to treat low-code applications as native capabilities without custom integration code.","intents":["I want my no-code HAP application to become a tool that AI agents can automatically discover and use","I need to expose HAP workflows as callable functions to LLM-based agents without writing integration code","I want to enable agents to trigger HAP business processes as part of their reasoning chains"],"best_for":["Enterprise teams using HAP APaaS platform who want AI agent integration","No-code builders extending applications with AI capabilities","Organizations building multi-agent systems that need to orchestrate HAP workflows"],"limitations":["Requires HAP instance with exposed APIs or webhooks — cannot introspect closed/private applications","Schema translation latency depends on HAP application complexity; deeply nested workflows may produce large MCP tool definitions","Limited to HAP's native capability set — cannot expose custom JavaScript/Python extensions unless HAP exposes them via API","No built-in caching of schema definitions — each agent connection may re-introspect application structure"],"requires":["HAP platform instance (version not specified in repository)","HAP application with exposed API endpoints or webhook capabilities","MCP client implementation (Claude, Anthropic SDK, or compatible MCP consumer)","Network connectivity between MCP server and HAP instance"],"input_types":["HAP application schema (JSON/REST API responses)","Workflow definitions from HAP","Data model specifications"],"output_types":["MCP tool definitions (JSON schema format)","Callable tool interfaces for agents","Structured responses from HAP workflows"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_1","uri":"capability://tool.use.integration.hap.workflow.invocation.through.agent.function.calls","name":"hap workflow invocation through agent function calls","description":"Enables AI agents to trigger HAP workflows and business processes by calling them as functions through the MCP protocol. The MCP server translates agent function calls into HAP API requests, manages parameter mapping between agent outputs and HAP input schemas, handles asynchronous workflow execution, and returns results back to the agent's reasoning context. Supports both synchronous (blocking) and asynchronous (fire-and-forget) invocation patterns.","intents":["I want an AI agent to execute a HAP workflow as part of its task decomposition","I need to pass agent reasoning outputs as inputs to HAP business processes","I want agents to wait for HAP workflow completion and use results in downstream reasoning"],"best_for":["Developers building AI agents that orchestrate enterprise workflows","Teams automating multi-step business processes that span no-code and AI logic","Organizations using HAP for process automation who want AI-driven decision making"],"limitations":["Workflow execution timeout depends on HAP configuration — long-running workflows may exceed agent context windows","Parameter type coercion between agent outputs (typically strings/JSON) and HAP input types may fail silently if schemas don't align","No built-in retry logic for failed workflow invocations — agents must implement their own error handling","Asynchronous workflows return immediately without results — agents cannot directly use workflow outputs in synchronous chains"],"requires":["HAP instance with workflow API endpoints exposed","HAP API authentication credentials (API key or OAuth token)","MCP client with function-calling support","Network access from MCP server to HAP instance"],"input_types":["Agent function call parameters (JSON)","Structured data from agent reasoning","HAP workflow input schemas"],"output_types":["Workflow execution results (JSON)","Execution status/IDs for async workflows","Error messages and failure details"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_2","uri":"capability://search.retrieval.hap.data.model.querying.and.retrieval.via.agent.context","name":"hap data model querying and retrieval via agent context","description":"Allows AI agents to query and retrieve data from HAP data models (tables, collections) through MCP tool definitions, enabling agents to access enterprise data as part of their reasoning. The MCP server translates agent query intents into HAP API calls, handles filtering/sorting/pagination parameters, and returns structured data that agents can reason over. Supports both simple lookups and complex filtered queries.","intents":["I want an agent to look up customer records from HAP before making a decision","I need agents to query HAP data models with filters and return results for reasoning","I want agents to retrieve related data across multiple HAP tables to inform their actions"],"best_for":["Developers building AI agents that need access to enterprise data in HAP","Teams using HAP as a data layer for agent-driven applications","Organizations where agents need to make decisions based on current data state"],"limitations":["Query complexity limited by HAP API capabilities — complex joins or aggregations may not be supported","Large result sets may exceed agent context windows — pagination required but not automatic","No built-in caching of query results — repeated queries hit HAP API each time","Data freshness depends on HAP's eventual consistency model — agents may see stale data in distributed setups","Query performance depends on HAP database indexing — no query optimization at MCP layer"],"requires":["HAP instance with data model APIs exposed","HAP API authentication with read permissions on target data models","MCP client with tool-calling support","Network connectivity to HAP instance"],"input_types":["Query parameters (filters, sort, pagination)","Data model identifiers","Field selectors"],"output_types":["Structured data records (JSON)","Paginated result sets","Query metadata (total count, page info)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_3","uri":"capability://tool.use.integration.hap.api.endpoint.exposure.as.mcp.resources","name":"hap api endpoint exposure as mcp resources","description":"Exposes HAP's REST API endpoints as MCP resources that agents can discover and invoke. The MCP server introspects HAP's API documentation or OpenAPI schema, translates endpoints into MCP resource definitions with proper HTTP method mapping, parameter handling, and response parsing. Agents can then call these endpoints through the MCP protocol without needing to know the underlying REST API structure.","intents":["I want agents to call HAP REST APIs without hardcoding endpoint URLs","I need to expose HAP API capabilities as discoverable MCP resources","I want agents to invoke HAP endpoints with proper authentication and error handling"],"best_for":["Developers integrating HAP with AI agents that need flexible API access","Teams using HAP's REST API who want to expose it through MCP","Organizations building agent systems that need to call multiple HAP endpoints"],"limitations":["Requires HAP to expose OpenAPI/Swagger documentation — custom endpoints without documentation won't be auto-discovered","HTTP method semantics may not map cleanly to MCP tool semantics — PUT/PATCH/DELETE operations require careful handling","Authentication token management — MCP server must securely store and rotate HAP API credentials","Response size limits — large API responses may exceed MCP message size constraints","No built-in request/response transformation — agents must understand HAP's API response format"],"requires":["HAP instance with REST API endpoints","HAP API documentation (OpenAPI/Swagger) or manual endpoint configuration","HAP API authentication credentials","MCP client implementation"],"input_types":["HTTP request parameters (query, body, headers)","API endpoint specifications","Authentication tokens"],"output_types":["HTTP response bodies (JSON/XML)","Status codes and headers","Error messages"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_4","uri":"capability://tool.use.integration.agent.driven.hap.application.state.mutation.and.updates","name":"agent-driven hap application state mutation and updates","description":"Enables AI agents to create, update, and delete records in HAP data models through MCP function calls. The MCP server translates agent mutation intents into HAP API write operations, validates input data against HAP schemas, handles transaction semantics, and returns confirmation/results. Supports both single-record and batch operations with rollback capabilities.","intents":["I want an agent to create new records in HAP based on its reasoning","I need agents to update HAP records with new information they've gathered","I want agents to delete or archive HAP records as part of their workflow"],"best_for":["Developers building autonomous agents that modify enterprise data","Teams using agents to automate data entry and record management","Organizations where agents need write access to HAP for workflow automation"],"limitations":["Write permissions must be carefully scoped — MCP server requires HAP credentials with appropriate data model write access","No built-in audit logging at MCP layer — HAP's audit trail depends on platform configuration","Batch operations may fail partially — no automatic rollback if some records fail","Schema validation happens at HAP layer — agents may not get immediate feedback on invalid data","Concurrent writes from multiple agents may cause conflicts — no optimistic locking at MCP layer"],"requires":["HAP instance with write-enabled API endpoints","HAP API credentials with write permissions on target data models","MCP client with function-calling support","Network access to HAP instance"],"input_types":["Record data (JSON matching HAP schema)","Record IDs for updates/deletes","Batch operation payloads"],"output_types":["Created/updated record IDs","Confirmation messages","Error details for failed operations"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_5","uri":"capability://automation.workflow.mcp.server.lifecycle.management.and.hap.connection.pooling","name":"mcp server lifecycle management and hap connection pooling","description":"Manages the MCP server's connection to HAP instances, including authentication, connection pooling, credential rotation, and graceful shutdown. The server maintains persistent connections to HAP APIs, reuses connections across multiple agent requests, handles authentication token refresh, and implements health checks to detect connection failures. Supports multiple HAP instance configurations for multi-tenant scenarios.","intents":["I want the MCP server to maintain efficient connections to HAP without recreating them per request","I need automatic credential rotation and token refresh for long-running agent sessions","I want the MCP server to detect and recover from HAP connection failures"],"best_for":["DevOps teams deploying HAP-MCP in production environments","Organizations running long-lived agent services that need stable HAP connections","Teams managing multiple HAP instances with different credentials"],"limitations":["Connection pool size must be tuned for expected agent concurrency — too small causes bottlenecks, too large wastes resources","Credential rotation requires coordination with HAP's authentication system — timing mismatches may cause temporary failures","Health checks add latency — frequent checks impact performance, infrequent checks delay failure detection","No built-in load balancing across multiple HAP instances — requires external orchestration","Connection state is not persisted — server restart loses in-flight requests"],"requires":["HAP instance with stable API endpoints","HAP API credentials (API key or OAuth)","Node.js runtime (version not specified)","Network connectivity to HAP"],"input_types":["HAP connection configuration (host, port, auth)","Pool size and timeout parameters"],"output_types":["Connection status and health metrics","Error logs and diagnostics"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_6","uri":"capability://automation.workflow.agent.error.handling.and.hap.failure.recovery","name":"agent error handling and hap failure recovery","description":"Implements error handling and recovery strategies for agent interactions with HAP, including retry logic for transient failures, circuit breakers for cascading failures, timeout management, and structured error reporting. The MCP server catches HAP API errors, classifies them (transient vs permanent), applies appropriate recovery strategies, and returns actionable error information to agents for decision-making.","intents":["I want agents to automatically retry failed HAP operations without manual intervention","I need the MCP server to detect when HAP is unavailable and fail gracefully","I want agents to receive clear error messages so they can adjust their reasoning"],"best_for":["Teams running agents in production where HAP availability may be variable","Organizations building resilient agent systems that handle transient failures","DevOps teams managing SLAs for agent-driven workflows"],"limitations":["Retry logic may mask underlying HAP issues — agents may succeed after retries but with stale data","Circuit breaker thresholds must be tuned per deployment — no one-size-fits-all configuration","Timeout values depend on HAP performance characteristics — too aggressive causes false failures, too lenient impacts agent latency","Error classification heuristics may misidentify error types — permanent errors may be retried, transient errors may fail immediately","No built-in alerting — operators must monitor logs to detect persistent HAP issues"],"requires":["HAP instance with observable error responses","MCP client that supports error handling","Monitoring/logging infrastructure for diagnostics"],"input_types":["HAP API error responses","Timeout and retry configuration"],"output_types":["Structured error objects for agents","Retry attempt logs","Circuit breaker status"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_7","uri":"capability://automation.workflow.multi.agent.concurrent.request.handling.and.rate.limiting","name":"multi-agent concurrent request handling and rate limiting","description":"Manages concurrent requests from multiple AI agents to HAP through the MCP server, implementing request queuing, rate limiting, and fair scheduling. The server enforces HAP API rate limits, prevents agent requests from overwhelming the platform, implements backpressure mechanisms, and ensures fair resource allocation across agents. Supports both per-agent and global rate limit configurations.","intents":["I want multiple agents to safely query HAP without exceeding rate limits","I need fair resource allocation when multiple agents request HAP simultaneously","I want the MCP server to queue requests and prevent HAP overload"],"best_for":["Organizations running multiple AI agents that access the same HAP instance","Teams deploying agent systems at scale where HAP API limits are a constraint","DevOps teams managing shared HAP infrastructure across multiple agent workloads"],"limitations":["Rate limit enforcement adds latency — agents may experience queuing delays","Fair scheduling algorithms may not match business priorities — high-priority agents may be delayed by low-priority ones","Rate limit configuration must match HAP's actual limits — misconfiguration causes either underutilization or overload","No built-in priority queuing — all agents treated equally regardless of importance","Distributed deployments require shared rate limit state — adds complexity and potential consistency issues"],"requires":["HAP API rate limit specifications","MCP client that supports concurrent requests","Request queuing infrastructure"],"input_types":["Agent requests (any MCP tool call)","Rate limit configuration"],"output_types":["Queued request status","Rate limit exceeded errors","Request execution results"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-hap-mcp__cap_8","uri":"capability://tool.use.integration.hap.workflow.schema.introspection.and.mcp.tool.generation","name":"hap workflow schema introspection and mcp tool generation","description":"Automatically introspects HAP workflow definitions and generates corresponding MCP tool schemas that agents can discover and invoke. The MCP server queries HAP's workflow metadata, extracts input/output specifications, generates JSON schemas for MCP tool definitions, and keeps them synchronized with HAP changes. Supports dynamic tool discovery so agents can access newly created workflows without server restart.","intents":["I want agents to automatically discover all available HAP workflows as MCP tools","I need MCP tool schemas to stay in sync when HAP workflows are modified","I want agents to invoke HAP workflows with proper input validation based on workflow schemas"],"best_for":["Organizations with frequently changing HAP workflows who want agents to adapt automatically","Teams building agent systems where workflow discovery must be dynamic","DevOps teams managing HAP platforms where workflow changes shouldn't require MCP server updates"],"limitations":["Schema introspection latency depends on HAP's metadata API performance — large numbers of workflows may cause delays","Dynamic tool generation may not support all HAP workflow features — complex conditional logic may not translate to MCP schemas","Schema caching required for performance — stale schemas possible if HAP workflows change frequently","Tool naming and descriptions depend on HAP metadata quality — poorly documented workflows produce unclear MCP tools","No versioning of workflow schemas — agents may break if workflows change incompatibly"],"requires":["HAP instance with workflow metadata APIs exposed","HAP API credentials with read access to workflow definitions","MCP client that supports dynamic tool discovery"],"input_types":["HAP workflow metadata","Workflow input/output specifications"],"output_types":["MCP tool definitions (JSON schema)","Tool discovery responses","Schema update notifications"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":33,"verified":false,"data_access_risk":"high","permissions":["HAP platform instance (version not specified in repository)","HAP application with exposed API endpoints or webhook capabilities","MCP client implementation (Claude, Anthropic SDK, or compatible MCP consumer)","Network connectivity between MCP server and HAP instance","HAP instance with workflow API endpoints exposed","HAP API authentication credentials (API key or OAuth token)","MCP client with function-calling support","Network access from MCP server to HAP instance","HAP instance with data model APIs exposed","HAP API authentication with read permissions on target data models"],"failure_modes":["Requires HAP instance with exposed APIs or webhooks — cannot introspect closed/private applications","Schema translation latency depends on HAP application complexity; deeply nested workflows may produce large MCP tool definitions","Limited to HAP's native capability set — cannot expose custom JavaScript/Python extensions unless HAP exposes them via API","No built-in caching of schema definitions — each agent connection may re-introspect application structure","Workflow execution timeout depends on HAP configuration — long-running workflows may exceed agent context windows","Parameter type coercion between agent outputs (typically strings/JSON) and HAP input types may fail silently if schemas don't align","No built-in retry logic for failed workflow invocations — agents must implement their own error handling","Asynchronous workflows return immediately without results — agents cannot directly use workflow outputs in synchronous chains","Query complexity limited by HAP API capabilities — complex joins or aggregations may not be supported","Large result sets may exceed agent context windows — pagination required but not automatic","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.53,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.041Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=hap-mcp","compare_url":"https://unfragile.ai/compare?artifact=hap-mcp"}},"signature":"aBJnwEgZLVks0b+of600ALzw6R3fwyH07hA/xVeM+DTWzJqfU37XLli0byd2nJkJ4LCEl3YCaUddxghZZ3qoBg==","signedAt":"2026-06-21T14:21:02.043Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/hap-mcp","artifact":"https://unfragile.ai/hap-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=hap-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}