Skip to content
Back to search

adminforth

Admin panels for humans and AI agents. Let agents search, update, and act on your data through built-in chat or MCP, with the same permissions as your team. Open-source and self-hosted.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/devforth/adminforth with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/devforth/adminforth'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/devforth--adminforth/badge.svg)](/listings/devforth--adminforth)

HTML

<a href="/listings/devforth--adminforth"><img src="/api/listings/devforth--adminforth/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 270 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <a href="https://adminforth.dev"><img src="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/logo.svg" width="64" height="64" alt="AdminForth"></a>
  3. # AdminForth — agent-first business admin
  4. **The back office your coding agent builds and your agents run. Your data, your server, your rules. A change history that names the agent.**
  5. [Website](https://adminforth.dev) · [Start with your agent](#start-with-your-agent) · [Documentation](https://adminforth.dev/docs/tutorial/gettingStarted/) · [For developers](#for-developers)
  6. </div>
  7. <img width="1806" height="985" alt="adminforth-agent-demo" src="https://github.com/user-attachments/assets/acc1a1b2-52c3-408a-a71d-14b0eeb5c149" />
  8. 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.
  9. <picture>
  10. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/readme/business-agent-chat-dark.png">
  11. <img src="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/readme/business-agent-chat-light.png" width="100%" alt="An agent connected to an example business app through MCP: asked which follow-ups are overdue, it lists two requests, then updates the next action of REQ-1042 on the owner's request.">
  12. </picture>
  13. <p align="center"><sub>Maya’s agent works on her company’s app through MCP, with her permissions. Northstar Services and its data are made up.</sub></p>
  14. <p align="center">
  15. <a href="https://www.npmjs.com/package/adminforth"><img src="https://img.shields.io/npm/dw/adminforth" alt="npm downloads"></a>
  16. <a href="https://github.com/devforth/adminforth/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-green" alt="MIT license"></a>
  17. <a href="https://github.com/devforth/adminforth/stargazers"><img src="https://img.shields.io/github/stars/devforth/adminforth?style=flat" alt="GitHub stars"></a>
  18. <a href="http://tluma.ai/ask-ai/devforth/adminforth"><img src="http://tluma.ai/badge" alt="Ask AI"></a>
  19. </p>
  20. ## What it gives you
  21. 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.
  22. 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.
  23. 3. **Screens, optional.** Ask your agent for the day’s work. Open a screen or a dashboard when you want to see it all.
  24. <picture>
  25. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/readme/business-audit-dark.png">
  26. <img src="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/readme/business-audit-light.png" width="100%" alt="The audit log of the example app: Maya through Codex updated REQ-1042, Tom created a follow-up in the browser, Priya through Claude Code changed a status. Each row shows the old and the new value.">
  27. </picture>
  28. <p align="center"><sub>Who changed what, when, through which agent, and what it was before.</sub></p>
  29. > **8 of the 10 biggest months for software vulnerabilities ever recorded happened in 2026.** [One in five of all vulnerabilities ever registered](https://cvetodo.com/cve-statistics) were published this year, and the year isn’t over ([monthly data](https://craci.com/resources/CVE-publication-trends)). Exploitation in the wild [nearly doubled](https://cloud.google.com/blog/topics/threat-intelligence/vulnerability-discovery-and-exploitation-trends-in-the-ai-era). 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.
  30. ## Start with your agent
  31. 1. Install [Claude Code](https://code.claude.com/docs/en/desktop-quickstart) or [Codex](https://learn.chatgpt.com/docs/quickstart) and sign in.
  32. 2. Create a folder for the project, for example `my-business`, and open the agent in it.
  33. 3. Paste the build instructions below. Change the lines under `MY BUSINESS BRIEF` to your own process first.
  34. 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.
  35. <details>
  36. <summary><b>Build instructions for your coding agent</b></summary>
  37. ```text
  38. Help me build a small business application with AdminForth. Work with me in
  39. plain language. I don't have a developer: tell me exactly what to do myself,
  40. step by step.
  41. MY BUSINESS BRIEF
  42. BUSINESS_PROCESS: Customer requests for my maintenance business.
  43. CURRENT_PROBLEM: We send quotes and forget to follow up.
  44. TEAM_ACCESS: Me and two managers. Each manager handles their own requests.
  45. CURRENT_DATA: A spreadsheet. Start this example with synthetic data.
  46. WHAT I WANT
  47. A web app on AdminForth that my agent and my team's agents work with through
  48. MCP, with sign-in, permissions and an audit log. I will mostly talk to it
  49. through my agent; screens are for checking. Keep the first version small and
  50. ready for more parts later (orders, jobs, stock, invoices).
  51. START HERE
  52. Read https://devforth.io/admin/api/af-start/business/ first, then
  53. https://adminforth.dev/docs/tutorial/gettingStarted/ and
  54. https://adminforth.dev/llms.txt. Use AdminForth as the framework: reuse
  55. its screens, forms, filters and access rules, don't build a separate stack.
  56. Use pnpm and Node.js 24. For a new local example use SQLite, the documented
  57. create-app flow and Prisma migrations. Read the generated AGENTS.md, CLAUDE.md
  58. and skills before changing anything. If something can't run here, tell me what
  59. I must do instead of pretending it works.
  60. Show me a short plain-language outline (records, roles, the first operation)
  61. and ask only about decisions that change the data or the access rules.
  62. BUILD
  63. 1. Records and relationships for my process, named so my team understands
  64. them, with a small set of fictional sample records.
  65. 2. Access rules on the server: I manage everything; every other person works
  66. only with what their role allows, including direct record requests, lists
  67. and relationships. A hidden button is not an access rule.
  68. 3. The MCP plugin (https://adminforth.dev/docs/tutorial/Plugins/mcp/) so I can
  69. connect my agent, and the Audit Log plugin
  70. (https://adminforth.dev/docs/tutorial/Plugins/audit-log/) with its
  71. executed-by column, so every change names the person and the agent.
  72. 4. No production data, emails or payments in this first version.
  73. SHOW ME
  74. Run the app and give me the local address and sign-in. Connect my agent with
  75. the command from the Agents settings page, then do one operation through the
  76. agent: find a record that needs attention, add its next action, and show me the
  77. audit log entry. Show one action my agent is allowed and one a teammate's agent
  78. would be refused. Say which checks you actually performed.
  79. Write five prompts for my daily work with this app, in the words of my process.
  80. Explain where the code and data are, how to reopen the app tomorrow, how to
  81. update AdminForth and its plugins later, and what remains before my team uses
  82. it: hosting, real data, backups, access review.
  83. ```
  84. </details>
  85. Prompts for the first day, with the example above:
  86. - `What needs my attention today?`
  87. - `Which follow-ups are overdue, and whose?`
  88. - `Add a request from Harbor Café: office maintenance quote. Owner Maya, next action: send the quote by Friday.`
  89. - `Which invoices are unpaid for more than 30 days?`
  90. <picture>
  91. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/readme/business-overview-dark.png">
  92. <img src="https://raw.githubusercontent.com/devforth/adminforth/main/documentation/static/img/readme/business-overview-light.png" width="100%" alt="The Overview page of the example app: open requests, overdue follow-ups, jobs this week, unpaid invoices, today's jobs and items low in stock.">
  93. </picture>
  94. <p align="center"><sub>When you want to look: the overview of the whole business, built with the dashboard plugin.</sub></p>
  95. > [!NOTE]
  96. > The framework is free and MIT-licensed. Coding-agent access, model usage, hosting and paid services you connect have their own costs. Check each change in the app before your team relies on it.
  97. ⭐ **Star AdminForth** to find it again when your agents need an admin to work in.
  98. ## For developers
  99. 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:
  100. - **Data sources:** Postgres, MySQL, SQLite, MongoDB, ClickHouse.
  101. - **Agents:** the [MCP server plugin](https://adminforth.dev/docs/tutorial/Plugins/mcp/) 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](https://adminforth.dev/docs/tutorial/Plugins/agent/); resources and endpoints you can hide from agents; [audit log](https://adminforth.dev/docs/tutorial/Plugins/audit-log/) with agent attribution.
  102. - **Security plugins:** TOTP and passkeys, OAuth SSO, user sessions with revoke, login captcha, signed password-reset tokens.
  103. - **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.
  104. - **More plugins:** import and export (CSV, XLSX), uploads to S3, i18n, rich editor, background jobs, dashboards and [more](https://adminforth.dev/docs/tutorial/ListOfPlugins/).
  105. - **Made for coding agents:** generated apps ship `AGENTS.md`, `CLAUDE.md` and skills; the docs publish [`llms.txt`](https://adminforth.dev/llms.txt).
  106. [Hello world in 5 minutes](https://adminforth.dev/docs/tutorial/gettingStarted/) · [Live demo](https://demo.adminforth.dev/) · [Tutorial](https://adminforth.dev/docs/tutorial/Customization/branding/) · [YouTube: an agentic admin panel in minutes](https://www.youtube.com/watch?v=4tB8uzY__uk)
  107. ## Project initialisation
  108. 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.
  109. ### Path 1: Existing database
  110. Provide your database URL with `--db`, or enter it when the CLI asks `Please specify the database URL to use`:
  111. ```bash
  112. pnpm dlx adminforth@latest create-app --app-name myadmin --db "postgresql://user:password@localhost:5432/dbname"
  113. cd myadmin
  114. ```
  115. 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.
  116. Then generate AdminForth resource files from your existing tables:
  117. ```bash
  118. pnpm exec adminforth resource
  119. ```
  120. ### Path 2: New database
  121. Omit `--db`, or accept the default `sqlite://.db.sqlite` value in the interactive prompt, and choose Prisma migrations:
  122. ```bash
  123. pnpm dlx adminforth@latest create-app --app-name myadmin
  124. cd myadmin
  125. pnpm makemigration --name init && pnpm migrate:local
  126. pnpm dev
  127. ```
  128. Please follow [getting started](https://adminforth.dev/docs/tutorial/gettingStarted/) for the full guide.
  129. # For AdminForth developers
  130. > Follow this section only if you want to make changes to the AdminForth framework or develop a plugin.
  131. 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.
  132. ## Requirements
  133. - **Node.js 22.12+, 24, or 26** (Node.js 20 and 21 are not supported)
  134. - **Docker**
  135. - **pnpm**
  136. - **Taskfile**
  137. To run dev demo:
  138. ```sh
  139. cd dev-demo
  140. pnpm setup-dev-demo
  141. pnpm migrate:all
  142. pnpm start
  143. ```
  144. ## Adding columns to a database in dev-demo
  145. Open `./migrations` folder. There is prisma migration folder for the sqlite, postgres and mysql and `clickhouse_migrations` folder for the clickhouse:
  146. ### Migrations for the MySQL, SQLite and Postgres
  147. To make migration add to the .prisma file in folder with database you need and add new tables or columns. Then run:
  148. ```
  149. pnpm makemigration:sqlite -- --name init
  150. ```
  151. and
  152. ```
  153. pnpm migrate:sqlite
  154. ```
  155. to apply migration
  156. > use :sqlite, :mysql or :postgres for you case
  157. ### Migrations for the clickhouse
  158. In order to make migration for the clickhouse, go to the `./migrations/clickhouse_migrations` folder and add migration file to the folder.
  159. Then run
  160. ```
  161. pnpm migrate:clickhouse
  162. ```
  163. to apply the migration.
  164. ## Testing CLI commands during development
  165. Make sure you have not `adminforth` globally installed. If you have it, remove it:
  166. ```sh
  167. pnpm uninstall -g adminforth
  168. ```
  169. Then, in the root of the project, run once:
  170. ```
  171. cd adminforth/adminforth
  172. pnpm build
  173. pnpm link
  174. ```
  175. Then, go to testing app, e.g. created with CLI, and use next command:
  176. ```
  177. npx -g adminforth <your command under development>
  178. ```
  179. This will always run latest version of adminforth package.
  180. ## Star History
  181. [![Star History Chart](https://api.star-history.com/svg?repos=devforth/adminforth&type=date&legend=top-left)](https://www.star-history.com/#devforth/adminforth&type=date&legend=top-left)
  182. ## Want to talk through your process?
  183. [Book a free 30-minute consultation](https://talk.devforth.io/book/30-minute-meeting) 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.
  184. <a href="https://devforth.io"><img src="https://raw.githubusercontent.com/devforth/OnLogs/e97944fffc24fec0ce2347b205c9bda3be8de5c5/.assets/df_powered_by.svg" height="28" alt="Powered by Devforth"></a>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.