Getting Started with Agent Gateway

This guide covers the prerequisites and initial setup steps for using Tray Agent Gateway with MCP servers.

Prerequisites

User Permissions

Workspace Administrator Role - Required to:

• Enable and configure MCP servers
• Add Workflow Tools and Connector Tools
• Access Agent Gateway settings in workspace settings

Workspace Member Role - Required to:

• Execute tools through configured MCP servers
• Requires valid API token with appropriate permissions

Technical Requirements

Supported AI Client (at least one):

• Claude Desktop
• VS Code with Claude extension
• Cursor
• Windsurf (Codeium)
• Any other MCP-compatible client

Development Environment:

• Node.js installed (for running Tray MCP client setup utility)
• Command line access
• Internet connection

Tray Platform Requirements:

• Active Tray.ai workspace
• Workspace ID (UUID from workspace URL)
• API token

Finding Your Workspace ID

Your Workspace ID is a UUID in your workspace URL:

https://app.tray.io/workspaces/12345678-abcd-1234-ef56-0123456789ab/...
                               └──────────────────────────────────┘
                                        Workspace ID

Copy this UUID - you'll need it when configuring MCP clients.

Creating an API Token

API tokens authenticate MCP client connections to your workspace.

Organization admins create API tokens from Account Settings → Tokens → Create API user. The token must have appropriate permissions for the workspace where your MCP server is configured.

For complete token creation and management instructions, see API Users & Tokens.

Tool Limits and Recommendations

Recommended Limits

15-20 tools maximum per MCP server

This recommendation is based on LLM performance:

• Better tool selection accuracy
• Faster agent response times
• Reduced hallucination risk
• Improved user experience

No hard technical limit exists, but exceeding 20 tools degrades agent performance.

Multiple Server Strategy

If you need more than 20 tools:

Create separate MCP servers for different use cases:

• Customer support tools server
• Sales tools server
• IT operations tools server

AI clients can connect to multiple MCP servers simultaneously.

Use different workspaces for team/project isolation:

• Each workspace has its own MCP server
• Better access control and governance
• Clear separation of concerns

Next Steps

With prerequisites complete:

1. Configure MCP Server - Enable and set up your first MCP server
2. Add Workflow Tools - Create Composite Tools from workflows
3. Add Connector Tools - Expose connector operations
4. Connect AI Client - Configure your AI assistant