A
licenseNot graded
qualityD
maintenanceEnables AI assistants to interact with IBM ODM Decision Center for managing business rules, decision tables, ruleflows, and project generation.
MIT
OpenL MCP Server
OfficialRelated Servers
Alternatives to OpenL MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with IBM Engineering Lifecycle Management (ELM), including DOORS Next Generation, EWM, and ETM, for managing requirements, work items, tests, and project builds through natural language.MIT
- AlicenseBqualityBmaintenanceExposes over 300 Operaton BPM REST operations as tools for AI agents to interact with the Operaton engine. It enables managing process deployments, instances, user tasks, and decision tables through natural language commands.10012 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants to manage Rundeck operations including jobs, executions, projects, nodes, system management, key storage, webhooks, and ACL policies via natural language.5028 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceBridges IBM Operational Decision Manager with AI assistants, enabling decisions as tools for integration with platforms like Watson Orchestrate and Claude Desktop.8Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and execute automated decision services from IBM Decision Intelligence or IBM Automation Decision Services. It exposes deployed decision operations as tools for platforms like Claude Desktop and IBM watsonx Orchestrate.11 npm7Apache 2.0
TDQS
A3.6/5.0
Scored across 74 tools
Disambiguation3/5
Most tools target distinct resources, but the set contains several near-overlapping pairs (openl_append_table vs openl_append_table_rows, openl_list_branches vs openl_list_project_branches, openl_update_table vs the finer-grained update_table_row/column/cell/range tools) plus multiple test-result variants. The extensive descriptions and cross-references help, but the volume of similar verb/noun combinations still creates real selection risk.
Naming Consistency4/5
All tools consistently use the openl_ prefix and overwhelmingly follow a verb_noun snake_case pattern (list_, get_, create_, delete_, update_, append_, insert_, merge_). A few noun-first exceptions such as openl_project_status and openl_repository_project_revisions, plus close variants like append_table vs append_table_rows, are minor deviations.
Tool Count1/5
At 74 tools, this surface far exceeds the typical well-scoped MCP server, and the rubric explicitly flags 50+ tools as extreme. Even accounting for OpenL Studio's broad domain, many granular table-editing and debugging tools could be consolidated, and the sheer count will strain agent context and tool-selection accuracy.
Completeness4/5
Coverage is broad: project, file, table, test, trace/debug, branch/merge, and deployment workflows are all represented with substantial CRUD-like operations. Minor gaps remain—no undeploy/delete deployment, no project rename or repository management, and merge-conflict resolution is intentionally delegated to the user—but agents can generally work around them.
Maintenance
ActivityActive
ResponsivenessNo issues