MCP server for IBM Engineering Lifecycle Management (ELM) via OSLC REST API
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"elm-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<h1 align="center">elm-mcp</h1> <p align="center"><strong>Bring IBM Engineering Lifecycle Management to your AI agent.</strong><br> An MCP server that reads and writes requirements, work items and test cases in IBM ELM over the open OSLC REST protocol — so an agent can work the ALM as a first-class tool.</p> <p align="center"> <a href="https://pypi.org/project/elm-mcp/"><img src="https://img.shields.io/pypi/v/elm-mcp" alt="PyPI"></a> <img src="https://img.shields.io/badge/python-3.10%2B-blue" alt="Python 3.10+"> <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a> <a href="https://github.com/filhocf/elm-mcp/actions/workflows/ci.yml"><img src="https://github.com/filhocf/elm-mcp/actions/workflows/ci.yml/badge.svg" alt="CI"></a> </p> --- **elm-mcp** exposes IBM ELM's three OSLC domains — **DOORS Next (RM)**, **EWM/RTC (CCM)** and **ETM (QM)** — as MCP tools. An AI assistant (Kiro, Claude, OpenCode, Hermes, …) can then list projects, query and create requirements, work items and test cases, and move them through their workflow, without a human clicking through the Jazz web UI. It is an **independent implementation** over the open [OSLC](https://open-services.net/) REST protocol — **not a fork** of IBM software, and it does **not** bundle any IBM client library. The package is **vendor-neutral**: no organization-specific host, project or namespace is baked in; those come from your own configuration at runtime. ## Why ALM tools like IBM ELM hold the official record — requirements, backlog, tests, traceability — but they live behind a web UI and OSLC APIs that an agent cannot use out of the box. elm-mcp is the bridge: it lets an agentic workflow read context from the ALM and write artifacts back to it, over the Model Context Protocol, so the agent and the traditional process share one source of truth. ## Install Run it with [`uv`](https://docs.astral.sh/uv/) — no clone, no manual virtualenv: ```bash uvx e…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.