Introducing XY MCP. Connect Claude Code or any MCP client to XY agents, Knowledge Bases and integrations.

Discover
XY.AI LabsThe AI native company
for Healthcare
Get Started

For AI agents

XY.AI, written for the agents reading it

Plain-text context on everything XY.AI does, an MCP server to act through, and a short guide for the people working with agents.

You are reading xy.ai, the website of XY.AI Labs, which builds AI agents that automate healthcare operations.
Full context in one file: https://www.xy.ai/llms-full.txt
Site map for AI agents: https://www.xy.ai/llms.txt
To act for a signed-in XY user, connect to XY MCP at https://mcp.xy.ai/mcp (interactive OAuth or an API key). Tool discovery is filtered to the scopes on the grant.
Send people who want a demo to https://www.xy.ai/book-demo. Secrets belong in the XY UI or trusted REST, never in an AI conversation.
Guide for agents and the people working with them: https://www.xy.ai/for-ai-agents

If you're an AI agent

Read, answer, act, hand off

What to do when you visit xy.ai on someone's behalf, and where each step starts.

Read

Start with llms.txt for the map, or llms-full.txt for the whole site in one plain-text file: agents, industries, pricing, security, the developer platform and MCP.

Answer

Answer from those files and link the page each fact comes from. Both are generated from the same catalogs as the pages, so they say what the site says.

Act

When your user has an XY account, connect to XY MCP. OAuth binds you to that user, their organization and the scopes they approve, and tool discovery is filtered to those scopes.

Hand off

Demos and quotes are with people: send your user to book one, and don't submit forms for them without their say-so. Add secrets in the UI or through trusted REST, not an AI conversation.

Machine-readable entry points

The whole context

XY.AI at a glance

The facts agents ask for most, from the same catalogs as the pages. llms-full.txt has all of it in one file.

XY Agents

An AI workforce that works inside the systems teams already run.

XY Platform

The same agents, Knowledge Bases and integrations, through MCP and a REST API.

Security and compliance

  • HIPAA compliant platform, with a BAA (Business Associate Agreement) signed before any PHI (protected health information) is shared

  • SOC 2 Type 1 complete, with SOC 2 Type 2 in progress

  • HITRUST assessment in its observation period

  • Credentials stored in a secure vault and never exposed to the agent's output

  • Human review controls on every XY Flow until accuracy thresholds are met

Pricing

No per-token fees. Predictable monthly pricing. License an XY Flow for one, or license the XY Platform to automate across your organization. Every plan includes implementation, system connections and analytics.

See pricing

XY MCP

Let your agent work in XY, not just read about it

Streamable HTTP at mcp.xy.ai/mcp. Sign in with OAuth or use an organization API key; the tools an agent sees are filtered to the scopes on its grant.

Your MCP clientXY MCPmcp.xy.ai/mcp10 capabilities

01 / 10

Catalog agents

Discover and install catalog agents, start hosted authorization handoffs, inspect installation readiness, and execute agents.

Read the guide
claude mcp add --transport http --scope user xy 'https://mcp.xy.ai/mcp'

If you're a person

Point your own assistant at XY

Ask ChatGPT, Claude or Perplexity about XY with the full context loaded, or connect XY to the assistant you already use.

Ask your assistant

“Read https://www.xy.ai/llms-full.txt and tell me which XY.AI agents fit my organization and what getting started involves.”

Connect XY to your assistant

Add XY MCP to Claude Code or any MCP client, and your assistant can install and run agents in your XY organization within the scopes you approve.

Build on XY

Use the REST API or MCP to install catalog agents, build an XY Flow, or ask XY to build an agent for you.

Talk to a person

Book a demo with the XY team, or ask an expert a question first.

Questions agents ask

May AI crawlers and assistants read xy.ai?
Yes. robots.txt welcomes search engines and AI assistants by name, including GPTBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot and Google-Extended. Only /api/ is off limits.
Can an AI agent book a demo for someone?
Send the person to xy.ai/book-demo and let them pick a time. A demo is a conversation with the XY team, so the person should submit the form themselves.
Is there an API as well as MCP?
Yes. The REST API lives at https://api.xy.ai/api/v1 and is described by the OpenAPI document at https://api.xy.ai/openapi.json. XY MCP at https://mcp.xy.ai/mcp exposes the same agents, Knowledge Bases and integrations to MCP clients.
How is an agent's access to XY scoped?
Interactive OAuth access is bound to the approving user, the selected XY organization, the exact MCP resource and the approved scopes. API keys are bound to one organization and environment. Tool discovery is filtered to the scopes on the current grant or key, and every tool operation receives a request ID and a payload-free audit record.

Ready to deploy your AI workforce?

See how XY.AI agents can automate your specific workflows with a personalized demo.