You already work with AI agents. AdminForth is the admin they run your business through: customers, orders, jobs, stock and invoices in your own database, built by your coding agent, used by you and your team through Claude Code, Codex or any agent that speaks MCP. The panel is one way in; your agent is another. Screens are there when you want to look.

_{Maya’s agent works on her company’s app through MCP, with her permissions. Northstar Services and its data are made up.}

1. Your data stays yours, and stays patched. Records live in your own database on your server. Agents get in through one locked door: sign-in, a separate revocable key per agent, two-factor and passkeys for people. The security parts come from AdminForth, one framework our team maintains; updating is a version bump your agent runs.
2. Your team and their agents work inside your rules. Each person, and each of their agents, sees and changes only what their role allows. The server checks every request. The audit log names the person and the agent for every change.
3. Screens, optional. Ask your agent for the day’s work. Open a screen or a dashboard when you want to see it all.

_{Who changed what, when, through which agent, and what it was before.}

8 of the 10 biggest months for software vulnerabilities ever recorded happened in 2026. One in five of all vulnerabilities ever registered were published this year, and the year isn’t over (monthly data). Exploitation in the wild nearly doubled. An app your agent generated last month, with hundreds of packages nobody updates, sits right in that path. AdminForth, one framework maintained by our team, doesn’t.

1. Install Claude Code or Codex and sign in.
2. Create a folder for the project, for example my-business, and open the agent in it.
3. Paste the build instructions below. Change the lines under MY BUSINESS BRIEF to your own process first.

The agent builds the first part with sample data, runs the app, connects itself to it through MCP and shows you one operation end to end. From then on, you talk to your business.

Help me build a small business application with AdminForth. Work with me in
plain language. I don't have a developer: tell me exactly what to do myself,
step by step.

MY BUSINESS BRIEF
BUSINESS_PROCESS: Customer requests for my maintenance business.
CURRENT_PROBLEM: We send quotes and forget to follow up.
TEAM_ACCESS: Me and two managers. Each manager handles their own requests.
CURRENT_DATA: A spreadsheet. Start this example with synthetic data.

WHAT I WANT
A web app on AdminForth that my agent and my team's agents work with through
MCP, with sign-in, permissions and an audit log. I will mostly talk to it
through my agent; screens are for checking. Keep the first version small and
ready for more parts later (orders, jobs, stock, invoices).

START HERE
Read https://devforth.io/admin/api/af-start/business/ first, then
https://adminforth.dev/docs/tutorial/gettingStarted/ and
https://adminforth.dev/llms.txt. Use AdminForth as the framework: reuse
its screens, forms, filters and access rules, don't build a separate stack.
Use pnpm and Node.js 24. For a new local example use SQLite, the documented
create-app flow and Prisma migrations. Read the generated AGENTS.md, CLAUDE.md
and skills before changing anything. If something can't run here, tell me what
I must do instead of pretending it works.

Show me a short plain-language outline (records, roles, the first operation)
and ask only about decisions that change the data or the access rules.

BUILD
1. Records and relationships for my process, named so my team understands
   them, with a small set of fictional sample records.
2. Access rules on the server: I manage everything; every other person works
   only with what their role allows, including direct record requests, lists
   and relationships. A hidden button is not an access rule.
3. The MCP plugin (https://adminforth.dev/docs/tutorial/Plugins/mcp/) so I can
   connect my agent, and the Audit Log plugin
   (https://adminforth.dev/docs/tutorial/Plugins/audit-log/) with its
   executed-by column, so every change names the person and the agent.
4. No production data, emails or payments in this first version.

SHOW ME
Run the app and give me the local address and sign-in. Connect my agent with
the command from the Agents settings page, then do one operation through the
agent: find a record that needs attention, add its next action, and show me the
audit log entry. Show one action my agent is allowed and one a teammate's agent
would be refused. Say which checks you actually performed.

Write five prompts for my daily work with this app, in the words of my process.
Explain where the code and data are, how to reopen the app tomorrow, how to
update AdminForth and its plugins later, and what remains before my team uses
it: hosting, real data, backups, access review.

Prompts for the first day, with the example above:

• What needs my attention today?
• Which follow-ups are overdue, and whose?
• Add a request from Harbor Café: office maintenance quote. Owner Maya, next action: send the quote by Friday.
• Which invoices are unpaid for more than 30 days?

_{When you want to look: the overview of the whole business, built with the dashboard plugin.}

⭐ Star AdminForth to find it again when your agents need an admin to work in.

AdminForth is a TypeScript and Vue 3 framework for back-office and business applications. Declare resources over your database and get list, show, create and edit screens with filters, validation and access control, plus the same resources as MCP tools for agents. Everything else is code you own:

• Data sources: Postgres, MySQL, SQLite, MongoDB, ClickHouse.
• Agents: the MCP server plugin with OAuth 2.1 sign-in or per-user revocable secrets, every call under the user’s permissions, validation and hooks; the in-app agent; resources and endpoints you can hide from agents; audit log with agent attribution.
• Security plugins: TOTP and passkeys, OAuth SSO, user sessions with revoke, login captcha, signed password-reset tokens.
• Extend in code: hooks, custom actions, Express endpoints, Vue components injected into any part of the page, custom pages and the AFCL component library, styled with Tailwind.
• More plugins: import and export (CSV, XLSX), uploads to S3, i18n, rich editor, background jobs, dashboards and more.
• Made for coding agents: generated apps ship AGENTS.md, CLAUDE.md and skills; the docs publish llms.txt.

Hello world in 5 minutes · Live demo · Tutorial · YouTube: an agentic admin panel in minutes

AdminForth supports Node.js 22.12+, 24, and 26. Node.js 20 and 21 are no longer supported. We recommend Node.js 24 LTS for production.

Provide your database URL with --db, or enter it when the CLI asks Please specify the database URL to use:

pnpm dlx adminforth@latest create-app --app-name myadmin --db "postgresql://user:password@localhost:5432/dbname"
cd myadmin

The CLI inspects the database. When it already has tables, AdminForth connects to it without generating Prisma migrations, and the generated project README includes the SQL for the required adminuser table, to add with your own migration tool. When the database is empty, you can let AdminForth manage its schema with Prisma migrations.

Then generate AdminForth resource files from your existing tables:

pnpm exec adminforth resource

Omit --db, or accept the default sqlite://.db.sqlite value in the interactive prompt, and choose Prisma migrations:

pnpm dlx adminforth@latest create-app --app-name myadmin
cd myadmin
pnpm makemigration --name init && pnpm migrate:local
pnpm dev

Please follow getting started for the full guide.

Follow this section only if you want to make changes to the AdminForth framework or develop a plugin.

The most convenient way to add new features or fixes is to use dev-demo. It imports the repository source code and plugins, so you can edit them and see changes on the fly.

• Node.js 22.12+, 24, or 26 (Node.js 20 and 21 are not supported)
• Docker
• pnpm
• Taskfile

To run dev demo:

cd dev-demo

pnpm setup-dev-demo
pnpm migrate:all

pnpm start

Open ./migrations folder. There is prisma migration folder for the sqlite, postgres and mysql and clickhouse_migrations folder for the clickhouse:

To make migration add to the .prisma file in folder with database you need and add new tables or columns. Then run:

pnpm makemigration:sqlite -- --name init

and

pnpm migrate:sqlite

to apply migration

use :sqlite, :mysql or :postgres for you case

In order to make migration for the clickhouse, go to the ./migrations/clickhouse_migrations folder and add migration file to the folder.

Then run

pnpm migrate:clickhouse

to apply the migration.

Make sure you have not adminforth globally installed. If you have it, remove it:

pnpm uninstall -g adminforth

Then, in the root of the project, run once:

cd adminforth/adminforth
pnpm build
pnpm link

Then, go to testing app, e.g. created with CLI, and use next command:

npx -g adminforth <your command under development>

This will always run latest version of adminforth package.

Book a free 30-minute consultation about whether an admin built on AdminForth is a good fit for your business and what a useful first version could look like. The consultation is free; implementation and hosting are separate.