Xata MCP server

What the model can do

Xata (the Postgres platform with branching): organizations, projects, branches with their health, instances, region, size and scale-to-zero, branch metrics (CPU, memory, disk, connections, IOPS, latency, replication lag) over a window, backups with their restore window, and limits; when you ask, can create, rename or delete a project, create a child branch, rename, describe, hibernate, wake or resize a branch, delete a branch, restore a branch from a backup into a new branch, and invite a member.

Reads

• xata_list_organizationsThe Xata organizations this key sees, with id, name, whether enabled, billing status (ok, no_payment_method, invoice_overdue) and usage tier.
• xata_list_projectsProjects in a Xata organization: id, name, created and updated dates, and whether scale-to-zero is on for base and child branches.
• xata_list_branchesBranches of a Xata project: id, name, description, parent branch, region, created and updated dates, public access and whether backups are available.
• xata_get_branchOne Xata branch in detail: health (healthy, transient, fault, hibernated), instances ready, region, instance type, storage, replicas…
• xata_branch_metricsMetrics for one Xata branch over a window (default the last 24 hours, at most 30 days): any of cpu, memory, disk, connections_active…
• xata_list_backupsBackups in a Xata project: per branch, the earliest and latest point in time it can be restored to.
• xata_get_limitsA Xata organization's resource limits: maximum projects, project creation rate, branches and the per-project defaults.

Acts, when you ask

These change something in Xata. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• xata_create_projectCreates an empty project in a Xata organization.
• xata_rename_projectRenames one Xata project.
• xata_delete_projectPermanently deletes one Xata project with all of its branches and databases and their data.
• xata_create_branchCreates a child branch of an existing Xata branch (it inherits the parent's configuration and a copy of its data).
• xata_update_branch_detailsRenames a Xata branch or changes its description (an empty description clears it).
• xata_set_branch_hibernationHibernates a Xata branch (hibernate true: it goes offline and every connection to it fails until woken) or wakes it (false).
• xata_resize_branchChanges a Xata branch's replicas (0 to 4), storage in GiB or instance type.
• xata_delete_branchPermanently deletes one Xata branch and all of its data.
• xata_restore_branchRestores a Xata branch's backup into a NEW branch, at target_time (inside the window xata_list_backups shows) or at the latest point.
• xata_invite_memberInvites one person by email to the Xata organization as admin or editor.

Connect it

First connect Xata on Dashboard → Connections, then add Memtro to your client once. The Xata tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Xata connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which branches are not healthy right now?
• › What was the main branch's replication lag over the last day?
• › How far back can the production branch be restored?
• › What is our organisation's project limit?
• › Hibernate the preview branch.

Questions

Is this an official Xata MCP server?

No. It is Memtro's MCP server with Memtro's Xata connector behind it: the connector reads Xata through its API with the credentials you connect on Dashboard → Connections, and Xata publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Xata?

Only when you ask, and only what it has been granted: create a project; rename a project; delete a project and all its branches; create a child branch from an existing branch; rename or describe a branch; hibernate or wake a branch; resize a branch (replicas, storage, instance type); delete a branch; restore a branch from backup into a new branch; invite someone to the organization. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server