◉index.md
traceops.dev

// api-first work item coordination

Track what your agents find.

TraceOps.Dev gives repo audits, implementation plans, and coding agents a durable place to store findings, claims, statuses, and external PR or commit metadata.

IssueFeatureAudit findingWorkflow state
Sign inRead docsContact
traceops.workflowv0.1

// work item

ClaimedrepoId, severity, status, source, files, tags

// surface

API + MCPOne workflow, two integration paths
create_workitem

Agent-readable workflow state, stored outside the prompt.

get_next_workitem

Agent-readable workflow state, stored outside the prompt.

update_workitem_status

Agent-readable workflow state, stored outside the prompt.

// product

Reusable coordination patterns, not disposable chat state.

01

Track what your agents find

Capture audit findings, implementation tasks, and repository issues as durable work items instead of losing them in chat transcripts.

02

API-first

Use a small authenticated HTTP API to create, search, claim, update, and link work items from automation.

03

MCP-ready

Expose the same workflow through an MCP stdio server so coding agents can coordinate progress without inventing state.

04

Built for repo audits and implementation plans

Keep severity, status, source, files, tags, claims, and external branch or PR metadata close to the repository work.

05

Hosted option is coming

A hosted TraceOps.Dev option is planned for teams that want managed operations without running their own deployment.

06

Open-source friendly architecture

Use Bicep, GitHub Actions, Azure Static Web Apps, Azure Functions, the core TraceOps.Dev API, and OIDC-based deployment.

// workflow

Built for repo audits and implementation plans.

The API and MCP server share the same small loop: create, search, claim, update, and link work items. That gives agents enough state to coordinate without taking over source control.

  1. An audit, agent, or maintainer finds a concrete issue, feature, or audit finding.
  2. TraceOps.Dev stores it as a work item with tenant, repository, type, category, severity, status, source, files, and tags.
  3. An agent or engineer searches for work, claims the next actionable item, and updates status as implementation moves.
  4. External branch, commit, and PR links are stored as metadata; TraceOps.Dev does not mutate repositories in v0.1.

// docs

API, MCP, and work item details.

Product

Overview

TraceOps.Dev is a hosted website, API, and MCP workflow for tenant-scoped repository work items.

Start

Setup

Sign in to the hosted service, create a key, configure MCP clients, and verify the connection.

HTTP

API

The hosted TraceOps.Dev API is the source of truth for work items and tenant-scoped automation.

Agents

MCP

The TraceOps.Dev MCP server is a local stdio bridge to the hosted TraceOps.Dev API.