Name: Mcptix
Author: ownlytics

LABSCO 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 runs both through npx, which picks up the mcptix command from that local install. 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

Follow the published steps — npm install @ownlytics/mcptix

See installation options

USE CASES

01

Breaking a feature into work you can actually start

Ask for the decomposition and let the assistant write each ticket with its plan attached.

02

Handing a plan from one assistant to another

Write the detail into the ticket's context field so the coding agent reads it instead of being re-briefed.

03

Keeping long plans out of the conversation

Store filenames, line numbers and method names on the ticket, and reference them when needed.

04

Seeing what the assistant actually filed

Open the local UI and read the tickets rather than trusting the summary in chat.

BEFORE YOU INSTALL

What to know first

Requires

Node.js 14 or later

Where it runs

Both documented clients run the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

# Install mcptix
npm install @ownlytics/mcptix

# Initialize mcptix in your project
npx mcptix init

# Start mcptix
npx mcptix start

MCP Clients

Roo Code, Claude Desktop

JSON

{
  "mcpServers": {
    "mcptix": {
      "command": "<YOUR_PATH_TO_NODE>",
      "args": [
        "<YOUR_PATH_TO_NODE_MODULES>/@ownlytics/mcptix/dist/mcp/index.js"
      ],
      "env": {
        "MCPTIX_HOME_DIR": "<YOUR_PATH_TO_PROJECT>/.mcptix",
        "HOME": "/home/<YOUR_USERNAME>"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Mcptix