XataWorks is a bus. Plug your web app in.

The picture

Think of XataWorks as a bus. Each web application that declares its operations through WebMCP plugs into it. An agent sits on the same bus and can work every application plugged in — your helpdesk, your order system, your shipping tracker — in one piece of work, in the person’s own signed-in session.

That changes what adding WebMCP to your application is worth. You are not building one integration. You are making your application one more device on a bus that already reaches the other applications your users have open.

Try it in a minute

Every hands-on article is built around an example hosted with the guide. Paste this into XataWorks’ address bar and ask the agent to greet someone:

You will be asked whether the agent may use the site’s tools:

What is in the guide

• The idea: what WebMCP is, how it compares to MCP, and the bus.
• Hands on: a hello world, a tool that changes things, and two applications answering one question.
• Permissions: every question and every answer, photographed, from allowing one call to giving each tenant of your service its own answers.
• Agents and skills: agents that orchestrate the bus and skills your application publishes.

Why the pictures matter

Every screenshot and recording in the guide is a frame of the running application, captured by a script, over a real agent turn. When you open the examples yourself you will see the same questions with the same words. If you ever do not, that is a bug in the guide, and the address at the foot of this page is the place to report it.