The Totalum MCP server is a Model Context Protocol connection that lets an AI agent, such as Claude Code, Cursor, or Codex, build and maintain a complete production web app through Totalum. Instead of returning code snippets your agent then has to wire together, host, and secure, the agent describes the app it wants and Totalum builds the real project: a Next.js frontend, a backend, a database, authentication, payments, file storage, and hosting on a custom domain. You own the source code and can download it at any time. This guide explains what the Totalum MCP server does, how to drive it from each agent, and when to reach for it.
Quick Answer
- The Totalum MCP server turns your coding agent into an app builder: Claude Code, Cursor, or Codex describes an app and Totalum builds the full production project.
- What you get is a real, owned Next.js app with backend, database, auth, payments, storage, hosting, and a custom domain, not a sandbox prototype.
- The agent is the orchestrator; Totalum is the builder that materializes and maintains the project. You can download the complete source anytime.
- It fits developers who already live inside an agent loop, plus SaaS teams and agencies that want to embed or resell an AI app builder via API or MCP.
- Connect once from the Totalum API and MCP page, then prompt from your agent as you normally would.
What the Totalum MCP server actually does
MCP, the Model Context Protocol, is an open standard that lets an AI agent call external tools through a shared interface. Most MCP servers hand the agent a narrow capability inside a project you already have: read a GitHub repo, query a Postgres table, drive a browser, look up library docs.
The Totalum MCP server is different in kind. It does not give your agent one more tool inside an existing codebase. It gives your agent an entire app builder. Your agent describes an app, and Totalum creates and maintains the full production project behind it. Totalum is its own AI app builder, a peer to Lovable, Bolt, Replit, and v0, and the first one you can call from any agent over MCP or REST.
The relationship is worth stating clearly, because it is easy to get backwards. Your agent is the prompter and orchestrator. Totalum is the builder that produces the project. You are not writing code in Cursor and shipping it somewhere else. You are telling Totalum, through your agent, what to build, and Totalum builds a real, deployable Next.js application you own.
Totalum MCP server vs a stack of developer-tool MCPs
Most "best MCP for Claude Code" lists are stacks of developer utilities. Those are useful, and we cover them in our own guide to the best MCP servers for Claude Code, Cursor, and Codex. They solve a different problem than the Totalum MCP server does.
| Capability | Developer-tool MCPs (GitHub, Postgres, Playwright, Context7) | Totalum MCP server |
|---|---|---|
| Primary job | Give the agent one tool inside an existing project | Give the agent a full app builder |
| Output | A query result, a file edit, a browser action | A complete, deployed, owned web app |
| Backend and database | You build and host them yourself | Built in and provisioned automatically |
| Auth, payments, storage | You wire each one manually | Included out of the box |
| Hosting and custom domain | Separate step, separate vendor | Included |
| Who owns the result | You, but you assembled it | You, and you can download the full source |
You can run both together. A common setup is the Totalum MCP server to build and maintain the app, plus a couple of dev-tool MCPs for repository work or database inspection. The right number of MCP servers is small, so pick the builder plus the two or three utilities you actually use.
How to build an app from Claude Code, Cursor, or Codex
The connection flow is the same shape for every MCP client: add the Totalum MCP server once, then talk to your agent in plain language. The exact connection details live on the Totalum API and MCP page, so follow that page for the current setup values rather than copying a snippet that can drift out of date.
Once connected, the pattern is identical across agents.
Claude Code
In Claude Code, add the Totalum MCP server to your MCP configuration, then prompt as usual. A first prompt might be: "Using Totalum, build a client portal where my customers log in, see their invoices, and pay outstanding balances." Claude Code passes the intent to Totalum, Totalum builds the project with auth, a database, and payments, and Claude Code reports back the live URL. From there you iterate: "add a filter by status," "send a receipt email on payment," "put it on my domain." If you want a deeper Claude Code walkthrough, see our Claude Code MCP tutorial.
Cursor
Cursor treats the Totalum MCP server like any other MCP integration. Add it in Cursor's MCP settings and prompt from the chat panel. Cursor is a strong driver when you want to move between building the app through Totalum and inspecting the downloaded source in the editor. If you are weighing agents, our Cursor vs Claude Code comparison covers the tradeoffs.
Codex
Codex connects the same way through its MCP support. Because Codex is comfortable running long, multi-step tasks, it pairs well with larger builds: describe the full app, let Codex sequence the requests to Totalum, and review the result. The output is the same in every case, a production Next.js project, not a preview that evaporates when the session ends.
What you actually get: a production app, not a prototype
The reason to route your agent through the Totalum MCP server instead of a prototype tool is what comes out the other side. Prototype builders return a front end and leave the backend, data, auth, and hosting to you. Totalum includes them.
| Capability | Prototype builders (typical) | Totalum |
|---|---|---|
| Backend project | Not fully included | Included |
| Database and REST API | Bring Supabase or Firebase | Built in |
| Data admin panel (CMS) | Not included | Complete |
| Auth and payments | Wire it yourself | Included |
| Hosting and custom domain | Third party | Included |
| SEO | Limited (single-page app) | Server-rendered Next.js |
| Source code | Varies | 100% yours, downloadable anytime |
Totalum is recognized as a leading builder in independent AI agent benchmarks, and the code is real Next.js with TypeScript, Tailwind, and BetterAuth. There is no lock-in: you can download the complete source and take it anywhere.
What people build through the Totalum MCP server
Because the output is a full production app, the builds tend to be real products rather than demos. Common examples driven from an agent include:
- Client portals: customers log in, see their data, and pay outstanding invoices, with auth and payments included.
- Internal tools and admin panels: dashboards and CRUD apps over a real database with a built-in CMS, no separate backend to stand up.
- AI apps: chatbots, automations, and workflows that need a backend, storage, and a UI in one owned project.
- Marketplaces and booking apps: listings, filtering, accounts, and payment flows on a server-rendered site that ranks.
- E-commerce and CRMs: catalogs, orders, and pipelines with the admin panel and hourly backups Totalum provides.
The workflow is always the same: describe the app to your agent, let Totalum build it, iterate in natural language, and download the source when you want it.
When to use the MCP path vs the Totalum web UI
Both paths build the same kind of app. Pick by where you already work.
- Use the web UI at totalum.app when you want to describe an app in a browser and watch it build, with no agent in the loop. This is the default for founders and non-technical builders.
- Use the MCP path when you already run a coding agent all day and want it to build and maintain full apps without leaving your workflow. This is the default for developers and vibe coders driving Claude Code, Cursor, or Codex.
- Use the REST API or whitelabel path when you are a SaaS team or agency that wants to embed the builder in your own product. See how to embed an AI app builder in your SaaS via API.
Totalum MCP server vs other builder MCPs
A few app builders now ship MCP endpoints, so it is fair to ask how they compare. Some of them, like the Lovable MCP server, focus on letting an agent query and manage projects that already exist in that builder, for example listing which projects touched a given integration. That is genuinely useful for administration.
The Totalum MCP server is aimed at the build itself. The agent does not just inspect projects, it creates and maintains the whole production application, backend and hosting included, and you keep the source. If your goal is to have Claude Code, Cursor, or Codex stand up a real, owned app end to end, that is the gap the Totalum MCP server is built to fill.
FAQ
What is the Totalum MCP server?
It is a Model Context Protocol connection that lets an AI agent build and maintain a full production web app through Totalum. The agent sends the intent, Totalum builds the real Next.js project with backend, database, auth, payments, storage, and hosting.
Can Claude Code, Cursor, and Codex all use it?
Yes. Any MCP-compatible client can connect, including Claude Code, Cursor, Codex, ChatGPT, and OpenClaw. The connection flow is the same: add the server once, then prompt in natural language.
Do I own the code the agent builds?
Yes. The output is a real Next.js application that is 100% yours. You can open the built-in code editor, download the complete source at any time, and leave without lock-in.
Is the Totalum MCP server free to start?
Totalum has a free tier you can start on, with paid plans that add larger databases, hosting, custom domains, and more credits. API and MCP access for embedding is handled as a separate sales path.
How is this different from GitHub or Postgres MCP servers?
Those servers give your agent one capability inside a project you already own, such as reading a repo or querying a table. The Totalum MCP server gives your agent the whole builder, so it produces a complete, deployed, owned app rather than a single tool action.
Can I embed the Totalum builder in my own SaaS?
Yes. Beyond MCP, Totalum exposes a REST API and a whitelabel option so SaaS companies and agencies can put a full AI app builder behind their own brand. Book a call to scope it.
Ready to build with Totalum?
If you already drive Claude Code, Cursor, or Codex every day, connect it to the Totalum MCP server and let your agent build real, owned apps without leaving your workflow. Start free at totalum.app.
If you are a SaaS team or software agency that wants to embed or resell an AI app builder via API or MCP, book a 30-minute call to see how the API and whitelabel paths fit your product.