Run your business from the AI assistant you already use
One MCP server puts 130 tools in front of Claude, ChatGPT, Codex or any MCP client. It asks before it writes, drafts before it publishes, and logs what it did.
MCP is off until you connect it, and each connection only reaches the businesses you allow.
update_builder_surface_draft · home
Dashain offer: 15% off
This week only, in store and online.
What it does
15 things AI & MCP does for you
The same circles as the features map, grouped by the part of the day they help with.
AI & MCP
- One MCP server One URL puts 130 tools in front of the AI you already use.
- Connect in minutes Copy the setup for ChatGPT, Codex, Claude Code or any MCP client from Settings.
- Orders by AI List and read orders, preview a status change, then make it.
- Typed actions Create orders, collect payments, issue refunds, manage KOTs, adjust stock and record expenses.
- Confirm before writing A write can run as a dry run first; one that needs it will not run without a confirmation.
- AI page builder An agent drafts pages, themes and the design system; you preview, then publish.
- Categories by AI Create, update and nest categories, one at a time or in a batch.
- SEO by AI An SEO health report, SEO fields and missing image alt text, fixed by an agent.
- Content by AI Blog and module entries written, illustrated and updated by an agent.
- Read your records An agent can list, describe and query the records your plan exposes.
- Audit log Agent calls are logged, and an agent can list them and see what one call sent.
- Scoped access An OAuth token per connection; the agent sees only the businesses and tools it is allowed.
- AI workspace Organise categories by asking, in a chat-style workspace.
- AI descriptions Draft item descriptions with AI.
- Your own AI key Add your own AI provider key, and generated images use your account.
How it works
Three steps from sign up to your first AI-made change
-
1
Open AI / MCP Connection
In Settings, under Advanced, copy the setup for ChatGPT, Codex, Claude Code or any MCP client.
-
2
Approve the connection
Sign in and approve it. The token reaches only the businesses and tools you are allowed.
-
3
Ask for the change
The assistant drafts or dry-runs it, you check it, and it goes live when you confirm.
- tools on one MCP server
- 130
- URL for every client you connect
- 1
- steps before a public change: draft, preview, publish
- 3
- audit log of what agents did
- 1
What the assistant can reach
Autohisab Business (dev) runs one MCP server that an outside AI assistant connects to with an OAuth token you approve. Through it the assistant can list and read orders and move an order's status, create orders, collect payments, issue refunds, adjust stock and record expenses, manage categories, fix SEO fields and missing alt text, write blog entries, and draft pages, themes and the design system in the page builder. Anything that reaches a public page goes draft, then preview, then publish. A write that needs it runs as a dry run first and only goes ahead with a confirmation, and agent calls are written to an audit log you can read back.
- Orders
- List, read, preview and move a status
- Money and stock
- Payments, refunds, expenses, stock adjustments
- Catalogue
- Categories, items and parties
- Storefront
- SEO fields and image alt text
- Content
- Blog and module entries
- Page builder
- Pages, themes and the design system, as drafts
MCP audit log
-
list_orderssuccess -
perform_actionsuccess -
update_module_entrydenied
Each row names the tool, who called it and whether it ran. Page builder calls are kept in the builder's own log.
Connect your AI
Connect in a couple of minutes
Every client connects to one address, https://business-dev.autohisab.com/mcp/business.
You sign in to Autohisab Business (dev) and approve access; the connection acts as your account, on the businesses you can manage, with the tools your plan and role allow.
Public changes go draft, preview, publish; writes that need it ask for a confirmation; calls are written to an audit log.
Claude (web or Desktop)
- 1 Open Customize, then Connectors, and click the + button.
- 2 Choose Add custom connector, give it a name and paste the server URL below.
- 3 Click Add, then sign in to Autohisab Business (dev) in the window that opens and approve access.
https://business-dev.autohisab.com/mcp/businessClaude Code
- 1 Run this in your terminal.
- 2 Start Claude Code, type /mcp, choose the server and follow the browser sign-in.
claude mcp add --transport http autohisab_business_dev_development https://business-dev.autohisab.com/mcp/businessIt worked if
Ask it: "List my last 5 orders." The first time, it asks which business to use.
If it does not
- No sign-in window: allow pop-ups for claude.ai, or run /mcp again in Claude Code.
- Free Claude plans can add one custom connector.
- A write that needs a confirmation will ask for one: that is the safety check working.
Client steps per the Claude Help Center and Claude Code docs, checked 19 September 2026. Full tool list and reason codes: MCP developer docs.
ChatGPT (developer mode)
- 1 In ChatGPT, open Settings, then Security and login, and turn on Developer mode. Plus, Pro, Business, Enterprise and Education accounts can.
- 2 Create a developer-mode app with the + button, paste the server URL below and choose OAuth.
- 3 Sign in to Autohisab Business (dev) when asked, then pick the app from the composer's Developer mode tool.
https://business-dev.autohisab.com/mcp/businessCodex CLI
- 1 Add the server, then sign in. The second command opens your browser.
codex mcp add autohisab_business_dev_development --url https://business-dev.autohisab.com/mcp/business
codex mcp login autohisab_business_dev_developmentIt worked if
Ask it: "List my last 5 orders." The first time, it asks which business to use.
If it does not
- On a Business or Enterprise workspace, an admin has to allow developer mode first.
- Codex keeps servers in ~/.codex/config.toml under [mcp_servers.autohisab_business_dev_development].
- A write that needs a confirmation will ask for one: that is the safety check working.
Client steps per the OpenAI developer mode and Codex MCP docs, checked 19 September 2026. Full tool list and reason codes: MCP developer docs.
Gemini CLI
- 1 Add the server with the command below, or add the JSON to ~/.gemini/settings.json.
- 2 Start Gemini CLI and run /mcp auth autohisab_business_dev_development to sign in through your browser.
gemini mcp add --transport http autohisab_business_dev_development https://business-dev.autohisab.com/mcp/businesssettings.json
{
"mcpServers": {
"autohisab_business_dev_development": {
"httpUrl": "https://business-dev.autohisab.com/mcp/business"
}
}
}It worked if
Ask it: "List my last 5 orders." The first time, it asks which business to use.
If it does not
- Use httpUrl, not url: url is for SSE servers in Gemini CLI.
- If tools do not appear, run /mcp to see the server's status.
- A write that needs a confirmation will ask for one: that is the safety check working.
Client steps per the Gemini CLI MCP docs, checked 19 September 2026. Full tool list and reason codes: MCP developer docs.
Connection details
Server URL https://business-dev.autohisab.com/mcp/business
Transport Streamable HTTP
Auth OAuth, scope mcp:use
Resource metadata https://business-dev.autohisab.com/.well-known/oauth-protected-resource
Auth server https://business-dev.autohisab.com/.well-known/oauth-authorization-server
Client register https://business-dev.autohisab.com/oauth/registerIt worked if
Ask it: "List my last 5 orders." The first time, it asks which business to use.
If it does not
- A 401 on the first call is normal: it carries the sign-in details the client follows.
- The full tool list, annotations and reason codes are on the MCP developer docs page.
- A write that needs a confirmation will ask for one: that is the safety check working.
Full tool list and reason codes: MCP developer docs.
-
Any client that speaks MCP. Settings has ready-made setups for ChatGPT, Codex and Claude Code, and a generic one for everything else. They all connect to the same single server.
-
Writes are designed not to surprise you. A write can be run as a dry run that describes its effect and changes nothing; an action that needs confirmation will only run when the call carries the confirmation from that dry run. Anything that reaches a public page is saved as a draft you preview before it is published.
-
No. The connection uses an OAuth token that you approve, every tool checks that the business it is asked about is one the token may manage, and the assistant is only offered the tools your plan and permissions include. A business it may not reach is answered the same way as one that does not exist.
-
Yes. Agent calls are written to an audit log. The assistant can list it with list_mcp_audit, and mcp_call_replay shows what one call sent without running it again. Page builder calls are kept in the builder's own audit log.
-
No. MCP is off until you connect it from Settings, under Advanced, AI / MCP Connection. When your plan does not include MCP, that screen says so instead of handing out an address that would refuse you.
-
Yes, for image generation. MCP lets your assistant work in the business; separately, Settings has AI Providers, where you can add your own provider key. Today that key is used to generate storefront images, entry featured images and auto content images.
Your assistant works on the same records
The orders, stock and pages it changes are the ones your team sees at the counter and online.
- Ring up a sale from a searchable catalogue, take part payment, seat a table and send the kitchen its ticket.
- Stock held per outlet, low stock and out of stock at a glance, purchase orders that feed Payables, and scan-code labels.
- Build apps for your own business or for the marketplace: a scoped API, embedded screens, storefront blocks, signed webhooks and a review before merchants see them.
-
All features
Every part of Autohisab Business (dev) on one map.