Getting Started
Itera customer documentation is organized around three tracks:
- Platform docs are required. They explain the core customer integration and the role of
itera.yml. - Inspector docs are optional. They cover the React, Vue, and Angular component inspector integrations for teams that want deeper component-level visibility.
- MCP docs are optional. They cover the Itera MCP server for compatible MCP clients and coding agents that need Itera task context, implementation-plan scope, prototype details, or failure-review history.
Recommended reading order
- Start with the Platform Overview to understand the required setup.
- Use this site as the canonical entry point for customer-facing integration guidance.
- Add the Inspector Overview only if your team needs the optional component inspector.
- Add the MCP Overview only if your team wants MCP-compatible clients or agents to work with Itera context.
What each track covers
Platform
The platform section is the foundation for every integration. It covers how itera.yml shapes the runtime setup, how Itera connects to your application, and where to look when configuration choices affect behavior.
Inspector
The inspector section is for teams integrating the optional component inspector. It covers the bridge and runtime startup model, React integration, Vue integration, Angular integration, framework-specific entrypoints, builder-based Angular source metadata, and troubleshooting for bootstrap timing, host-origin mistakes, and framework-specific source metadata gaps.
MCP
The MCP section is for teams connecting compatible MCP clients and coding agents to Itera through OAuth. It covers URL-only connection setup, the tool reference, practical agent prompting workflows, and troubleshooting for discovery, OAuth, tool visibility, and structured tool errors. MCP setup is not required for normal application runtime configuration.
Managed vs self-managed deployments
When your application is deployed inside Itera-managed infrastructure, Itera infrastructure already injects the documented inspector environment variables during deployment. Teams only need to wire those values into the app themselves for local development or customer-managed deployments outside Itera-managed infrastructure.
Next steps
Move into the platform overview for the required integration path, the inspector overview when your rollout needs the optional component inspector, or the MCP overview when your team wants MCP-compatible clients or agents to work with Itera context.