Platform / AI Development
Code or canvas. One platform.
Tray Build for visual low-code. Tray Headless for Claude Code, Cursor, Codex, and any MCP-compatible AI IDE — with a dedicated plugin for Claude Code. Both are first-class interfaces to the same platform — shared governance, and the same audit trail whether you write code or drag a canvas.
What it does.
Tray Build
The visual low-code builder for developers, analysts, and operators. Branching, approvals, error handling, and full workflow logic — without custom code. Ship any process in days.
Learn more →Tray Headless
NewThe full Tray platform in Claude Code, Cursor, Codex, and any MCP-compatible AI IDE. A dedicated plugin for Claude Code — MCP for everything else. Build, validate, and deploy workflows without leaving your IDE.
Learn more →Visual workflow canvas
Drag, connect, and configure complex workflows — branching, loops, error paths — without a line of code.
Tray Headless for Claude Code
The best Tray experience in Claude Code. Config, typed tools, validation hooks, and six built-in skills — out of the box.
AI steps, built in
Drop LLM calls, classification, and document extraction directly into any workflow step. No separate AI platform.
Tray Headless MCP
Full platform as MCP services — for Cursor, Codex, Windsurf, or any MCP-compatible AI IDE.
38 workflows built in a 2-week POC
“Tray is the holy grail for software development. It has allowed us to build a single master workflow that is infinitely configurable and scalable without cumbersome code.”
What you can build
See what teams build with AI Development.
Watch how purpose-built agents handle real work — short walkthroughs of how each one operates.
-
Build a workflow in Claude Code.
Use Tray Headless for Claude Code to scaffold, configure, and validate a multi-step workflow — connectors, branching, error handling — without leaving your IDE.
-
Hand off to the ops team.
The same workflow built headless opens in Tray Build's visual canvas. Operators can extend, monitor, and manage it without touching the code.
-
Ship new connectors from an API spec.
Claude CDK turns an OpenAPI spec into a production-grade Tray connector. New integrations in minutes — not days of boilerplate.
-
Validate before you deploy.
Tray Headless MCP's Validate tier checks per-step schemas and runs whole-workflow structural audits. Catch broken configurations before they reach production.
-
Build once, use everywhere.
A developer builds a workflow in Claude Code. An operator edits it in Tray Build. IT governs it centrally. Same artifact — every team working in their preferred surface.
-
Reuse approved building blocks.
Publish agents, sub-workflows, and connector configs as composable building blocks. Teams across the org build on approved patterns — IT knows exactly what's in production.
The full Tray Headless stack.
Tray Headless is a layered architecture — from the best IDE experience to direct REST access. Every layer exposes the complete platform.
- Tray Headless for Claude Code — best experience in Claude Code, with CDK, skills, and validation hooks
- Tray Headless MCP — full platform, any AI IDE
- Headless Core — RESTful platform APIs
- Tray AI Orchestration Platform — Integration · Automation · MCP · Governance · 700+ connectors
Frequently asked questions
What's the difference between Tray Build and Tray Headless? +
Tray Build is the visual low-code builder — the fastest way to build workflows and agents without writing code. Tray Headless is the same platform exposed for AI IDEs — Claude Code, Cursor, Codex, Windsurf. Both interfaces share the same connectors, governance, and execution engine. Teams choose the right surface for the right job.
Is Tray Headless MCP-only? +
No. Tray Headless MCP is the recommended path for AI IDEs, but Headless Core — Tray's full RESTful platform APIs — is available for teams who want direct API access without MCP.
How does Tray Headless for Claude Code differ from Tray Headless MCP? +
Tray Headless MCP is the foundation — the full platform as MCP services. Tray Headless for Claude Code is the native plugin built on top of that: config files, typed tool definitions, response formatters, validation hooks, and six built-in skills, all optimised specifically for Claude Code.
Which models can I route to? +
OpenAI, Anthropic, Google, AWS Bedrock, Azure OpenAI, and self-hosted endpoints. Routing rules can mix models per step or per agent — cost, latency, or policy-based.
Do I need a separate SKU for the developer experience? +
No. Tray Build and Tray Headless are the same product. Pricing follows usage, not interface type.
One platform
Built as one. Not stitched together.
Every capability runs on the same connector library, governance layer, and data model — designed together from day one.
See AI Development in action.
Walk through a scenario from your stack with a Tray.ai expert.