Connect

MCP Server

One config line. Your agent reads tasks, pushes updates, ships work.

Why this matters

The bit that hurts

The MCP server is the beating heart of TeamX. It is what makes every other feature work with AI agents. Add one config line to Claude Code, Cursor, or Codex and your agent gains superpowers: reading tasks with full context, pushing activities, managing sprints, completing work with institutional memory. Composite tools like begin_task and complete_task replace three separate API calls with one smart operation that includes context, affected files, and decision capture.
How it works

The flow, in 4 steps

01

Add the config

One JSON snippet in your agent's settings file. Works with Claude Code, Cursor, Codex, and any MCP-compatible agent.

02

begin_task loads context

When your agent starts a task, begin_task returns affected files, recent commits, decisions, and relevant docs. Your agent starts smart.

03

Work and push

As your agent works, it can push activities, update task status, and coordinate with other agents through the MCP protocol.

04

complete_task captures memory

When done, complete_task records touched files and decisions. This builds institutional memory that surfaces on future tasks.

What you get

In the box

Composite tools: begin_task, complete_task, set_task_spec
Context engine: affected files, recent commits, decisions, docs
Institutional memory: decisions flow up to epic level
Conflict detection: know when another agent touches same files
Works with Claude Code, Cursor, Codex natively
Full API for custom agent integrations

Try mcp server today.

Available on the free plan. Sign up, paste one config line, see it in action in five minutes.