Clock-in timestamp, geofence zone confirmation (if location is enabled), and a session start confirmation — for example: "You're clocked in at 8:47 AM — Northside Office Zone confirmed." The clock event is written to TheDeskMonitor in real time and your manager can see you're on shift immediately.
AI Action Commands
Your AI assistant doesn't just answer questions — it can do things. Clock in, clock out, and trigger real workforce actions through Claude, Copilot, Gemini, or any MCP-compatible AI. With your confirmation, from anywhere.
Setup Guide Back to Library HubAction commands require authentication
All write-capable commands require a user-scoped dm_live_* API key
bound to a specific TheDeskMonitor employee account (Professional+ plan).
They are not available on the demo key and are disabled in demo mode.
Your AI assistant will always confirm with you before calling any write tool. No action is triggered without your explicit approval in the AI conversation. Get your API key at Settings → API Keys.
What can AI action commands do?
Write-capable MCP tools create real data in TheDeskMonitor. Each action command includes a confirmation step in your AI assistant — you type the command, the AI confirms with you, you approve, and the action is executed. No action happens silently.
Clock-out timestamp, total session hours worked, and a productivity score summary for the session if available — for example: "Clocked out at 5:32 PM. Today's session: 8 hours 45 minutes. Productivity score: 87." The event is written to TheDeskMonitor immediately and the manager sees the confirmed session log.
Onboarding Actions (No auth required)
A registration link, the recommended onboarding steps, and a plain-English explanation of what to expect after sign-up — all without leaving your AI client. No auth required; this action is available to anyone exploring TheDeskMonitor through a connected AI assistant.
How confirmation works
All write-capable MCP tools include a built-in safety pattern: your AI assistant will always describe the action it is about to take and ask for your confirmation before calling a write tool. You cannot accidentally clock in or out without explicitly approving the action in the conversation.
Example: you type "Clock me in" → your AI responds
"I'll create a clock-in entry for you now at [current time]. Confirm?" →
you reply "Yes" → the AI calls clock_in → the event is written to TheDeskMonitor →
the AI returns confirmation of the clock-in time and any geofence result.
What's coming in future releases
The current set of write-capable MCP tools (v1.6.0) focuses on time recording actions. Additional action tools are planned for future versions of the MCP server. See the changelog for the latest updates.
Getting authenticated for action commands
Sign up or log in
Register for TheDeskMonitor or log in if you already have an account. Professional+ plan required for action tools.
Generate a user-scoped key
Go to Settings → API Keys and create a dm_live_* key.
A user-scoped key is bound to your employee account — action tools write data
for that specific employee.
Add to your AI client
Add the key as a bearer token in your AI client's MCP config. See the full setup guide for client-by-client instructions.
Start with read-only commands first
Not sure where to start? Explore all 6 INFO query categories — workforce, projects, locations, productivity, costs, and custom reports — with a free demo key (no account needed).
See INFO commands Start Free Trial