# DeskMonitor (remote · api.thedeskmonitor.com)

DeskMonitor: 24 workforce-intelligence MCP tools, OAuth 2.1, free demo key included.

- Trust score: 75/100 (medium)
- Change this week: +51
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.thedeskmonitor.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-thedeskmonitor-mcp/api-mcp-v1.md), [page](https://verifymcp.io/servers/com-thedeskmonitor-mcp/api-mcp-v1)

## Channel facts

- Endpoint: `https://api.thedeskmonitor.com/api/mcp/v1`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2770 tokens (~115/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-thedeskmonitor-mcp https://api.thedeskmonitor.com/api/mcp/v1
```

### Codex

```toml
[mcp_servers.com-thedeskmonitor-mcp]
url = "https://api.thedeskmonitor.com/api/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thedeskmonitor-mcp": {
      "type": "remote",
      "url": "https://api.thedeskmonitor.com/api/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thedeskmonitor-mcp --url https://api.thedeskmonitor.com/api/mcp/v1 --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thedeskmonitor-mcp:
    url: "https://api.thedeskmonitor.com/api/mcp/v1"
```

### Other

```json
{
  "mcpServers": {
    "com-thedeskmonitor-mcp": {
      "type": "http",
      "url": "https://api.thedeskmonitor.com/api/mcp/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 75, +37)

- [security improvement] Transport: unverified → pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Tool “start_free_trial” now declares an output schema
- [functional improvement] Tool “invite_staff” now declares an output schema
- [functional improvement] Tool “list_employees” now declares an output schema
- [functional improvement] Tool “list_my_timesheet” now declares an output schema
- [functional improvement] Tool “list_pending_approvals” now declares an output schema
- [functional improvement] Tool “list_recent_activity” now declares an output schema
- [functional improvement] Tool “summarize_team_hours” now declares an output schema
- [functional improvement] Tool “switch_to_demo” now declares an output schema
- [functional improvement] Tool “switch_to_production” now declares an output schema
- [functional improvement] Tool “ask_workforce” now declares an output schema
- [functional improvement] Tool “clock_in” now declares an output schema
- [functional improvement] Tool “clock_out” now declares an output schema
- [functional improvement] Tool “get_analytics_feature_usage” now declares an output schema
- [functional improvement] Tool “get_analytics_overview” now declares an output schema
- [functional improvement] Tool “get_analytics_questions” now declares an output schema
- [functional improvement] Tool “get_capabilities” now declares an output schema
- [functional improvement] Tool “get_dashboard_summary” now declares an output schema
- [functional improvement] Tool “get_data_dictionary” now declares an output schema
- [functional improvement] Tool “get_demo_scenarios” now declares an output schema
- [functional improvement] Tool “get_employee_details” now declares an output schema
- [functional improvement] Tool “get_pricing_and_plans” now declares an output schema
- [functional improvement] Tool “get_productivity_overview” now declares an output schema
- [functional improvement] Tool “get_started_guide” now declares an output schema
- [functional improvement] Tool “get_workload_alerts” now declares an output schema
- [functional] First check of Tool coverage: 89
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 79
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [cosmetic] “list_employees” reworded the description of “page”
- [cosmetic] “list_employees” reworded the description of “page_size”
- [cosmetic] “list_pending_approvals” reworded the description of “team_id”
- [cosmetic] “summarize_team_hours” reworded the description of “team_id”
- [cosmetic] “get_analytics_feature_usage” reworded the description of “period”

### 2026-07-31 (score 38, +14)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 24, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 24)

First indexed and scored.

## MCP tools (24)

### `get_started_guide` (~90 tokens)

Get Started Guide

Returns a role-scoped welcome message and curated sample questions to help you get started with DeskMonitor AI. Use when a new user asks 'what can I do?', 'what can I ask?', or 'how do I get started?' Call this first when connecting. Do NOT use for querying live workforce data.

Input parameters:

- `role` (string): Your role hint. If omitted, inferred from auth token.

Output parameters:

- `api_key_note` (string): API key setup guidance
- `api_key_setup_url` (string): URL to generate an API key
- `mcp_auth_method` (string): Auth method description
- `mcp_config_snippet` (string): Ready-to-paste MCP client config JSON
- `mcp_server_url` (string): MCP server endpoint URL
- `mode` (string): demo or production
- `sample_questions` (array): Curated starter questions for this role
- `support` (object): Support contact information
- `tenant_name` (string): Tenant display name
- `welcome_message` (string): Role-scoped welcome text

### `get_data_dictionary` (~69 tokens)

Data Dictionary

Returns the schema of queryable data — what fields exist, their meaning, and which tools expose them. Use when the user asks 'what data exists?', 'what fields are available?', or 'what is a productivity score?'. NOT for querying live data — use the analytics tools for live results.

Output parameters:

- `entities` (array): Array of data entity definitions, each with name, description, fields array, and exposed_by_tool

### `switch_to_demo` (~55 tokens)

Switch to Demo Mode

Switches to DeskMonitor demo mode with synthetic data. Returns demo tenant info and suggested queries. Use when the user wants to explore without a real account. Use a dm_demo_* API key to call data tools in demo mode.

Output parameters:

- `demo_tenant_id` (string): Demo tenant readable ID (DEMO-000001)
- `message` (string): Activation confirmation message
- `mode` (string): Always 'demo'
- `note` (string): Instructions for calling data tools in demo mode
- `sample_questions` (array): Suggested queries to try in demo mode

### `switch_to_production` (~43 tokens)

Switch to Production Mode

Switches back to production mode and confirms your real tenant context from your auth token. Use when the user wants to see their real company data after exploring demo mode.

Output parameters:

- `message` (string): Confirmation or onboarding guidance
- `mode` (string): Always 'production'
- `tenant_readable_id` (string): The authenticated tenant's readable ID
- `user_id` (string): Authenticated user ID

### `get_demo_scenarios` (~43 tokens)

Demo Scenarios

Returns 5 guided scenario walkthroughs using the demo tenant's synthetic data. Use when the user wants to see example queries or guided tours of DeskMonitor capabilities.

Output parameters:

- `scenarios` (array): Array of scenario objects, each with id, title, description, and suggested_queries array

### `get_dashboard_summary` (~77 tokens)

Dashboard Summary

Returns the dashboard KPIs for the current user — hours worked today, team productivity score, pending approvals, active headcount. Use when the user asks 'how is my team today?', 'am I clocked in?', 'what's my summary?'. Do NOT use for historical timesheet data — use list_my_timesheet for that.

Output parameters:

- `as_of` (string): ISO 8601 timestamp of the snapshot
- `error` (string): Error message if retrieval failed

### `list_employees` (~125 tokens)

List Employees

Lists employees visible to the current user based on their role. Supports pagination and name search. Use when the user asks 'who is on my team?', 'list all employees', or wants a roster. Use get_employee_details for information about ONE specific person.

Input parameters:

- `page` (integer): Page number (1-based). Default: 1.
- `page_size` (integer): Number of employees per page (max 100). Default: 20.
- `search` (string): Name or email search filter
- `team_id` (string): Filter by team (manager scope)

Output parameters:

- `applied_filters` (object): Echo of filters used: team_id, search, page, page_size
- `result` (object): Paginated result: employees array, total count, current page

### `get_employee_details` (~83 tokens)

Employee Details

Returns the full profile for a specific employee including role, team, clock-in status, and recent activity. Use when the user asks about ONE specific person. Use list_employees for multiple people. Use 'me' as employee_id for the authenticated user's own profile.

Input parameters:

- `employee_id` (string, required): Employee ID (UUID) or 'me' for the authenticated user.

Output parameters:

- `email` (string): Work email
- `id` (string): Employee UUID
- `is_clocked_in` (boolean): Whether currently clocked in
- `name` (string): Full name
- `role` (string): Employee role
- `team` (string): Team name

### `list_my_timesheet` (~105 tokens)

My Timesheet

Returns the authenticated user's time log entries for a date range. Use when the user asks 'how many hours have I worked?', 'show me my timesheet', or 'what did I work on yesterday?'. Cannot query another person's timesheet — use summarize_team_hours for team-level hours.

Input parameters:

- `from` (string): Start date (YYYY-MM-DD). Defaults to 30 days ago.
- `to` (string): End date (YYYY-MM-DD). Defaults to today.

Output parameters:

- `entries` (array): Array of timesheet entries
- `total_hours` (number): Total hours in the date range

### `summarize_team_hours` (~115 tokens)

Team Hours Summary

Aggregates hours worked by the manager's team for a given period. Requires Manager role or above. Use when the manager asks 'how many hours did my team work this week?', 'show me team hours', or 'who worked the most hours?'. Do NOT use for an individual employee's timesheet — use list_my_timesheet for personal timesheets.

Input parameters:

- `period` (string)
- `team_id` (string): Team ID (UUID) to scope the report. Defaults to the manager's primary team if omitted.

Output parameters:

- `period_applied` (string): Period enum value used
- `period_end` (string): Computed end date (YYYY-MM-DD)
- `period_start` (string): Computed start date (YYYY-MM-DD)
- `result` (object): Team hours breakdown from the attendance report
- `scope_team_id` (string): Resolved team UUID or null for org-wide
- `scope_team_name` (string): Resolved team name

### `list_pending_approvals` (~78 tokens)

Pending Approvals

Returns timesheets pending approval in the manager's team. Requires Manager role or above. Use when the manager asks 'show me pending approvals', 'who needs sign-off?', or 'any outstanding timesheets?'.

Input parameters:

- `team_id` (string): Optional team UUID to filter pending approvals. Omit for all teams visible to this user.

Output parameters:

- `count` (integer): Number of pending approval items
- `items` (array): Array of pending approval records

### `list_recent_activity` (~100 tokens)

Recent Activity

Returns a daily aggregate activity feed scoped to the authenticated user, including clock events, timesheet submissions, and approval actions. Use when the user asks 'show me recent activity', 'what happened today?', or 'what did I do yesterday?'. Not a real-time stream — data reflects completed events within the selected time window.

Input parameters:

- `limit` (integer)
- `since` (string): Return activity after this timestamp. Defaults to 24h ago.

Output parameters:

- `events` (array): Array of activity events

### `get_workload_alerts` (~73 tokens)

Workload Alerts

Returns workload alerts — team members with unusual hours, employees not yet clocked in, timesheet gaps. Use when the manager asks 'who needs attention?', 'any anomalies today?', 'any warnings?', or 'are there any issues?'.

Input parameters:

- `date` (string): Date to check. Defaults to today.

Output parameters:

- `alerts` (array): Array of workload alert items per employee
- `as_of` (string): Snapshot timestamp
- `total_count` (integer): Total number of alerts

### `get_productivity_overview` (~99 tokens)

Productivity Overview

Returns productivity scores and active/idle time ratios for an employee or team. Use when the user asks 'what's my productivity score?', 'how productive was the team?', or 'show me active vs idle time'. Employee sees own data only. Manager+ can query other team member IDs.

Input parameters:

- `period` (string)
- `user_id` (string): Target user. Defaults to authenticated user. Manager+ can specify team member IDs.

Output parameters:

- `data_availability` (string): available | no_data | synthetic_demo
- `period_applied` (string): Period enum value used
- `privacy_note` (string): Privacy clarification for activity scoring
- `productiveSeconds` (integer): Seconds of productive app use
- `score` (integer): Productivity score 0-100
- `totalSeconds` (integer): Total tracked seconds
- `week_end` (string): Period end date (YYYY-MM-DD)
- `week_start` (string): Period start date (YYYY-MM-DD)

### `clock_in` (~236 tokens)

Clock In

Clock the authenticated user in to start a new work session. Creates a TimeLog entry in DeskMonitor.
Use when the user says 'clock me in', 'start my shift', 'I am starting work', or any attendance start phrase.
Supports optional GPS coordinates for geofence validation.
WARNING: This is a write tool — it mutates DeskMonitor data. Always confirm with the user before calling this tool. Example: tell the user what you are about to do and ask for explicit confirmation before proceeding.
Calling clock_in will end any active DeskAgent desktop session for this user (cross-device handover by design).
Do NOT call if the user is already clocked in — call get_dashboard_summary first to check status.
Returns: { success, clock_in_time, is_within_geofence, matched_office_name, next_tap_due_at }.
Requires a user-scoped API key (dm_live_* key bound to a specific user). Disabled in demo mode.

Input parameters:

- `latitude` (number): GPS latitude (optional). Used for geofence validation.
- `longitude` (number): GPS longitude (optional). Used for geofence validation.

Output parameters:

- `clock_in_time` (string): ISO 8601 clock-in timestamp
- `error` (string): Error code if clock-in failed
- `is_within_geofence` (boolean): Whether the location is within a configured geofence
- `matched_office_name` (string): Name of the matched office/geofence, if any
- `message` (string): Human-readable result or error message
- `next_tap_due_at` (string): When the next attendance tap is expected
- `success` (boolean): Whether the clock-in succeeded

### `clock_out` (~164 tokens)

Clock Out

Clock the authenticated user out to end their current work session. Finalises the TimeLog and generates gap-fill blocks.
Use when the user says 'clock me out', 'end my shift', 'I am done for the day', or any attendance end phrase.
WARNING: This is a write tool — it mutates DeskMonitor data. Always confirm with the user before calling this tool.
Do NOT call if the user is already clocked out — call get_dashboard_summary first to check status.
Returns: { success, clock_in_time, clock_out_time, blocks_generated }.
Requires a user-scoped API key. Disabled in demo mode.

Input parameters:

- `latitude` (number): GPS latitude at clock-out (optional).
- `longitude` (number): GPS longitude at clock-out (optional).

Output parameters:

- `blocks_generated` (integer): Number of gap-fill TimeLog blocks created
- `clock_in_time` (string): ISO 8601 clock-in timestamp for this session
- `clock_out_time` (string): ISO 8601 clock-out timestamp
- `error` (string): Error code if clock-out failed
- `message` (string): Human-readable result or error message
- `success` (boolean): Whether the clock-out succeeded

### `invite_staff` (~207 tokens)

Invite Staff Member

Invite a staff member to join your DeskMonitor workspace by email. Use when the user asks to 'add an employee', 'invite a team member', 'send a team invite', 'onboard someone new', or 'invite [name] to my workspace'. The invite is sent by email — the recipient gets a link to set up their account and join as an Employee. Only OwnerAdmin and Admin roles can invite staff. The invitee always joins as an Employee (role is display-only on the invite). WARNING: This is a write tool — it sends a real email invitation and creates a workspace account invitation. Always confirm the email address with the user before calling this tool. Disabled in demo mode. Returns: { status, message, email, name }.

Input parameters:

- `email` (string, required): Email address of the person to invite. Must be a valid email. Required.
- `name` (string): Full name of the person to invite (shown in the invitation email). Optional but recommended.

Output parameters:

- `email` (string): Email address the invite was sent to
- `error` (string): Error code if invitation failed
- `message` (string): Human-readable result message
- `name` (string): Name on the invitation, if provided
- `status` (string): invitation_sent or error code

### `get_capabilities` (~80 tokens)

Capabilities

Returns a structured list of DeskMonitor AI capabilities grouped by user role. Use when a new user asks 'what can I ask you?', 'what can DeskMonitor do?', 'show me all commands', 'what AI features are available?', or any capability-discovery question. Returns role-appropriate command examples and the public capabilities page URL. No authentication required.

Output parameters:

- `api_key_permissions` (object): API key scope and permission model
- `capabilities_by_role` (object): Commands grouped by role: everyone, manager_above, admin_owner_admin
- `changelog_url` (string): URL to product changelog
- `compliance` (object): Compliance status (GDPR etc)
- `data_storage` (object): Cloud provider and data residency
- `employee_self_service` (object): Self-service features available to employees
- `industries` (array): Target industry verticals
- `org_structure` (object): Org hierarchy and role levels
- `payment_integrations` (object): PayPal/Wise integration status by use case
- `platforms` (array): Platform availability (web, desktop, mobile)
- `privacy_model` (object): Privacy and monitoring model details
- `related_resources` (object): Deep-link to the capabilities reference page
- `remote_team_support` (object): Remote team support details
- `report_types` (array): Available report types
- `sso_available` (boolean): Whether SSO is currently live
- `sso_roadmap` (string): SSO roadmap status
- `support` (object): Support contact information
- `supported_ai_clients` (object): Confirmed and in-development AI client integrations
- `tool_names` (array): List of all tool name strings
- `total_tools` (integer): Total number of MCP tools available
- `write_tools` (array): Tools that mutate data

### `get_pricing_and_plans` (~72 tokens)

Pricing and Plans

Returns DeskMonitor pricing plans and subscription details. Use when the user asks 'how much does DeskMonitor cost?', 'what plans are available?', 'is there a free trial?', 'what\'s the pricing?'. Returns plan names, features, and pricing page URL. Safe to call without authentication.

Output parameters:

- `billing_portal_url` (string): URL to the billing portal
- `change_plan_note` (string): Guidance on changing plans
- `data_source` (string): live_db or fallback
- `demo_mode` (object): Demo mode availability
- `free_trial` (object): Free trial availability and duration
- `note` (string): Data freshness note
- `payment_integrations` (object): PayPal/Wise integration status
- `plans` (array): Array of plan objects (Community, Starter, Professional, Business, Enterprise)
- `related_resources` (object): Pricing and signup page URLs
- `upgrade_url` (string): URL to upgrade or manage billing

### `start_free_trial` (~81 tokens)

Start Free Trial

Returns the DeskMonitor free trial sign-up URL and onboarding instructions. Use when the user says 'I want to sign up', 'start a free trial', 'how do I get started?', 'create an account', 'I want to use DeskMonitor'. This is an informational tool — it provides the registration URL, not a write action. No authentication required.

Output parameters:

- `api_key_note` (string): API key setup guidance
- `api_key_setup_url` (string): URL to generate an API key
- `demo_first` (object): Demo key and description for pre-signup exploration
- `enterprise_path` (object): Enterprise qualification pathway guidance
- `mcp_config_snippet` (string): Ready-to-paste MCP client config JSON
- `mcp_server_url` (string): MCP server endpoint URL
- `onboarding_steps` (array): Step-by-step getting started guide
- `related_resources` (object): Signup URL and label
- `signup_url` (string): Registration URL with UTM tracking
- `trial_details` (object): Trial duration, no-credit-card status, what's included

### `ask_workforce` (~189 tokens)

Ask Workforce Question

Use when the user asks a free-form, open-ended question about their workforce that you are not sure which other tool answers — for example: 'Which team has the highest cost-to-output?', 'How is my team performing?', 'Who should I talk to first?', 'What's the biggest issue today?'.

Pass the user's question VERBATIM in the 'question' field — do not paraphrase or summarize. The question is logged as admin-only product telemetry for product improvement purposes.

This tool returns routing guidance pointing to the specific DeskMonitor tools most likely to answer the question. After calling this tool, call the suggested tools to retrieve real data.

Note: Questions asked via this tool are logged for product improvement (admin-only, tenant-scoped, not employee data).

Input parameters:

- `question` (string, required): The user's question about their workforce, in their own words. Pass verbatim — do not paraphrase.

Output parameters:

- `acknowledged` (boolean): Whether the question was captured
- `message` (string): Confirmation and routing guidance
- `question_received` (string): Echo of the question (truncated to 200 chars)
- `suggested_tools` (array): Tools most likely to answer this question
- `tip` (string): Follow-up suggestion

### `get_analytics_questions` (~142 tokens)

Demand Analytics — Questions & Themes

Returns demand intelligence captured from ask_workforce calls: recent verbatim admin questions, top question themes with counts, and the most-requested 'period' argument values across all tools.

Use when the admin asks: 'What questions have I asked?', 'What am I asking most?', 'What data am I looking for?', 'Show me my question history', 'What features am I using most?'.

Auth: requires Admin or OwnerAdmin role. Not available in demo mode. Tenant-scoped — only returns this tenant's data.

Input parameters:

- `limit` (integer): Max number of recent questions to return.
- `period` (string): Reporting window for question history.

Output parameters:

- `as_of` (string): Snapshot timestamp
- `available` (boolean): Whether results are available (false in demo mode)
- `period` (string): Reporting window used
- `period_demand` (array): Most-requested period argument values
- `privacy_note` (string): Privacy scope note
- `question_count` (integer): Number of questions returned
- `recent_questions` (array): Recent verbatim questions with timestamps
- `top_themes` (array): Theme groupings with counts

### `get_analytics_overview` (~251 tokens)

Platform Analytics Overview

Returns platform-level DeskMonitor analytics — AI/MCP queries served (from the internal McpAuditLogs table), web sessions, active unique visitors (1-day, 7-day, 28-day windows) and top referring sources (from Cloudflare Web Analytics when configured).

Use when the user asks: 'how many users does DeskMonitor have?', 'show me traffic stats', 'how many AI queries were served?', 'how many people are using DeskMonitor?', or any question about platform-level usage counts or audience size.

Do NOT use for: per-tenant employee data (use get_dashboard_summary), individual timesheet data (use list_my_timesheet), or real-time attendance (use get_workload_alerts).

Auth: requires an Admin or OwnerAdmin API key. Not available in demo mode.
Returns: active_users_1d, active_users_7d, active_users_28d, sessions_in_period, ai_queries_served_in_period, top_sources (up to 5), period, as_of.
Web traffic fields are 0 when Cloudflare Analytics is not configured (AI query count is always present).

Input parameters:

- `period` (string): Reporting window for session and AI-query counts.

Output parameters:

- `active_users_1d` (integer): Unique active users in the last 1 day
- `active_users_28d` (integer): Unique active users in the last 28 days
- `active_users_7d` (integer): Unique active users in the last 7 days
- `ai_queries_served_in_period` (integer): MCP tool calls served from McpAuditLogs
- `as_of` (string): Snapshot timestamp
- `available` (boolean): Whether analytics data is available
- `period` (string): Reporting window used
- `sessions_in_period` (integer): Total sessions in the reporting window
- `top_sources` (array): Top referring sources with session counts

### `get_analytics_feature_usage` (~193 tokens)

Platform Feature Usage Breakdown

Returns a breakdown of which DeskMonitor MCP tools users are calling most — sourced from the internal McpAuditLogs table, grouped by ToolName (top-N tool call counts for the period).

Use when the user asks: 'which MCP tools are most used?', 'which features are most popular?', 'what do AI clients do most in DeskMonitor?', 'show me feature engagement'.

Do NOT use for: raw session counts or audience size (use get_analytics_overview), employee-level productivity data (use get_productivity_overview), or real-time attendance data.

Auth: requires Admin or OwnerAdmin API key. Not available in demo mode.
Returns: feature_areas (list with tool_name and call_count), top_events, period, as_of.

Input parameters:

- `limit` (integer): Number of feature areas to return.
- `period` (string): Reporting window for tool call counts. Default: this_week.

Output parameters:

- `as_of` (string): Snapshot timestamp
- `available` (boolean): Whether analytics data is available
- `feature_areas` (array): Top tool call counts grouped by ToolName
- `period` (string): Reporting window used
- `top_events` (array): Top event names with counts

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-thedeskmonitor-mcp/api-mcp-v1#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 75
- 2026-08-01: 38
- 2026-07-31: 38
- 2026-07-30: 24
- 2026-07-29: 24
- 2026-07-28: 24
- 2026-07-27: 24
- 2026-07-26: 24

## Links

- Remote endpoint: https://api.thedeskmonitor.com/api/mcp/v1
- Website: https://thedeskmonitor.com/integrations/ai-connect
- Changelog RSS feed: https://verifymcp.io/servers/com-thedeskmonitor-mcp/api-mcp-v1/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thedeskmonitor-mcp/api-mcp-v1/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-thedeskmonitor-mcp/api-mcp-v1