Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Xata (BYOK) icon

Xata (BYOK)

Read your Xata organizations, projects, Postgres branches, regions, limits and branch logs with your own API key

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderXataunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Xata organizations do I belong to?
Tools called
list_organizations
Is my Xata organization in good standing?
Tools called
get_organization
What are my Xata plan limits?
Tools called
get_organization_limits
Which regions can I deploy Xata branches in?
Tools called
list_regions
What Xata projects do I have?
Tools called
list_projects
Show the settings of my Xata project
Tools called
get_project

About

Xata (BYOK) lets an AI assistant read your own Xata data through the Xata API with a key you supply (Xata API key). Read-only: 9 tools (list_organizations, get_organization, get_organization_limits, list_regions, list_projects, get_project, list_branches, get_branch, get_branch_logs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.xata.tech. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Xata. Xata and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Xata API (api.xata.tech) with a BYOK key; documentation: https://xata.io/docs/api-reference. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List organizationsList the Xata organizations the key can see with ID, name and account status (enabled or disabled, billing status, usage tier).
  • Get organizationGet one Xata organization: name and status including billing status and usage tier.
  • Get organization limitsGet the effective limits of a Xata organization: maximum projects, branches, instances per branch, storage per branch and creation rates.
  • List regionsList the regions where new Xata branches can be deployed for an organization, with cloud provider and whether public access and backups are available.
  • List projectsList the projects of a Xata organization with name, creation and update time and scale-to-zero and IP filtering settings.
  • Get projectGet one Xata project: name, timestamps, scale-to-zero settings and IP filtering.
  • List branchesList the database branches of a Xata project with name, description, parent branch, region and public access and backup flags.
  • Get branchGet one Xata branch: lifecycle state, health, instance counts, region, instance type, storage, replicas, scale-to-zero and backup settings.
  • Get branch logsGet PostgreSQL log entries of a Xata branch between two times, newest page first, with level, process and message.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-xata.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-xata.connectorbay.com/mcp
RESTPOST https://byok-xata.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-xata.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Xata API key in the X-Upstream-Key header (get one at xata.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Xata connector: questions and answers

What is the Xata connector?

Xata (BYOK) lets an AI assistant read your own Xata data through the Xata API with a key you supply (Xata API key). It is a hosted MCP server with 9 tools such as List organizations, Get organization, Get organization limits, List regions, List projects, Get project, published by Unify Dynamics LLC. It is independent and not affiliated with Xata.

How do I connect Xata to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-xata.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-xata.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-xata.json.

Do I need a Xata account or API key?

Yes: this is a bring-your-own-key connector. Create a Xata API key at https://xata.io/docs/platform/api-key and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Xata read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Xata connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Navitia Network Data (BYOK)

List the networks, routes, stop areas, stop points, trips, modes, operators, datasets, contributors and disruptions of a Navitia public transport region with your own Navitia token

Live · MCP + REST12 tools

Nebius Token Factory (BYOK)

Read your Nebius Token Factory models, uploaded files and fine-tuning jobs, events and checkpoints with your own API key

Live · MCP + REST8 tools

Neon (BYOK)

Read your Neon Postgres projects, branches, databases, compute endpoints and operations with BYOK

Live · MCP + REST11 tools

Neon Auth (BYOK)

Read the Neon Auth setup of your Neon branches: provider integration, trusted domains, OAuth providers, email and password rules, plugins, webhooks and OAuth clients with your own Neon API key

Live · MCP + REST11 tools

Neon Consumption (BYOK)

Read consumption history per project and per branch, the organization spending limit and branch counts of your Neon account with your own Neon API key

Live · MCP + REST5 tools

Neon Project Admin (BYOK)

Read the snapshots, backup schedules, JWKS providers, VPC endpoints, API key metadata, roles and masking rules of your Neon projects with your own Neon API key

Live · MCP + REST9 tools

Documentation

Back to top

Xata (BYOK) — connector documentation

  • MCP endpoint: https://byok-xata.connectorbay.com/mcp
  • REST API: POST https://byok-xata.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-xata.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Xata Xata API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-xata.connectorbay.com/health · Tool schemas: https://byok-xata.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-xata · agent@connectorbay.com

What Xata (BYOK) is for

Xata (BYOK) lets an AI assistant read your own Xata data through the Xata API with a key you supply (Xata API key). Read-only: 9 tools (list_organizations, get_organization, get_organization_limits, list_regions, list_projects, get_project, list_branches, get_branch, get_branch_logs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.xata.tech. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Xata. Xata and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Xata organizations do I belong to?"
  • "Is my Xata organization in good standing?"
  • "What are my Xata plan limits?"
  • "Which regions can I deploy Xata branches in?"
  • "What Xata projects do I have?"
  • "Show the settings of my Xata project"

What it does

  • list_organizations: List the Xata organizations the key can see with ID, name and account status (enabled or disabled, billing status, usage tier).
  • get_organization: Get one Xata organization: name and status including billing status and usage tier.
  • get_organization_limits: Get the effective limits of a Xata organization: maximum projects, branches, instances per branch, storage per branch and creation rates.
  • list_regions: List the regions where new Xata branches can be deployed for an organization, with cloud provider and whether public access and backups are available.
  • list_projects: List the projects of a Xata organization with name, creation and update time and scale-to-zero and IP filtering settings.
  • get_project: Get one Xata project: name, timestamps, scale-to-zero settings and IP filtering.
  • list_branches: List the database branches of a Xata project with name, description, parent branch, region and public access and backup flags.
  • get_branch: Get one Xata branch: lifecycle state, health, instance counts, region, instance type, storage, replicas, scale-to-zero and backup settings. Credentials are not read.
  • get_branch_logs: Get PostgreSQL log entries of a Xata branch between two times, newest page first, with level, process and message. Needs the logs:read scope.

BYOK key

You bring your own Xata Xata API key (https://xata.io/docs/platform/api-key). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.xata.tech over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

This covers the current Xata (Postgres) platform API at api.xata.tech. It does not run SQL and does not return branch credentials. The key's scopes decide what it can read.

Data sources

Live from the Xata API (api.xata.tech) with a BYOK key; documentation: https://xata.io/docs/api-reference. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Xata. Xata and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Xata account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Xata (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Xata (BYOK) is. Xata (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Xata data: Read your Xata organizations, projects, Postgres branches, regions, limits and branch logs with your own API key. You bring your own Xata Xata API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Xata call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.xata.tech, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Xata rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Xata receives. The request we make on your behalf, including the key and the arguments, under Xata's own terms and privacy policy. Xata acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Xata gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Xata data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Xata (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Xata at any time to end all access.

Children. Xata (BYOK) is a general-audience service operated by the adult using the assistant, under Xata's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Xata (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Xata (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Xata (BYOK) provides: Read your Xata organizations, projects, Postgres branches, regions, limits and branch logs with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Xata credentials and only access data you are allowed to access. Xata's terms apply to your use of Xata; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Xata. Xata and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Xata returns, lightly trimmed; it may be incomplete, delayed or changed by Xata. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Xata account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Xata's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Xata may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Xata key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Xata takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-xata

Xata (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Xata (BYOK) never asks for them.

Get Xata (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Xata Xata API key. Create one at https://xata.io/docs/platform/api-key, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Xata. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Xata.