Xata

io.github.xataioPublished by GitHub account xataiov1.0.0Updated Oct 24, 2026

Xata MCP server lets AI agents interact with your Xata projects, and Postgres database branches.

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote Xata MCP server that lets an AI assistant work with your Xata projects and Postgres database branches.

What you can do
Interact with your Xata projects and their Postgres database branches from an assistant session. The manifest lists no individual tools, so the exact operations available are not documented here; the server is described only as letting agents interact with Xata projects and Postgres branches.
When to use it
Useful when your data lives in Xata or in Postgres branches managed through Xata and you want an assistant to work with those projects directly instead of copying data elsewhere.
Requirements
A remote endpoint at api.xata.tech over streamable HTTP. Authentication is required via OAuth or an API key sent in the Authorization header as a Bearer token. No local runtime or packages are needed.
Before you install
You must supply a Xata API key or OAuth token in the Authorization header; treat it as a secret. The manifest does not document which operations the tools perform, so confirm whether they can write, change or delete projects or branches before granting access.

Installation

In SourceWeft

  1. Open Xata in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.xataio%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "xata": {
      "type": "http",
      "url": "https://api.xata.tech/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.