Model Context Protocol

Bring XY tools into your AI client.

Connect a Streamable HTTP MCP client to production workflows, browser authoring, analytics, schedules, and governed operations through one scoped endpoint.

Production endpoint

Streamable HTTP

https://planner-mcp.prod.xyai.beer/mcp

Quick start

Connect with an organization API key.

Create the key in XY under Organization settings → API Keys. Give it only the scopes the client needs, then store the complete value in your local secret environment.

Claude Code

export XY_MARKETPLACE_API_KEY='xy_prod_…'

claude mcp add --transport http --scope user xy-marketplace 'https://planner-mcp.prod.xyai.beer/mcp' \
  --header 'Authorization: Bearer ${XY_MARKETPLACE_API_KEY}'

MCP client configuration

{
  "mcpServers": {
    "xy-marketplace": {
      "type": "http",
      "url": "https://planner-mcp.prod.xyai.beer/mcp",
      "headers": {
        "Authorization": "Bearer ${XY_MARKETPLACE_API_KEY}"
      }
    }
  }
}

Do not place the API key in a shared configuration file. ResolveXY_MARKETPLACE_API_KEYfrom an OS keychain, secret manager, or private process environment.

Capabilities

Tools are discovered from the live server.

Your client negotiates the current tool catalog and input schemas through MCPtools/liston connection. That live response—not a copied list on this page—is the source of truth.

Workflow Planner

Build, review, test, export, and explicitly promote reusable workflows.

Browser Studio

Develop browser steps in retained authoring sessions with scoped controls.

Analytics

Query governed metrics and author dashboard drafts for review.

Schedules

Inspect and operate recurring compiled-workflow schedules.

Run observability

Read safe execution phases without mutating the underlying Temporal run.

Runtime credentials

Manage secret-backed references without returning stored credential values.

Live reference

Current MCP tools and input schemas.

This catalog is read from the production MCP registry at request time and refreshed every minute. Tool additions and schema changes appear here after the MCP deployment without a website release.

The public tool catalog is temporarily unavailable. Connected MCP clients still discover the current authorized tool set directly throughtools/list.

Security model

The key defines the boundary.

The same organization-scoped Marketplace API key authenticates REST and MCP.
Keys are environment-bound; this public guide always uses production.
Tool availability is limited by the scopes attached to the key.
The bearer key belongs in a secret manager or OS keychain, never in a URL or source control.

Open the REST API reference