API & MCP

Everything a person can do on Trackwell Query Filter, a program or AI agent can do with the same inputs and get the identical result.

HTTP API

Trackwell Query Filter

Runs a query such as “project = WEB AND status != Done AND assignee = me ORDER BY priority” over an exported issue list (Trackwell project, Trackwell CSV or Jira CSV) and returns the matching issues as a table and CSV. Same query language as the list view in Trackwell.

Inputs of Trackwell Query Filter
FieldTypeDefaultDescription
issuestextarea—Issues (JSON or CSV). A Trackwell project file (.trackwell.json), a Trackwell CSV export or a Jira CSV export.
issuesFilefile—Issues file (optional). Used instead of the pasted text when given.
querytext"statusCategory != Done ORDER BY priority, created"Query. Fields: project, key, type, status, statusCategory, priority, severity, assignee, reporter, labels, component, fixVersion, sprint, parent, epic, created, updated, resolved, due, resolution, text, summary, storyPoints and custom fields by name. Operators: = != > >= < <= ~ !~ IN, NOT IN, IS EMPTY. Values: words, "quoted text", 2026-11-24, -7d, me, today(), openSprints().
metext—Who is “me”. A person’s name or id in the issue list. Used by assignee = me.
asOfdate—Today is. Relative dates (-7d, today()) count from this day. Empty = today.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

{
  "mcpServers": {
    "trackwell-jql-filter": { "type": "http", "url": "https://trackwelljqlfilter.usefulweb.app/mcp" }
  }
}