What it is
Laksana runs an MCP server (Model Context Protocol). An AI app that speaks MCP can list issues, work orders and inspections and read reports in your workspace, with the same access as the member who connected it. It makes changes only when the workspace switches AI changes on and the member ticks "Make changes for me" when they sign in.
Server address
Paste this address into your AI app, sign in with Laksana and pick this workspace. The app reads what you can see. It makes changes only when the workspace switches AI changes on and you tick "Make changes for me" on the sign-in screen.
https://api.laksana.app/mcp
Connections and tokens are kept per workspace. Pick the workspace to work on.
Steps for your app
Replace the address with the server address shown above if your workspace uses another one. Tokens in the examples are placeholders.
Claude (web and desktop)
Open Customize, then Connectors. Choose Add, then Add custom connector. Paste the address, select Add, then Connect and sign in.
On a Team or Enterprise plan, an organisation owner adds it first in Organization settings, Connectors.
Claude Code
Run this command, then type /mcp in Claude Code and pick laksana to sign in.
claude mcp add --transport http laksana https://api.laksana.app/mcp
Cursor
Add this to ~/.cursor/mcp.json, then open Cursor Settings, Tools & MCP, and select Connect next to laksana.
{
"mcpServers": {
"laksana": {
"url": "https://api.laksana.app/mcp"
}
}
}
Grok
Go to grok.com/connectors, choose New Connector, then Custom. Paste the address and sign in.
What the app can see
The app reads what you can see in the workspace you pick. Laksana hides phone numbers, emails, IC numbers and addresses.
Make changes from your AI app
When the workspace has AI changes switched on, your AI app can also make everyday changes for you: report an issue, file an issue under a work order, change a status, assign, add an internal comment, log a work update and hand over an inspection. Each change runs straight away as you, with the same rules as the Laksana app.
- Allow it on the sign-in screen: tick "Make changes for me" and the changes you want. You see only the changes your role allows, and the boxes start unticked.
- Your role decides, on every call. When an owner changes your role, the next call follows it. You can untick any change later in My Profile; to add one back, connect again.
- Every change is recorded with your name and the app's name, and the record's timeline reads "Name (via App)".
- Changes stay inside the workspace team: comments are internal, and notices to reporters, residents and contractors stay with the Laksana app.
- Status changes follow the workspace modules. In a helpdesk workspace your AI app moves issues along (hold, resume, resolve, close). With Maintenance on, it also acknowledges and starts issues, and a forward move turns the issue into a work order, exactly as in the Laksana app. Moves back (reopen) and cancelling stay in the Laksana app; the AI app answers with a link to the right page.
- Changes that are hard to take back (a cancel, a reject, a final check, an inspection verdict) stay in the Laksana app. The AI app answers with a link to the right page.
- Every app outside the workspace's verified list shows "Unverified app" next to its name, everywhere the name appears.
- Limits: 60 changes per connection per hour, 30 per person per minute and 300 per workspace per hour.
- An owner can switch AI changes off for the workspace on the Connected apps page at any time, and see every change with what it was before and after.
Scopes
Every connection has the base scope. The two extra scopes are optional and apply where the member may use them.
| Scope | Access |
|---|---|
workspace:read | Read workspace data |
workspace:write | Make changes for me (the changes your role allows) |
plugin:accounting:read | Accounting export summary Adds one tool: accounting_export_summary |
plugin:calendar:read | My calendar feeds Adds one tool: list_calendar_feeds |
Tools
These tools are available to a connected app. A change tool is listed only when the workspace switches AI changes on, the member's role allows it and the member ticked it at sign-in. Each tool sees only what the member can see, and results hide phone numbers, emails, IC numbers and addresses. The descriptions are the ones the server sends to the app.
| Tool | What it does | Scope needed |
|---|---|---|
get_workspace | Returns the workspace name, timezone, your role, the modules that are on, your site cover and the extra tools you can use. | workspace:read |
list_issues | Lists reported issues you can see, newest first, with status, severity, site, assignee and due dates. | workspace:read |
get_issue | Returns one issue by id or reference, with its description, reporter (initials unless a member) and linked job state. | workspace:read |
list_issue_comments | Lists the comments on one issue, oldest first, newest 100. Internal comments appear only for members who can read them. | workspace:read |
list_work_orders | Lists work orders you can see, newest first, with status, priority, site, assignee, planned window and whether they are overdue. "reference" is the work order's own reference, the one the console shows: work orders share the issue numbering (ISS-...), preventive-maintenance jobs are WO-...; there is no separate work order number. | workspace:read |
get_work_order | Returns one work order by id or reference, with its description, checklist progress and the references of the reports it answers (linked_report_references). "reference" is the work order's own reference, the one the console shows: work orders share the issue numbering (ISS-...), preventive-maintenance jobs are WO-...; there is no separate work order number. | workspace:read |
list_my_work | Lists your own open work in this workspace, up to 25 per section: work orders assigned to you or your team that are still to do (requested, awaiting approval, approved, scheduled, in progress, on hold), inspections and checklists due, and "waiting_for_check": finished items waiting for a check, both your own (yours true) and the ones you may check now (may_check true), with the full count in waiting_for_check_total. | workspace:read |
list_work_updates | Lists work updates (routine logs) you can see, newest first, with status, site, asset, category and who submitted them. | workspace:read |
list_inspections | Lists inspection records you can see by due date, with template, site, asset, status and who completed them. | workspace:read |
list_patrol_sessions | Lists patrol rounds you can see, newest first, with route, site, status, times and checkpoint progress. No locations are returned. | workspace:read |
report_maintenance | Returns a maintenance report for a date range: workspace health, issue trends, asset repairs, compliance, work orders, work updates, stock or meter readings. | workspace:read |
report_bookings | Returns a bookings report for a date range: the booking pipeline, booking revenue or stay occupancy. | workspace:read |
report_collections | Returns the collections and receivables report for a date range. People who owe are shown as initials. | workspace:read |
report_patrol_coverage | Returns the patrol coverage report for a date range. | workspace:read |
search_help | Finds up to 3 Laksana help guides that answer a question, each with a short snippet and a link. | workspace:read |
create_issue | Reports a new issue at a site the member covers, with the same defaults, notifications and response times as the Laksana app. Text only. Needs an idempotency_key: a retry with the same key returns the first issue. | workspace:write |
accept_issue_as_work_order | Files an open issue under an existing work order (mode "link" with work_order_id), as the Accept button does. If the issue is already accepted, returns its work order with already_accepted true. The workspace approval setting applies, so the work order may wait for approval. | workspace:write |
update_issue_status | Moves an issue along the same steps as the Laksana app: hold (needs a reason), resume, resolve, close. Give expected_status to avoid acting on a record that changed since you read it. A refused move returns the allowed actions. In a workspace with Maintenance on, acknowledge and start run too, and a forward move of an issue (acknowledge, start, hold, resolve) turns it into a work order, as the Laksana app does; after that, use update_work_order_status. Moves back (reopen) and cancel stay in the Laksana app: the answer is not_available_via_ai with a link to the page. In a helpdesk workspace, hold, resume, resolve and close run here. | workspace:write |
assign_issue | Assigns an issue to an active member who covers its site, or to a team (one of the two). The assignee gets the usual notice. | workspace:write |
add_comment | Adds an internal comment to an issue or a work order, visible to the workspace team only. Needs an idempotency_key. | workspace:write |
update_work_order_status | Moves a work order along the same steps as the Laksana app: hold (needs a reason) and resume. Give expected_status to avoid acting on a record that changed since you read it. A refused move returns the allowed actions. Only those run here: approve, schedule, start, complete, reject, close and cancel stay in the Laksana app, and the answer is not_available_via_ai with a link to the page. | workspace:write |
assign_work_order | Assigns a work order to an active team member who covers its site, or to a team (one of the two), as the Laksana app does. | workspace:write |
verify_work | For work that is completed and waiting for a check: send it back to work with a reason (decision "send_back"). Work is checked by someone other than the person who did it, whenever another checker is available. | workspace:write |
create_work_update | Logs a text work update at a site the member covers, status received. When the workspace asks for a photo on every update, log it in the Laksana app instead. Needs an idempotency_key. | workspace:write |
review_work_update | Validates a work update, or rejects it with a reason, as the Laksana app does. A rejected update goes back to the member who logged it for new evidence. | workspace:write |
reassign_inspection | Hands an open inspection to another member who may do it at that site. A reason is required; the new assignee gets the usual notice. | workspace:write |
Rate limit
A connected app can make 60 requests per minute per token and 120 requests per minute per workspace. A workspace add-on can raise the workspace limit. A request without a live connector token shares a strict allowance of 60 requests per minute per IP address. A 429 response carries a Retry-After header with the seconds to wait.
Revoke access
Open My Profile, then AI connectors. Pick the workspace, then choose Revoke on a token or Disconnect on an app. Revoke all my tokens removes every token you hold in that workspace.
Disconnect this app? It loses access right away. You can connect it again any time.
Turning this off stops every token right away.
If a call is refused
A token without the needed scope gets 403 with insufficient_scope and the scopes it needs in required_scopes. A workspace that switched AI connectors off refuses every token.
{"error": "insufficient_scope", "message": "The API token does not have the required scope for this endpoint.", "required_scopes": ["workspace:read"]}