# @id3-clarity/mcp-server

Source: https://glimind.com/server/npm%2F-id3-clarity%2Fmcp-server
Registry id: `npm/-id3-clarity/mcp-server`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "id3-clarity-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@id3-clarity/mcp-server"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add id3-clarity-mcp-server -- npx -y @id3-clarity/mcp-server
```

## Tools (59)

- `add_release_exit_criterion`: Adds one derived or manual exit criterion
- `add_release_gate`: Adds an auto or manual quality gate
- `add_requirement_to_release`: Links a requirement to a release; related runs auto-inherited
- `add_test_run_to_release`: Directly attaches a test run with a runType classification
- `answer_release_exit_criterion`: Answers a manual criterion met/not_met
- `apply_release_exit_criteria_template`: Seeds exit criteria from the release type template
- `bulk_create_test_cases`: Bulk create test cases (max 50)
- `bulk_remove_requirements_from_release`: Bulk-unlink up to 500 requirements from a release
- `create_folder`: Creates a folder; use parentId for nested
- `create_project`: Creates a new project
- `create_release`: Creates a release; optional Jira fixVersion/sprint binding
- `create_requirement`: Creates a requirement; accepts legacy type/status or UUIDs
- `create_run`: Creates a test run; testSuiteId OR testCaseIds[] required
- `create_suite`: Creates a new test suite
- `create_test_case`: Creates a test case; non-MANUAL/AUTOMATED types auto-coerce
- `get_folder_tree`: Returns folder hierarchy as a tree
- `get_project`: Returns details of a specific project
- `get_project_stats`: Project statistics (case count, last 30 days success rate)
- `get_release`: Release detail — merged test runs
- `get_release_platform_readiness`: Readiness per platform (Web, iOS, Android, etc.)
- `get_release_readiness`: Readiness score, gates and blockers
- `get_requirement`: Returns full requirement detail incl. attachments and Jira sync
- `get_requirement_traceability`: Requirement → test case → last execution traceability matrix
- `get_run`: Returns run metadata only
- `get_run_progress`: Run progress statistics (pass/fail/skip/blocked/pending counts)
- `get_suite`: Returns suite detail with included cases
- `get_test_case`: Returns test case detail (steps + metadata + relations)
- `import_test_cases_json`: Bulk import via CLARITY JSON schema
- `link_requirement_to_jira`: Links a requirement to an existing Jira issue
- `link_requirement_to_test_case`: Links a requirement to up to 100 test cases per call
- `link_requirement_to_test_runs`: Links a requirement to up to 100 existing test runs
- `link_requirements`: Creates Jira issue links between requirements' issues
- `link_test_run_to_covered_requirements`: Links a run to every requirement its test cases executed
- `list_folders`: Lists folders in a project (flat)
- `list_projects`: Lists CLARITY projects accessible to your token
- `list_releases`: Lists releases with auto-computed metrics
- `list_requirement_link_types`: Jira issue link types with outward/inward phrases
- `list_requirement_statuses`: Lists requirement statuses (system defaults + project overrides)
- `list_requirement_types`: Lists requirement types (system defaults + project overrides)
- `list_requirements`: Lists requirements with type/status/priority/assignee filters
- `list_runs`: Lists test runs; supports status filter
- `list_suites`: Lists test suites
- `list_test_cases`: Lists test cases (paginated) with filters
- `push_requirement_to_jira`: Pushes a manually-created requirement to Jira as a new issue
- `push_requirement_update_to_jira`: Pushes CLARITY changes up to the linked Jira issue
- `remove_requirement_from_release`: Unlinks a requirement from a release (idempotent)
- `remove_test_run_from_release`: Detaches a directly attached test run
- `search_test_cases`: Full-text search by title in test cases
- `sync_requirement`: One-way pull-sync from Jira/Azure DevOps to local
- `unlink_requirement_from_test_case`: Removes a requirement ↔ test case link
- `unlink_requirement_from_test_runs`: Removes up to 100 requirement ↔ test run links
- `unlink_requirements`: Deletes one Jira issue link from a requirement's issue
- `update_execution_result`: Updates execution result for a case within a run
- `update_folder`: Updates folder name/parent
- `update_project`: Updates project info
- `update_release`: Partial update; status='released' auto-sets actualDate
- `update_requirement`: Updates requirement fields; linked items flip syncStatus
- `update_suite`: Updates a suite; addCaseIds/removeCaseIds for case management
- `update_test_case`: Updates test case fields

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
