IBM Engineering Lifecycle Management (ELM) MCP Server已验证已精选

MCP server for IBM ELM

Read and write requirements, test artifacts and work items in DOORS Next, ETM and EWM — through the Model Context Protocol, or through a REST API for your own scripts.

Ask instead of search

Your assistant answers questions about requirements, modules, test cases and work items straight from ELM — nobody writes an OSLC query. Where something is ambiguous the server names the candidates instead of picking one.

Changes that are verified

Every create and update is read back from ELM and compared with what was asked for, so you learn what was actually stored — not merely that the request was accepted. On configuration-managed components this happens inside a change set that you deliver yourself.

Big changes without fear

Whole documents are written in one call. If such a run breaks off, repeat it with the same request id: what already exists is skipped, nothing is duplicated, and nothing has to be rolled back.

• Requirements engineers who want their specification queried, not re-typed
• Test managers connecting requirements to test coverage
• Teams automating ELM work that today happens click by click in the web UI