{"id":"lhwong-kie-server","name":"kie-server","homepage":"https://hub.docker.com/r/lhwong/kie-server","repo_url":"https://hub.docker.com/r/lhwong/kie-server","category":"automation","subcategories":[],"tags":["ai-ml","automation","infrastructure","devtools","api","rules-engine","bpm","workflow"],"what_it_does":"KIE Server (kie-server) is a Java-based server component for running and managing business rules/workflows (Business Process Management) built with Drools/jBPM/KIE. It typically exposes HTTP endpoints to deploy, execute, and query rule/workflow artifacts and their runtime state (e.g., sessions, process instances), and integrates with KIE containers and runtime services.","use_cases":["Deploy and execute Drools rules and BPMN processes from an application","Expose an HTTP API for business logic automation (rules/process orchestration)","Manage versions/containers of decision/process artifacts","Run workflow/process engines with external clients requesting executions and querying status"],"not_for":["Building a lightweight, single-purpose rules engine without server/runtime management needs","Simple offline/background computation without an HTTP service boundary","Use cases that require a fully managed cloud rules/workflows service with minimal ops (if you prefer SaaS)"],"best_when":"You need server-side execution of KIE (rules/BPMN) artifacts with remote invocation and lifecycle/version management, and you’re comfortable operating a Java server.","avoid_when":"You need a simple REST-only integration with minimal configuration and strong vendor-neutral SDKs; or you require fine-grained, agent-friendly operational semantics (pagination, idempotency, retries) that aren’t documented in the provided materials.","alternatives":["Camunda Platform (self-managed)","Drools standalone embedded execution","JBoss jBPM/Kogito (depending on your BPM/rules needs)","Temporal (workflow orchestration, different model)","AWS Step Functions + Lambda (managed orchestration)"],"af_score":35.2,"security_score":51.5,"reliability_score":31.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:30:59.951559+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Basic Auth (commonly supported in Java stacks)","Bearer token/JWT (potentially via container/security integration)","Container-managed authentication (e.g., application server security realms)"],"oauth":false,"scopes":false,"notes":"No specific authentication scheme, scope model, or documented auth contract was provided in the supplied information, so scores reflect typical server-side deployment patterns rather than confirmed details."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"As a self-hosted server component, cost is typically engineering/infra related; no pricing details were provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":35.2,"security_score":51.5,"reliability_score":31.2,"mcp_server_quality":0.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":0.0,"tls_enforcement":70.0,"auth_strength":55.0,"scope_granularity":35.0,"dependency_hygiene":45.0,"secret_handling":50.0,"security_notes":"Security depends heavily on how you deploy KIE Server (reverse proxy TLS, app-server TLS, auth configuration). Without confirmed documentation/implementation details, scores reflect typical Java server considerations: ensure HTTPS/TLS end-to-end, use strong authentication, and keep deployment/container dependencies patched.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":40.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Likely requires container-specific configuration (security, deployment, runtime) that agents can’t infer without full docs","Stateful runtime operations may be hard to make idempotent without explicit ids/retry keys","API semantics (job/process correlation ids, session lifecycle) can be non-obvious without examples","Potential for large payloads and long-running operations where polling/timeouts must be handled carefully"]}}