An MCP database is a database your AI agent creates and uses through the Model Context Protocol. Connect Claude Code, Cursor, Codex or Copilot to the Codata IO MCP server at mcp.codata.io/mcp and sign in once. Your agent can then plan tables, save data, add login and email, and take the app live.
Your agent can write an app in an afternoon. Then the app needs somewhere to keep users, orders and files. If nobody sets that up before the conversation ends, the data sits in a local file and disappears with the laptop.
An MCP database fixes that. It hands your AI agent a real database it can create, change and use from the chat, over the Model Context Protocol.
This guide covers what MCP is, why a database for AI agents matters and how to connect your agent to Codata IO, step by step. It also covers safety and the other database MCP servers worth knowing.
What is MCP, in one minute
The Model Context Protocol (MCP) is an open standard that lets an AI agent call tools on another service. Think of it as a plug: the agent learns what a service can do, then asks it to do those things.
Here is a plain example. You tell Claude Code to "change the launch date to Friday" Claude Code calls a tool on the MCP server of your work management app. It finds the related task and updates the date.
An MCP server database setup is that same idea pointed at your data. Servers differ in how much sits behind them: a database only, or also the login, storage and hosting the app needs.
Why your agent needs a real database
Your agent needs a real database because its memory and local files don't last. Each chat starts fresh, and a prototype often keeps data in a JSON file or the browser.
That works on your machine and nowhere else. A real database gives the app three things a file can't:
- It outlives the conversation. Users, orders and messages stay put after the agent is done.
- Many people can use it at once. Two signups in the same second both get saved.
- It can grow. The agent can add a field or a table next week without losing what's there.
That's the gap between a demo and an app people use. MCP closes it without you copying connection strings around.
What an MCP database gives your agent
An MCP database lets your agent set up and change your data from the chat, without you opening a console. On the Codata IO database, your agent can:
- Plan tables from a plain request, such as "a signups table with name, email and date."
- Read and write rows while the app runs.
- Change the schema as the app grows. The database is auto-planned and auto-migrated, so a new field doesn't mean a manual migration.
- Try changes on a branch and roll back to an earlier version if one goes wrong.
A database is one part of an app. On Codata IO, the same connection also covers login, file storage, email, hosting and custom domains, so the agent can finish the whole thing. You own the code and the data.
Codata IO doesn't process payments. If your app takes money, connect a payment provider such as Stripe.
Set it up with Codata IO, step by step
You connect your agent to the Codata IO MCP server once, sign in, and then ask for what you want built.
- Create a free Codata IO account. The Free plan gives you 2 live apps and $5 of usage one time, with no card.
- Add the MCP server to your agent. The address is
https://mcp.codata.io/mcp. Use the snippet for your agent below, or runnpx @codata-io/cli init. It finds your editor and writes the config for you. - Sign in. The first time your agent uses the server, an OAuth login opens in your browser. Approve it and you're connected.
- Point your agent at the Codata skill. Paste: "I'm using Codata as my backend platform. Fetch https://codata.io/skill.md and follow it."
- Ask for something real. For example: "Build a waitlist app with a signups table and a confirmation email."
- Review the plan, then go live. Codata IO designs the backend and returns a plan showing the changes, the risk and anything that needs your approval. Once it's applied, the agent builds the app and publishes it on a free Codata domain, with email sending from that domain.
Connect Claude Code
Run this in your terminal, then run /mcp inside Claude Code to finish signing in:
claude mcp add --transport http codata https://mcp.codata.io/mcp
To share the setup with your team, add the server to .mcp.json in the project root instead:
{
"mcpServers": {
"codata": { "url": "https://mcp.codata.io/mcp" }
}
}
Connect Cursor
Create .cursor/mcp.json in your project. The sign-in opens the first time Cursor uses the server.
{
"mcpServers": {
"codata": { "type": "http", "url": "https://mcp.codata.io/mcp" }
}
}
Connect Codex
Add the server to ~/.codex/config.toml:
[mcp_servers.codata]
url = "https://mcp.codata.io/mcp"
Copilot in VS Code, Windsurf and Claude Desktop
- Copilot in VS Code: add the same address to
.vscode/mcp.json, or install the Codata for VS Code extension and use@codatain chat. - Windsurf: add it to
~/.codeium/windsurf/mcp_config.jsonasserverUrl. - Claude Desktop: open Settings, then Connectors, then Add custom connector, and paste the address.
Full steps for every client are in the MCP setup docs. Bringing your own agent uses no App Builder credits. What the live app consumes, such as database storage, files and emails, counts as usage.
Agents build the code. Codata IO is where it ships.
Connect your agent, free