Labsco
MCP SERVER

Mcptix

by ownlytics ↗

A local ticket tracker with a field built for AI plans — `agent_context` holds the full Markdown breakdown, so the planning model and the coding agent share one database instead of one context window.

Project & Task Management
Summary
A memory bank shaped like a ticket queue.

The workflow this is built for is two assistants and one database: a planning model breaks a feature into tickets with the full plan in `agent_context`, and a coding agent picks each one up and executes it without regenerating the context. That is a real answer to the cost of re-explaining a project every session. Absolute paths in the config are the thing that trips up the first setup — relative ones silently fail.

What it is

A ticket tracking system that runs in your project directory with its own UI, designed so an assistant can create and read tickets over MCP. The distinguishing piece is the `agent_context` field: a place to store a long Markdown plan — filenames, line numbers, method names — attached to the ticket rather than held in the conversation.

What you get
  • Tickets you can create, read, update and delete, for tasks, bugs and features
  • Comments on tickets, so a thread of decisions stays with the work
  • The `agent_context` field — extensive planning documents in Markdown, stored on the ticket instead of cluttering the conversation
  • A Complexity Intelligence Engine that tracks how complex each ticket is
  • A local UI on port 3000 for reading what the assistant wrote
  • One shared database behind both surfaces, so a planning assistant and a coding agent read and write the same tickets
Requirements

No account and no key. Node.js 14 or higher. `npm install @ownlytics/mcptix`, then run the `mcptix` command it installs — `mcptix init` to create the `.mcptix` folder, config and database, and `mcptix start` for the UI. The README reaches both through npx, which looks for an unscoped `mcptix` package npm does not have. Init also writes `.mcptix/mcp-server-config.json`, which is what you copy into your assistant's config — every path in it must be absolute, including the node binary from `which node`, the path to `dist/mcp/index.js` in `node_modules`, `MCPTIX_HOME_DIR` pointing at your project's `.mcptix`, and `HOME`. Your assistant launches the MCP server itself; `mcptix start` runs only the UI. Package `@ownlytics/mcptix`, marked beta, under BSL 1.1.

Setup effort

One command — npm install @ownlytics/mcptix