Documentation
Everything about using ezmodo — from your first project to connecting a coding agent over MCP. New here? Start with the Quick Start Guide.
Documentation directory
Public documentation published on ezmodo by other teams.
Projects
How projects work in EzModo: creating and configuring them, sequential numbering, simple versus full mode, where a product's code paths and screens live, project settings, and archiving.
Project types
What a project's type changes: the words ezmodo uses for epics, tasks and their statuses, and which features (Catalogs, Testing, Designs) the project shows. Includes the per-type feature matrix and the other switches — Simple mode, plan, public visibility — that also hide features.
Tasks
How tasks work in EzModo: fields, statuses, task types, assignment to people or AI agents, dependencies, steps, sprint scheduling, and how a task connects to the features its code belongs to.
Epics
Guide to epics: deliverable-shaped containers for related tasks, with statuses, automatic progress, breaking work down with your own agent, and alignment to goals through milestones.
Milestones
Guide to milestones — release boundaries with target dates, freezes, release tracking, changelogs, and goal alignment.
Sprints
Guide to sprints and the Board: calculated time boxes, the cross-project task wall at /{orgSlug}/board, points, capacity, closing a sprint, and velocity.
Goals
Guide to workspace-level goals: outcome-shaped strategic objectives that track progress through linked milestones, with key results and sub-goals.
Workspaces, Teams and Roles
Guide to workspaces (organizations), teams, member invitations, and the five built-in roles, plus project-level access control.
Documents and Knowledge Base
Guide to the per-project knowledge base: creating documents, folders and index pages, diagrams, sharing, version history, and how documents feed AI context.
AI in ezmodo
How AI works in ezmodo after bring-your-own-agent: connect your own agent (plugin, connector, other MCP clients), what ezmodo's own AI still does ("How it works" summaries and replay report narratives), and AI credits per plan.
Features and the Capability Map
Features: durable product capabilities that link to work and own code paths. Covers the feature/epic distinction, the 'is this a feature?' test, creating, scope across projects, nesting, status, linking work, code paths, grounded 'How it works' summaries, the wider capability map with plan gating, and troubleshooting.
Install the Claude Code Plugin
Install ezmodo into Claude Code with one /plugin install, then sign in by clicking a link — no API key, no config file, no CLI. The plugin bundles the MCP server, the work-tracking skills, five slash commands and two reminder hooks.
Using EzModo with Other Coding Agents
Connect EzModo to Cursor, Windsurf, Zed, Codex or any other MCP client with one config block and a browser sign-in. Covers what is and isn't lost compared with Claude Code, and where each client keeps its config.
Connect Claude to ezmodo
Add EzModo as a custom connector in Claude — works on claude.ai, Claude Desktop, iOS and Android with no install. Covers the OAuth sign-in, the client ID step Keycloak currently requires, the three consent scopes, and how the connector's tool surface differs from the local one.
What You Can Do With ezmodo MCP
Tour of the ezmodo MCP tool catalog: the 119 tools by category (including the public tracker), example prompts, multi-project handling, permissions and plan limits, and the actions that reach people outside your organization.
Authentication and API Keys
How CLI authentication works — browser OAuth by default, API keys for CI and headless use, where credentials are stored, and how to rotate or revoke them.
Troubleshooting CLI and MCP
Field guide for ezmodo MCP and CLI problems, organised by setup: the Claude Code plugin, the remote connector, any MCP client, the CLI itself, and legacy ezmodo mcp install configs.
Install the CLI
Install the EzModo CLI on macOS, Linux, or Windows — quick install, version-pinned install, manual install, verification, upgrade, and uninstall.
Set Up MCP for Claude Desktop
Connect Claude Desktop to ezmodo: the remote connector (recommended), a local npx server for the local-machine tools, and the legacy ezmodo mcp install route.
Set Up MCP for Claude Code
Connect Claude Code to ezmodo with the plugin, and move an old ezmodo mcp install --claude-code setup over to it.
Choosing the Right Plan
Pick the right ezmodo plan: personal versus team, what each tier is actually for, AI credits, when to upgrade, and common scenarios.
Plan Limits and Usage
What counts against each limit — AI credits versus agent writes — how seat billing works, what happens at a limit, and where to see usage.
Managing Your Subscription
Day-to-day subscription management: trials, upgrades and downgrades, billing intervals, payment methods, invoices, seats, cancellation, and subscription states.
How releases work
The pieces of a release and how they fit: milestones vs epics vs features, milestone vs candidate vs parent milestone, parent milestones, rejected-before-ship vs broken-after-ship, how an epic joins a milestone, deliverables, releases, candidates, environments and routes, the checklist, gates and enforcement, readiness, waivers, sign-off, promotion from the release page (including idempotent re-promotion and CI-reported deployments), holding CI deploys, release contents, and when in-review work completes.
Shipping a release
The how-to for shipping: setting up environments and the release process, releasing step by step from the release page (opened from the milestone's release status), per-build steps, release notes and store text, testing a build, release settings and step-owner notifications, shipping several deliverables, Release this epic and freezes, the CLI, and troubleshooting.
Setting up releases from CI
End-to-end CI setup: one API key with write:releases and write:testing, kept as a GitHub environment secret limited to main; the production approval on its own reviewers-only environment (production-approval) so the release gate runs after the approval, right before the deploy (a job waits for approval when it starts, so a gate before it answers stale); JSON bodies sent base64-encoded in a payloadBase64 envelope; job order (report, upload, approve, gate, deploy); copy-paste reusable GitHub Actions workflows for the gate and deployment reports (including status waiting with awaiting/note); a hold-off-first rollout; the gate response; GitLab, Jenkins, shell and CLI equivalents.
Sending test results from CI
Reference for uploading CI test results: the key, the upload fields and formats (JUnit, xUnit, JSON), matching results to cases by external key, filling an open run, duplicates, the response, and uploading from the CLI or an AI agent.
Gates reference
Every release gate type with its settings and what it checks, which gates can reject a build, the recommended gate set, enforcement and readiness rules, and troubleshooting for CI calls (401, 403 JSON vs HTML and the base64 body envelope, unknown deliverable, 400, environment names, test runs that don't count, pending gates).
Release this epic
Ship one epic on its own in one step: Release this epic creates a milestone for the version, adds the epic and the first candidate; the suggested version, epics already in a milestone, the manage_epic action, and troubleshooting.
Freezes
Freezing a project to one milestone while it ships: the four freeze types (Milestone Freeze, Stabilization, Testing Only, Full Freeze), that only starting work is checked, what counts as inside the milestone, freezing and lifting from the release page's Freeze phase or MCP, and troubleshooting.
Welcome to ezmodo
An introduction to EzModo: what it is, who it is for, and the core concepts — workspaces, projects, epics, tasks, features, milestones, goals and tags — with pointers to the deeper guides.
Quick Start Guide
Step-by-step guide to get new users running in under five minutes: account, view preference, project, tasks, connecting your AI agent, navigation, and team invites.
Understanding ezmodo Concepts
Comprehensive guide to ezmodo's core concepts: workspaces, goals, features and the code paths they own, designs, catalogs, projects and project types, milestones, epics, tasks, sprints, test suites and cases, documents, folders, tags, teams, and roles. Written in plain language, including the noun/verb split between features and work.