Reports deployable regions, instance types, images and extensions, reads project resource limits, and updates organization details on request.
8actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro updates Xata organization settings like names and billing details directly in conversation. DevOps teams configure infrastructure details without logging into the dashboard.
Ayro fetches the current organization's details including plan, region, and settings. Support can quickly confirm a customer's account configuration when troubleshooting.
Ayro shows available AWS regions where new database branches can be deployed. Developers choose the best region for latency without consulting documentation.
Each card is one request a support team gets, and the Xata actions Ayro runs to close it.
Ayro reads the regions open to the organization, the instance types available there with their CPU, RAM, and pricing, and the Postgres images on offer, so a deployment choice is made against what the account actually supports.
Ayro checks which extensions can be enabled for a specific Postgres image before anyone builds against one, so a dependency on pgvector or similar is verified rather than assumed.
Ayro reads the default project resource limits for the organization - maximum instances, storage, allowed regions, branch count - so a capacity question is answered before a deploy hits the ceiling.
Ayro reports the organization's status, name, billing, and admin settings alongside the API keys registered to it, and applies a name change when one is asked for.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Xata actions it has and picks the ones a request needs.
Authorize the Xata account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Xata actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeXata · Ayro
What can you do in Xata without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Xata.
No. This toolkit is organization and infrastructure administration only: regions, instance types, Postgres images, extensions, project resource limits, API keys, and Update Organization. Nothing in it reads rows, runs SQL, or searches a table, so Ayro answers account and provisioning questions rather than data questions.
All 8 actions your agent can call on Xata, straight from the live MCP connection.
Retrieve detailed information about a specific organization by its ID.
Retrieve the default resource limits for projects in a specified organization.
Get available PostgreSQL extensions for a specific image.
Retrieve a list of all available postgres images for a specified organization and region.
Retrieve a list of all instance types for the specified organization and region.
Retrieve a list of API keys for a specific Xata organization.
Retrieve a list of all regions where new branches can be deployed for the specified organization.
Update information for an existing organization, such as its name.
Same connection, same setup. Pick the next one your team already uses.
Checks channel presence, publishes realtime and batch messages, sends push notifications, and maintains the Ably device registry.
Triggers a named browser test, reports its status, timing and errors, and lists what the account actually covers.
Reports what deployed and what is queued, summarises what a release contains, aborts a bad deployment, and stands new projects up against their servers.
Returns the SP-initiated SSO sign-on URL, lists company identifiers, and completes the SAML round trip for account access.
Issues credentials over OpenID4VC and DIDComm, raises verification requests, maintains credential templates, and manages DIDComm connections.
Checks API health, lists organization certificates and projects, and reads the signing policies the connected user can submit against.

Authorize the account and your agent has all 8 actions from the first conversation.
