Connecting an assistant
The steps differ per assistant, but each comes down to the same thing: add this address as a connector or MCP server, then sign in when the suite's own sign-in page opens.
Connecting an assistant
The steps differ per assistant, but each comes down to the same thing: add this address as a connector or MCP server, then sign in when the suite's own sign-in page opens.
The address
Everything below uses it. Nothing else is needed — no key, no secret.
https://mcp.suite.internal.gokaizen.cloud/mcpClaude web, desktop, mobile
Settings → Connectors → Add custom connector. Paste the address, then sign in when asked. If an administrator has already added it for everybody, it only needs enabling.
Claude Code
One command, then /mcp inside Claude Code to sign in.
claude mcp add --transport http gokaizen https://mcp.suite.internal.gokaizen.cloud/mcpChatGPT
On business and enterprise plans, once a workspace administrator has enabled the suite as a connector: Settings → Connectors, then sign in when asked.
Cursor, Windsurf, Copilot and others
Add a remote MCP server with the address above and sign in when prompted. Some tools want it as JSON, in which case this is the shape they expect.
{
"mcpServers": {
"gokaizen": { "type": "http", "url": "https://mcp.suite.internal.gokaizen.cloud/mcp" }
}
}What signing in does
You sign in on the suite's own page, with your usual password, code or passkey. The assistant never receives your password — only a token that lets it act as you until it expires or you disconnect. Removing the connector ends it; an assistant that hands the access back is finished with the suite immediately, and one that does not lets it lapse. If your suite access is removed, every assistant you connected stops at the same moment.
Prompts a host can offer
A prompt is a question written down: it tells the assistant which actions to take and in what order. It reads nothing and writes nothing — the actions it names do that, and each is still refused where your role does not allow it. The order is the point.
end_of_period_check prompt
The checks a timekeeper does before a pay period is closed: what is still unencoded, overtime claimed without a request, and anything waiting on a decision.
Takes
`date` (optional)
Calls
pay_periods, timesheet_gaps, unfiled_overtime, leave_requests, overtime_requests
simulate_cutoff prompt
Simulate the payroll for the period covering a date and explain it — what it would pay, who was skipped and why. Calculates and pays nothing.
Takes
`date`
Calls
simulate_payroll
cost_review prompt
Read the labor cost figures in the order that keeps them honest: check the runs reconcile before quoting anything, then the spans, the trend and the breakdown.
Takes
`year` (optional)
Calls
payroll_reconciliation, cost_dashboard, cost_over_time, job_costs