ops-mcp

MCP server for the UluOps Platform API — 48 tools, 2 resources.

Overview

MCP client for the UluOps Platform API. Provides 48 tools and 2 resources for validation tracking, issue management, and analytics — zero business logic, pure protocol translation.

Installation

bash

npm install @uluops/ops-mcp

This installs the uluops-ops-mcp binary. To install it globally instead, use npm install -g @uluops/ops-mcp.

ℹ

Note

Naming note — this one server wears a different name at each layer. The npm package is @uluops/ops-mcp; it installs a binary named uluops-ops-mcp; the recommended .mcp.json server key is uluops-tracker (that key is what produces the mcp__uluops-tracker__* tool names in Claude Code); and in prose we call it the Tracker. All four refer to the same component. The separate @uluops/registry-mcp (uluops-registry) server is a different thing — see MCP Clients.

Configuration

Add to your Claude Code MCP configuration (.mcp.json):

json

{
  "mcpServers": {
    "uluops-tracker": {
      "command": "uluops-ops-mcp",
      "args": [],
      "env": {
        "ULUOPS_API_KEY": "ulr_your-api-key-here"
      }
    }
  }
}

The server connects to https://api.uluops.ai/api/v1/ops by default. Override with ULUOPS_BASE_URL only if you're running a local or custom API instance.

Variable	Description	Required
`ULUOPS_API_KEY`	API key — must start with `ulr_`, min 20 chars	Yes
`ULUOPS_BASE_URL`	Backend API URL	No (default: `https://api.uluops.ai/api/v1/ops`)
`ULUOPS_TRACKER_TIMEOUT`	Request timeout in ms	No (default: 30000)
`LOG_LEVEL`	Logging level	No (default: info)

Quick Start

typescript

// Save a validation run
save_run({
  project:       "my-project",
  workflow_type: "ship",
  agents: [{ name: "code-validator", score: 85, decision: "PASS" }],
  recommendations: [{
    agent: "code-validator",
    title:     "Fix lint error",
    priority:  "suggested",
    failure_code: "STR-MAL/M"
  }]
})

// Query open critical issues
query_issues({ project: "my-project", status: "open", priority: "critical" })

// Get project summary with issue counts and trends
get_project_summary({ project: "my-project" })

Tools Reference

Runs

Tool	Description
`save_run`	Save validation pipeline output with fingerprint-based issue correlation. Supports `analysis_summary`, `analysis_records`, and `exploration_maps` for structured agent output.
`update_run`	Update run metadata post-hoc — add tokens, scores, recommendations, or analysis data after initial save
`validate_run`	Preview what `save_run` would do without writing to the database
`get_run`	Get a run by UUID
`get_run_details`	Run info with all recommendations, correlation stats (new/recurring/regression). Omit `run_number` for latest
`get_run_analysis`	Get structured analysis records and summaries for a run — convention inventories, tension maps, system metrics
`get_latest_run`	Get the most recent run for a project, optionally filtered by workflow type
`list_runs`	List runs for a project with pagination
`diff_runs`	Compare two runs — fixed, new, unchanged issues, and agent score changes
`delete_run`	Delete a run (requires `confirm: true`)
`archive_runs`	Archive old runs without deletion — by run number, date, or keep-last count

Issues

Tool	Description
`query_issues`	Query issues by project, status, priority, agent, severity, failure domain/mode, persistence
`search_issues`	Full-text search across projects with relevance ranking and multi-filter support
`create_issue`	Create a user-submitted issue directly, outside of validation runs
`get_issue_details`	Full issue lifecycle with occurrences, notes, regression history, and optionally related issues
`get_issue_history`	Complete issue history — all occurrences, changes between runs, and notes
`get_issue_by_fingerprint`	Look up an issue by its SHA-256 fingerprint
`update_status`	Update issue status — identify by ID, fingerprint, or file_path+title
`update_issue_by_fingerprint`	Update issue status by fingerprint
`bulk_update_status`	Update multiple issue statuses in one transaction (max 100)
`undo_issue_status`	Undo the last status change on an issue
`edit_issue`	Edit issue metadata (title, file_path, category, severity, failure_code) without changing fingerprint
`add_issue_note`	Add context, resolution, or blocker notes to an issue
`merge_issues`	Merge duplicate issues into a target — migrates occurrences, marks sources as merged
`soft_delete_issue`	Soft-delete an active issue. Sets `deleted_at`; reversible via `restore_issue`
`restore_issue`	Restore a soft-deleted issue

Projects

Tool	Description
`list_projects`	List all active projects (excludes soft-deleted)
`get_project`	Get project by ID or name with metadata, run count, and issue stats
`create_project`	Create a new project for tracking
`update_project`	Rename a project
`get_project_summary`	Project overview with workflow stats, agent performance, and issue counts
`get_project_trends`	Issue trends over time for a project
`soft_delete_project`	Soft-delete a project (can be restored). Requires confirmation
`restore_project`	Restore a soft-deleted project with all associated data
`delete_project`	Permanently delete all project data. Two-step confirmation required

Analytics

Tool	Description
`get_analytics`	Cross-project analytics: agent_performance, resolution_rates, cross_project_patterns, file_hotspots, regression_analysis, trend_summary, cost_analysis, taxonomy_distribution
`get_agent_reliability`	Agent effectiveness — false positive rates, resolution rates, reliability scores
`get_agent_matrix`	Agent-taxonomy coverage matrix with blind spot detection and overlap analysis
`get_agent_lifecycle`	Version lifecycle trajectory for an agent — performance per definition version
`get_agent_runs_analysis`	Analysis summaries with run context for a specific agent across runs
`get_burndown`	Taxonomy burndown with time series and trend analysis per failure domain
`get_velocity`	Velocity metrics per failure mode with sparkline data and trend reliability
`get_discovery`	Discovery timeline — new vs recurring issues over time

Taxonomy

Tool	Description
`get_taxonomy`	Get the failure taxonomy schema (domains, modes, severities)
`get_full_taxonomy_analytics`	Distribution analytics by domain, severity, mode, and agent

Analysis Records

Tool	Description
`get_project_analysis`	Analysis summaries for a project — system metrics, category scores, epistemic assessments from cognitive lens runs
`query_analysis_records`	Query analysis records across all projects — find calcified conventions, degraded tensions, decay vectors, and other structured findings
`list_agents`	List canonical agents accepted by `save_run`

Resources

Resource URI	Description
`validation://projects`	List all tracked projects (JSON array)
`validation://taxonomy`	Failure taxonomy schema — domains, modes, severity codes

Resources vs Tools — For project-specific data, use the get_project_summary tool rather than resources. MCP resource templates with parameters are not fully supported by the current SDK.

Issue Statuses

Issues support seven resolution statuses:

Status	Meaning
`open`	Active, unresolved
`completed`	Genuine defect, fixed
`wontfix`	Correct observation, not worth acting on (lifecycle mismatch)
`false-positive`	Agent was factually wrong
`observation`	Valid observation, tracked separately from defects
`deferred`	Acknowledged, deferred to later
`merged`	Merged into another issue

Rate Limiting

Configured for Claude Code's burst-then-pause usage pattern:

Setting	Value
maxRequestsPerMinute	120
burstThreshold	15
burstWindowMs	5000
automationDetection	disabled

Operation	Typical Parallel Calls
Query context (summary, issues, runs)	3–5
Create issues from validation workflow	10–30
Update agents with metrics	6
Save recommendations	1 (array payload)

Why automation detection is disabled — Claude Code is trusted automation with consistent timing patterns. Enabling bot detection would misidentify legitimate agent use as suspicious traffic.