Build your own internal tool under 10 seats

TL;DR

• Below ten seats, per-seat builders are priced for a different customer. An agent can write the tool itself; what it needs is a backend, a login and a place to host it.
• With Manybases, one MCP connection lets Claude Code create the project, its tables, its users and its site.
• Who sees what is one access preset per table: espaces when each client sees only their own rows, espace_modere when members read and create but only the author or the space admin edits.
• Seats: 3 end users per app on Free, 1,000 on Builder.
• Price: $0 on Free (2 projects) · $14.99/month on Builder (20 projects).

What does an internal tool for a small team actually need?

An order tracker for a three-person shop, a lead list shared with an assistant, a client-facing status board for a freelancer: the shape is always the same. A few tables, a login for a handful of people, a rule about who may see and edit which rows, and a URL. The interface is the easy part now: an agent writes it in an afternoon. The parts that used to justify a builder — hosting, auth, permissions — are the parts the backend has to supply.

The builder market is priced for larger teams. Retool's Free plan covers "up to 5 users"; its Team plan is "$10/month" per builder and "$5/month" per internal user, billed monthly (retool.com/pricing, read 2026-09-12, reported). A comparison of eight builders reports Zoho Creator from "$8/user/month", Power Apps from "$20 per user/month" and ToolJet from "$19/builder/month" (zite.com, read 2026-09-12, reported — check each vendor's page before relying on it). These are fair prices for what they include. They are also the wrong shape for a team of six that just wants its own tool.

How do I build one with Claude Code and Manybases?

Connect the MCP once: add https://mcp.manybases.com as a custom connector, and a consent screen on the dashboard issues the key (connecting the MCP). Then, in one session:

Create a project "orders-desk". Tables: orders (client_id, status, amount, due_on),
notes (order_id, author_id, body). Set orders to the `espaces` preset and notes
to `espace_modere`. Invite maria@ and tom@ as end users. Build a single-page
site that lists orders by status, with a screen where a signed-in user creates
a space per client, and deploy it.

The agent calls create_project, create_table, set_table_preset, invite_user and deploy_site — five of the MCP's tools (tool list). The site goes live on manybases.online, and "a site can carry no code, no key and no binding" (data isolation): the page calls its project's API, with nothing to paste. Invitations are single-use links, valid 7 days, that you share yourself — "no e-mail is sent" (inviting users). If the code lives in a repository: install the Manybases GitHub App, link the repo, copy one workflow file, push (deploying from GitHub).

Spaces are the one part your agent does not set up alone. A space is born from a signed-in user of the app, who becomes its admin; the agent's key is refused on that call. Members are then added through the spaces API, by that admin or with your own keys, each addition confirmed in two steps, and joining a space takes no extra seat (spaces). No MCP tool covers spaces today: that is why the prompt asks for a screen in the app where people create their own.

Some steps stay with a human on purpose: opening a table to users or anon, deleting an end user, creating a secret key, exporting — 13 gestures in all (the human boundary). The agent builds; you keep the keys.

Try it: connect Claude Code to Manybases, then paste the prompt above.

Which preset for which table?

Internal tools are where two presets earn their keep.

Source: access presets. "Every table carries one preset that says who may list, read, create, update and delete its rows", and presets replace row-level security policies: "there are eight of them, they cannot be misconfigured, and the API applies them to every request." A business rule such as "orders over $5,000 need two approvals" is not a preset: your app displays the rule.

What does it cost for a team of six?

Sources: Manybases, pricing, read 2026-09-18; Retool, retool.com/pricing, read 2026-09-12, reported. Retool includes an app builder, integrations and AI credits that Manybases does not, so this compares shapes, not features. A second and a third internal tool on Builder cost nothing more, and egress is $0 on every plan.

What does Manybases not do for an internal tool?

• More than 1,000 end users per app, the most any plan allows: use Supabase, or a builder like Retool.
• Social login: people sign in with e-mail and password or a magic link, through the invitation. Not available today.
• Scheduled tasks, incoming webhooks, realtime. A tool that must react to a Stripe event or refresh live needs Supabase or Convex.
• A custom domain: the tool lives on manybases.online. Not available today.
• A drag-and-drop interface builder: the interface is code your agent writes. If nobody on the team wants code at all, use Glide or Softr.

Sources: seats, pricing, read 2026-09-18; the rest, limitations.

What happens when the team grows?

Up to 1,000 end users per app, the tool stays on Builder (pricing, read 2026-09-18). Past that, export from Settings → Export (a human gesture): dump.sql, your files and manifest.json. The export "keeps your table names and presets, so the mapping to another backend is mechanical" (export). If you downgrade instead, "apps beyond your new plan's limit become read-only — nothing is deleted, nothing is lost" (pricing).

Next

• What the MCP gives your agent
• Pricing, plan by plan
• The eight access presets, in the documentation

Your team's tool, written by your agent, hosted by us: connect Claude Code to Manybases.

Found an error on this page? Tell us at contact@manybases.com.