Tray Headless
Build on Tray from any AI IDE. The full Tray platform — workflows, connectors, authentication, validation, and runs — built from natural language in your AI development environment.
Tray Headless brings the complete Tray platform — building workflows, configuring connectors, setting up authentication, validating, and running — into your AI development environment, as text. It's the full platform surface, not a subset or a wrapper.
Two ways to use it
There are two ways to work with Tray Headless, both backed by the same hosted Tray platform.
- Tray Headless for Claude Code — a guided experience. The
tray-workflowsplugin bundles skills, a connector-research subagent, built-in validation, and an opinionated build process on top of the Tray platform tools. Best when you want the assistant to plan, research, build, validate, and test a workflow for you from a plain-English description. - Tray Headless MCP — the same Tray platform capabilities exposed as MCP tools, hosted at
api.tray.io/mcp. Point any MCP-compatible client at it — Cursor, Codex, Windsurf, Claude Code, or your own agent. Best when you're working outside Claude Code or building your own automation against Tray.
Both talk to the same hosted Tray platform, so anything built headless opens in Tray's visual builder with no migration. Build in text, hand off to the canvas, or move between the two freely.
Which should I use?
| Tray Headless for Claude Code | Tray Headless MCP | |
|---|---|---|
| Best for | Guided, end-to-end workflow building in Claude Code | Using Tray tools in any MCP client or your own agent |
| Includes | Skills, research subagent, build process, validation surfacing, workspace pinning | The platform tools only |
| Setup | /plugin install + sign in | Add an HTTP MCP server entry + sign in |
| What you get | Guided workflow building + platform tools | Platform tools only |
The Claude Code plugin is one client of the Tray MCP server; the difference is that the plugin adds the guided build process, skills, research subagent, and workspace pinning on top. The raw server gives you the tools, and you (or your agent) drive them.
How it fits together
A few terms recur across both surfaces:
- Workspace — your Tray environment. Every build targets one workspace; its Workspace ID comes from your workspace settings.
- Project — a container for workflows within a workspace.
- Workflow — a trigger plus a series of steps. The unit you build and run.
- Connector — an integration such as Salesforce, Slack, or Google Sheets, with versioned operations. Some connectors are triggers.
- Authentication — a stored credential for a connector's service, reused across workflows. Both surfaces use a one-time browser sign-in to Tray (OAuth2) — there's no API token to generate or paste.
- Validation — Tray's server-side structural checks, run on every change and as a whole-workflow audit.
- Visual builder — Tray's graphical workflow editor. Headless builds open there directly; there's no migration step.
Regional availability
Tray Headless is currently available for US region workspaces only. The service connects to api.tray.io/mcp.
Supported regions:
- US (United States) ✓
- EU (European Union) — Coming soon
- Other regions — Coming soon
If your workspace is in a region outside the US, or if you have questions about regional availability, please contact your Customer Success representative or account team.