TeamFlow in Cursor

1. Install

npx -y github:macleodlabs-ai/teamflow-plugin skills install --for cursor

That writes:

• .agents/skills/<skill>/SKILL.md — the ten skills, in the shared skills directory this tool reads
• .cursor/rules/teamflow.mdc — the always-on reporting instruction, generated from the same SKILL.md sources
• .cursor/mcp.json — the TeamFlow MCP server
• .teamflow/hooks/cursor.sh — the hook itself; it calls teamflow hook --for cursor, prints nothing the tool could read as a denial, and exits 0 whatever happens
• .cursor/hooks.json — the hook registration: afterFileEdit, postToolUse, postToolUseFailure, afterShellExecution and stop

Add --scope user to install for every project on this machine, or --dry-run to see the file list without writing anything. Re-running it replaces TeamFlow's block and leaves the rest of each file alone.

2. The skills you get

The same ten the Claude Code plugin carries, generated from the same SKILL.md files. This tool loads them as skills, one directory each, with the name prefixed so they do not collide with anybody else’s in a shared directory.

Each one wraps a github:macleodlabs-ai/teamflow-plugin subcommand, so the skill and the shell command are the same thing. Inside Claude Code they are /teamflow:login, /teamflow:status and so on.

3. Sign in once

Open Settings -> MCP (or Tools & Integrations on newer builds). teamflow appears with a Needs login control; clicking it opens the browser, and Cursor stores the token. The tools macleodlabs_teamflow_capabilities, macleodlabs_teamflow_call and macleodlabs_teamflow_buy_credits turn green when it is done.

Then, in the chat: "run teamflow status".

4. By hand

The installer writes this for you. If you would rather paste it: .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.

{
  "mcpServers": {
    "teamflow": {
      "url": "https://codercat.io/mcp"
    }
  }
}

A remote server needs url and nothing else. type is for stdio servers, and an API key belongs nowhere in this file.

The rule has to be .mdc: Cursor ignores plain .md in that directory. The installer writes the frontmatter (alwaysApply: true) for you.

Cursor scans .cursor/skills as well as the shared root, so keep the skills in one place: a repository with both would show Cursor each skill twice.

The generated rule at cursor.mdc is a different thing: it teaches an agent how to call a paid MacleodLabs service and handle HTTP 402. The two sit side by side.

5. The stages to report

JIRA is the thirteenth: the ticket exists and nothing has started. Statuses are running, success, waiting, blocked, failed and idle. This is the same vocabulary the Claude Code plugin derives, so a ticket moved from here sits in the same column as one moved by Claude.

6. Without the agent

Anything that runs in a shell posts the same report with no model involved. A git hook, an npm script, a run configuration, a CI step:

npx -y github:macleodlabs-ai/teamflow-plugin report --issue DAEMON-142 --stage LOCAL_TEST \
  --status success --summary "42 tests, 0 failing"

Same envelope, same transport, same credential. Prefer it wherever the board has to be right whether or not an agent remembered. npx -y github:macleodlabs-ai/teamflow-plugin report --help lists every flag.

7. What this is not

Cursor reports automatically through its own hooks: afterFileEdit, postToolUse, postToolUseFailure, afterShellExecution and stop. Nothing to remember. Cursor has the fullest hook set outside Claude Code, including a distinct failure event, so a red test run reports rework rather than a green gate. Cursor documents command, output and duration for afterShellExecution and no exit status, so a shell command is classified only where Cursor does supply one; the definite signal is postToolUse and postToolUseFailure.

The hooks see this tool's own calls and nothing else. A test run in another terminal, a merge from the web UI, a deploy from a pipeline: put npx -y github:macleodlabs-ai/teamflow-plugin report in the git hook or the script that already runs on every change, and those land on the board too.

8. What leaves your machine

TeamFlow is a delivery map for Jira, Linear and GitHub issues, run by MacleodLabs. Reports carry derived state only: a ticket key, a stage, a status, a short summary and evidence links. Prompts, diffs, source code, commands and logs are never sent and are rejected before they are charged.

• Every client
• llms.txt
• Capabilities
• The reporting contract, in full