Itera Customer DocsOne place to start your Itera customer integration

Set up the required platform configuration with `itera.yml`, then add optional inspector or MCP workflows when your team needs deeper UI visibility or agent access to Itera context.

Getting Started

Platform Overview

MCP Overview

Inspector Overview

Required platform setup

Every customer integration starts with the Itera platform and an `itera.yml` file that describes how Itera should understand and work with your application.

Optional inspector integration

The component inspector is a separate layer for teams that want richer component-level visibility inside supported React, Vue, or Angular applications.

Optional MCP workflows

Itera MCP lets compatible MCP clients and coding agents create tasks, read Itera task context, inspect implementation plans, debug prototypes, and review failure history through OAuth.

Start with the required path

The platform integration is the baseline for every customer deployment. If you are new to Itera, begin with Getting Started and then move into the Platform Overview to understand where itera.yml fits.

Add the inspector only when you need it

The component inspector is optional. It is useful when your team wants more UI context inside a supported React, Vue, or Angular application, but it is not a prerequisite for the core platform integration. The Inspector Overview explains when it belongs in your rollout.

Connect agents through MCP when useful

Itera MCP is optional and separate from normal application runtime setup. Use it when a compatible MCP client or coding agent needs to create tasks, read Itera task context, inspect planned PR scope, debug prototypes, or review failure history. Start with the MCP Overview when those workflows fit your team.