Compatible with every major AI agent and IDE
What is the Xata MCP Server?
Connect your Xata account to any AI agent to manage your serverless data infrastructure through natural conversation.
What you can do
- Organization Management — List, create, and update organizations, and manage member invitations and roles.
- Project Control — Create and list projects within your organizations and monitor resource limits and quotas.
- Database Operations — Manage branches, retrieve credentials, and execute SQL queries directly against your data.
- Developer Workflow — Handle API keys and GitHub integrations to streamline your deployment pipeline and repository mapping.
How it works
- Subscribe to this server
- Enter your Xata API Key
- Start managing your databases from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Backend Developers — quickly spin up projects and branches without leaving the terminal or IDE.
- Data Engineers — query data and inspect organization structures via SQL directly through the agent.
- DevOps Managers — automate member access, invite collaborators, and manage API key rotations.
Built-in capabilities (28)
Cancel a pending organization invitation
Create a new database branch
Create an API key for the organization
Create a new Xata organization
Create a new project in an organization
Create a new user API key
Bulk delete user API keys by ID
Execute single or batch SQL queries over HTTP
Retrieve database username and password for a branch
Query observability data (CPU, Memory, Disk, etc.) for a branch
Retrieve the current GitHub repository mapping for a branch
Get detailed information about a specific organization
Get resource limits for projects in an organization
Link a GitHub App installation to an organization
Invite a user to an organization via email
List all branches in a project
List available PostgreSQL versions/images
List organization-scoped API keys
List pending or expired invitations for an organization
List members of an organization
List all organizations the authenticated user belongs to
List all projects within an organization
List available regions for project deployment
List API keys for the authenticated user
Map a GitHub repository to a branch
Remove a member from an organization
Trigger a password rotation for a branch
Update organization information
Why Cursor?
Cursor's Agent mode turns Xata into an in-editor superpower. Ask Cursor to generate code using live data from Xata and it fetches, processes, and writes. all in a single agentic loop. 28 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Xata in Cursor
Xata and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Xata to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Xata in Cursor
The Xata MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 28 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Xata for Cursor
Every tool call from Cursor to the Xata MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all organizations I have access to?
Yes! Use the list_organizations tool to retrieve all Xata organizations available to your current API key.
How do I start a new project in a specific organization?
Simply use the create_project action providing the organization_id and the desired name for your new project.
Can I run raw SQL queries through the agent?
Yes, the execute_sql tool allows you to run SQL queries directly against your database branches for advanced data manipulation and analysis.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Flowise
7 toolsManage low-code AI workflows via Flowise — run predictions, track chatflows and agentflows, handle tools, and audit execution history directly from any AI agent.

TED EU
6 toolsSearch EU public procurement tenders via TED — find contracts by country, sector, or value range from any AI agent.

Obsidian Publish
5 toolsEmpower your AI to read your public or private Obsidian Publish sites. Index files, crawl navigation trees, and retrieve deep markdown knowledge.

Campaign Monitor
10 toolsManage email marketing via Campaign Monitor — track campaigns, manage subscribers, and monitor performance directly from any AI agent.
