AI assistants¶
The suite can be used from an AI assistant such as Claude, ChatGPT or Claude Code. You connect the suite to the assistant once, sign in with your Gokaizen account, and from then on you can ask the assistant to do things in the suite for you, in plain words.
| Address to connect | https://mcp.suite.internal.gokaizen.cloud/mcp |
| Sign-in | your Gokaizen account, through Auth |
| Support | internal@gokaizen.ai |
The connection uses the Model Context Protocol (MCP), an open standard that most AI assistants support. The suite does not run or train any AI itself.
The one rule¶
The assistant acts as you. It signs in as you, can do only what your role allows, and everything it does is recorded under your name, exactly as if you had done it on screen. A refusal from the suite is final: the assistant cannot work around it, and neither should you ask it to.
Connecting¶
The exact steps depend on the assistant. In each case you add the suite as a connector, custom integration or MCP server using the address above, and the assistant opens the suite's sign-in page for you.
- Claude (web, desktop, mobile): Settings → Connectors → Add custom connector, paste the address, then sign in when asked. An administrator may have added it for the whole organization already, in which case it only needs enabling.
- Claude Code:
claude mcp add --transport http gokaizen https://mcp.suite.internal.gokaizen.cloud/mcp, then/mcpinside Claude Code to sign in. - ChatGPT: available on business and enterprise plans once a workspace administrator has enabled the suite as a connector. Then Settings → Connectors, and sign in when asked.
- Other assistants and tools (Cursor, Windsurf, Copilot and the like): add a remote MCP server with the address above and sign in when prompted.
You sign in through the suite's own sign-in page, with your usual password, code or passkey. Your password is never shared with the assistant or its provider: the assistant only receives a token that lets it act as you until it expires or you disconnect.
To disconnect, remove the connector in the assistant. The suite lets an assistant hand back the access it was given, so one that does this is finished with the suite the moment you remove it; one that does not leaves its access to lapse on its own instead. If your suite access is removed, every assistant you connected stops working with it at the same time, whichever kind it is.
What you can ask¶
Each assistant words things its own way. What the suite offers, by area:
| Area | What the assistant can do |
|---|---|
| Yourself | Who you are signed in as, which employee record is yours, what your role allows, and whether you may clock in or out right now |
| People | Find an employee by name or number; read a person's record, position and employment; the company's headcount |
| Projects and partners | Find a project (shown as Customer - Project) or a cost center; list customers and suppliers |
| Timesheets | Read anyone's timesheet you may see, or your own. Log time for people: the assistant shows you a plan first — who, which day, which project, how many hours, and whether it replaces a day already encoded — and writes it only after you agree |
| Attendance | Who worked which day, with hours and overtime; overtime claimed on a timesheet that nobody has filed a request for; whether a cutoff is fully encoded; the time clock's days and how they were verified |
| Leave and overtime | List requests, file leave or overtime for yourself or for someone else, withdraw a request, see who is on leave over a range, and the leave types you may file |
| Calendar | Holidays with their pay multipliers, and pay periods with their dates and pay date |
| Approvals | List everything waiting on your decision — overtime, leave, deduction requests and advances, incentive grants, quotations and invoices — and approve or reject one at a time, as it was filed |
| Pay | Your own payslips, and one in full |
| Payroll | List payroll runs; simulate a run for a period, which calculates everything and pays nothing; labor cost by project or cost center |
| Deductions and incentives | Deduction requests and advances, incentive grants, and what people still owe |
| Sales | Quotations, sales orders, invoices and delivery receipts; what customers owe and what is overdue; the quotation pipeline |
Every action, in detail¶
The server publishes its own reference, generated from what it is actually running:
What an AI assistant can do in the Gokaizen Suite
It opens on a short overview and gives each group of actions its own page, so you can go straight to the part you need. Every action is listed by name with what it takes, whether it changes anything, and a worked example. It is always current, so it is the place to look rather than this one when you want the detail — it also repeats the connecting steps above, for whoever opens the reference without coming through here.
How it keeps you and the suite safe¶
- Your account, your permissions. There is no shared "AI user". Every request carries your own sign-in, is checked against your roles, and is written to the audit log under your name.
- Confirmation before writing. Assistants ask you before running an action that changes something, and the suite adds a second step for anything that writes many rows: it shows the plan in words first and writes only what you saw. A plan can be used once and expires after fifteen minutes.
- Sign-in stays in the suite. The assistant never sees your password. It is sent to the suite's own sign-in page, and the token it receives expires on its own and is refreshed only while you keep the connector.
- Encrypted end to end. The connection is HTTPS only.
- Limits on use. Requests are rate-limited per person and per network address, sign-in attempts are limited, and oversized requests are refused, so a runaway or malicious client cannot slow the suite down for everyone or guess its way in.
- Only known assistants can start a sign-in. An assistant must register itself before it can send anyone to the sign-in page, and it may only be sent back to secure (HTTPS) addresses or to a program on your own computer.
- A record of every action. Each request the assistant makes is logged with who made it, what was asked and whether it succeeded, so misuse can be investigated. What you typed is not logged.
- Removing access ends it. Deactivating a person's suite access stops every assistant they connected at the same moment.
- Disconnecting can end it at once. The suite offers every assistant a way to hand back the access it was given, so removing a connector can finish it there and then rather than leaving it to lapse.
- Assistant access stands on its own. It is registered separately from the suite's own sign-in, with the same people and the same permissions, so it can be withdrawn for everyone at once without interrupting anybody's ordinary use of the suite.
What the AI provider receives¶
When you ask an assistant something, your question and the suite's answer pass through the assistant's provider (Anthropic for Claude, OpenAI for ChatGPT, and so on) under that provider's terms and privacy policy. Treat anything you ask for as information you are sharing with that provider.
- Ask only for what your work needs. Do not ask the assistant to list government identifiers, bank account numbers or salary rates unless your task genuinely requires them.
- Use a work account with the assistant, under the arrangements Gokaizen has with that provider. Do not connect the suite to a personal account.
- The suite does not send anything to an AI provider on its own. Data moves only when you ask.
The privacy policy has the details, and the terms of use say what is expected of you.