elm-alm-py 0.3.0

MCP server for IBM Engineering Lifecycle Management (ELM) via OSLC REST API

elm-alm-py

MCP server for IBM Engineering Lifecycle Management (ELM) — read and write access to DOORS Next (RM), RTC/EWM (CCM), and ETM (QM) via OSLC REST APIs.

Tested against ELM 7.0.3 (alm.dataprev.gov.br).

Install

uv pip install -e .

Configuration

Option 1: Credentials file (recommended)

elm-alm-py login

Saves to ~/.elm_creds.json:

{"url": "https://your-elm-server.example.com", "username": "user", "password": "base64encoded"}

Option 2: Environment variables

export ELM_URL=https://your-elm-server.example.com
export ELM_USER=your_username
export ELM_PASSWORD=secret

Usage

# As MCP server (stdio)
elm-alm-py

MCP client configuration

{
  "mcpServers": {
    "elm-alm": {
      "command": "/path/to/.venv/bin/elm-alm-py"
    }
  }
}

Tools

Read Operations

Tool	Description
list_projects(domain)	List projects for RM/CCM/QM
search_requirements(project, query?)	OSLC query on RM requirements
get_requirement(uri)	Get single requirement by URI
list_workitems(project, query?)	OSLC query on CCM work items
get_workitem(id)	Get single work item by ID
search_testcases(project, query?)	OSLC query on QM test cases

Write Operations

Tool	Description
create_workitem(project, title, type?, ...)	Create a work item (task/story/defect)
update_workitem(id, title?, description?)	Update work item fields (ETag-based)
add_child_workitem(parent_id, title, ...)	Create a child work item

create_workitem parameters

Parameter	Required	Description
project	✅	Project name (e.g., "MEU IMOVEL RURAL (MIR)")
title	✅	Work item title
type		"task" (default), "story", or "defect"
description		HTML description
parent_id		Parent work item ID (creates child link)
owner		Username (e.g., "claudio.filho")
filed_against		Category URI. Auto-discovered if not provided
custom_fields		Dict of extra RDF fields (see below)

custom_fields for project-specific attributes

Some RTC projects require custom fields. Pass them as a dict:

custom_fields={
    "rtc_ext:com.dataprev.team.workitem.attribute.categoriatarefa": {
        "rdf:resource": "https://server/ccm/oslc/enumerations/{projectAreaId}/..."
    }
}

Values can be:

• {"rdf:resource": "uri"} — for URI/enumeration fields
• "text" — for literal text fields

OSLC API Details

Work Item Types (CCM)

Type	RTC type ID	calm:id in services.xml
task	task	requirementChangeRequest
story	com.ibm.team.apt.workItemType.story	planItem
defect	defect	defect

Key Fields

Field	Namespace	Format
Title	dcterms:title	Text
Type	rtc_cm:type	rdf:resource URI
Category	rtc_cm:filedAgainst	rdf:resource (itemOid format)
Iteration	rtc_cm:plannedFor	rdf:resource URI
Owner	dcterms:contributor	rdf:resource /jts/users/{login}
Estimate	rtc_cm:estimate	Integer (milliseconds)
State	rtc_cm:state	rdf:resource URI

Content Types

• Create (POST): application/rdf+xml
• Read (GET): application/json (Accept header)
• Update (PUT): application/json with If-Match: {ETag}

Development

uv sync --group dev
uv run pytest tests/ -v --cov=elm_alm_py
uv run ruff check src/ tests/

Known Limitations

• _find_default_category returns first category from list (may not be correct for your project). Use filed_against parameter explicitly.
• update_workitem supports title, description, owner, estimate_hours, planned_for, and custom_fields.
• OSLC CM 1.0 services.xml parsing is bypassed — creation URL is constructed directly.

License

MIT