# Tray.io MCP

> Tray.io MCP Server lets your AI agent control automations directly within Tray.io. Instead of navigating complex cloud panels or clicking through dashboards, you use natural language to manage workflows, audit data flows, and monitor integrations in real time. It connects your LLM client straight into the operational layer of your integration platform.

## Overview
- **Category:** growth-engine
- **Price:** Free
- **Tags:** workflow-automation, data-integration, api-orchestration, business-process-automation, low-code, data-sync

## Description

You'll connect your AI agent straight into **Tray.io**’s operational layer. This means you bypass the clunky cloud panels and dashboards, managing automations, auditing data flows, and checking integrations using nothing but natural language. Your LLM client acts as a direct control panel for everything running inside Tray.io.

To audit your entire setup, you've got tools for inventorying every piece of moving parts. You can use `list_workflows` to pull an index listing the names and metadata for every single workflow defined in your account. If you need to know what pre-built solutions are available across the company, call `list_integration_solutions`; this gives you a full rundown of all saved templates. To find out exactly what services can plug into your system, use `list_available_connectors`—you'll get names for everything from Stripe to Salesforce.

When you zero in on one specific workflow, the process is simple. You retrieve granular metadata about that single instance using `get_workflow_details`. If you need a comprehensive view of what’s running and who owns it, you can check your system identity by calling `get_authenticated_user`; this confirms the name and details of the user currently logged in.

For auditing actual data movement, you've got deep logging capabilities. You can run `list_workflow_executions` to pull recent execution history on a specific workflow ID or name; this shows you exactly which runs succeeded and which ones failed. Knowing *why* something broke is key, so checking that execution log tells you the status for every node in the chain.

Your AI agent lets you run these checks conversationally: check your user identity with `get_authenticated_user` to confirm system boundaries; list out all existing workflows using `list_workflows`; pull specific details on one workflow using `get_workflow_details`; see what other people built by calling `list_integration_solutions`; know what services you can hook up via `list_available_connectors`; and finally, monitor the actual success or failure rates of a process by checking history with `list_workflow_executions`.

## Tools

### get_authenticated_user
Retrieves the name and details of the user currently logged into the system.

### get_workflow_details
Pulls specific metadata about a single workflow ID or name in Tray.io.

### list_available_connectors
Lists every service connector (like Stripe, Slack) that can be added to an integration.

### list_workflow_executions
Lists recent execution history, showing success and failure status for a specific workflow.

### list_integration_solutions
Retrieves a list of all pre-built solutions or templates saved in the account.

### list_workflows
Provides an index of all workflows defined within the Tray.io account.

## Prompt Examples

**Prompt:** 
```
List all active workflows in my account right now.
```

**Response:** 
```
I've pulled a total of 3 active workflows from your repository:
- Name: Salesforce Lead Sync, ID: wf-a1b2
- Name: Zendesk Ticket Router, ID: wf-c3d4
- Name: Stripe Financial Log, ID: wf-e5f6
```

**Prompt:** 
```
Can you check the latest execution history for workflow wf-a1b2?
```

**Response:** 
```
Checking execution logs for wf-a1b2. The last 2 runs completed successfully with status: SUCCEEDED. The latest run took 4.2 seconds on 2026-10-05T14:22:11Z. No anomalous behavior detected locally.
```

## Capabilities

### Audit Integration Solutions
Lists all pre-built integration templates (solutions) within your Tray.io account.

### Discover Available Connectors
Retrieves a list of every service connector you can use in the platform, such as Salesforce or Stripe.

### List All Workflows
Provides an overview and names of every workflow currently set up in your account.

### Get Workflow Details
Pulls specific metadata about a single, named workflow instance.

### Check Execution History
Reads the detailed logs and success/failure status for recent runs of a specific workflow.

### Verify User Identity
Checks your current user's authentication details and system access boundaries.

## Use Cases

### Need to audit a complex CRM data migration.
The architect needs to know how the Salesforce integration works. They ask their agent, which runs `list_integration_solutions` first. The agent lists all templates; then the architect uses `get_workflow_details` on the specific 'Salesforce Sync' workflow to confirm the data fields and trigger conditions before writing a single line of code.

### A critical financial sync failed overnight.
The ops lead wants to know why the Stripe logs stopped updating. They use `list_workflows` to find the 'Stripe Financial Log' workflow ID, then they call `list_workflow_executions` with that ID. The agent returns the last five runs, showing a failure status and an error message pointing directly to the failed node.

### Checking if a new service connector is available.
A developer needs to integrate with a niche marketing tool but isn't sure if Tray.io supports it. They run `list_available_connectors` and search the returned list for the required API type, instantly confirming feasibility before spending time on setup.

### Onboarding a new team member to the platform.
A manager needs to show a new hire which pipelines are active. They ask their agent to run `list_workflows`. The agent provides an indexed list of all workflows, giving the new employee immediate visibility into the organization's current data movement map.

## Benefits

- Stop guessing if a pipeline broke. Using `list_workflow_executions` lets you check the exact logs, confirming which nodes succeeded or crashed on a specific run.
- Mapping integrations gets faster. You can use `list_available_connectors` to see every service—Salesforce, Zendesk, etc.—before you even start designing your solution.
- Get a full system picture instantly. Running `list_workflows` gives you a complete index of everything running in the account without navigating multiple dashboard tabs.
- Diagnose issues fast. If a client reports a sync failure, use `list_workflow_executions` to grab the recent error logs and pinpoint exactly where the data flow broke down.
- Verify access points easily. The `get_authenticated_user` tool checks your current session's tokens and boundaries so you know exactly what permissions your agent has.

## How It Works

The bottom line is that your AI agent performs complex system checks—like reading logs or listing components—without you ever leaving the chat interface.

1. Attach the application component to your generative environment (Claude, Cursor, etc.).
2. Provide your Tray Access Token and any required regional endpoint configuration via the portal slot.
3. Engage your agent using natural language commands to audit operations or check for broken integration loops.

## Frequently Asked Questions

**How do I check if a workflow is active using list_workflows?**
The `list_workflows` tool provides an index of every workflow defined in your account. It gives you the names and IDs, allowing you to know exactly which workflows exist before checking their status.

**Can I use get_workflow_details to find out what a specific connector does?**
No, `get_workflow_details` only gives information about the workflow itself (like its trigger or name). For available connectors, you must use `list_available_connectors`.

**What is the best tool to check for failures? Is it list_workflow_executions?**
Yes. You absolutely need `list_workflow_executions`. This tool reads the historical log data for a specific workflow, telling you exactly which steps succeeded and where things crashed.

**Does get_authenticated_user tell me if my API key is valid?**
It verifies your user identity tokens and system boundaries. While it confirms *who* you are in the system, for API key validity, you'd need to check external credentials or use a specific connector test tool.

**How do I use list_available_connectors to check platform compatibility?**
It lists every service connector available in Tray.io. You can confirm instantly if a needed platform—like Salesforce or Stripe—is supported for building an integration.

**What does list_integration_solutions show me about my account?**
This tool provides a catalog of all saved solutions and templates in your workspace. It lets you find existing, high-level automation structures without needing the specific workflow ID.

**Can get_authenticated_user provide details on user permissions or roles?**
Yes, it retrieves the full profile of the currently connected account. You'll see granular data like the user's ID and associated access levels within Tray.io.

**Does list_workflows only show active automations in my account?**
No, it lists every single workflow record stored in your system. This gives you a complete inventory view, including drafts or solutions that are currently inactive.

**Where do I find my primary Tray.io Access Token?**
Log in precisely through your Tray.io admin interface. Focus toward the user settings and click heavily on 'Profile' located usually top-right corner or bottom-left depending on your tier. Inside, shift directly to Personal Access Tokens to view the encoded array. Keep generated values incredibly safe as they orchestrate mass systems.

**How important is defining the TRAY_REGION property?**
The API fundamentally varies endpoints based on your region (e.g., `us1`, `eu1`, `apac1`). If unassigned or blank, it legally defaults to `us1`. If your instance is physically nested anywhere else in global scope, you must insert your region, or your API logs will constantly fail resolving token access domains.

**Should I use a User Token or a Master Token for the Tray MCP?**
You must use the Master Token. The Master Token acts as an administrative key allowing you to list authentications and orchestrate workflows across your organization's workspace, whereas a User Token is restricted.