Automox
Talk to your Automox console in natural language. Manage devices, patches, and policies.
- Category
- Security
- Primary Subcategory
- Application Security & Vulnerability Management
Integration details
Description
The official Automox MCP server, packaged as a Claude Desktop Extension. Connects Claude to your Automox environment so you can manage devices, check compliance posture, run policies, prepare for Patch Tuesday, browse the worklet catalog, drive Splashtop remote-control sessions, and more — all by asking. Exposes 133 MCP tools across 18 domains (devices, policies, patches, groups, webhooks, worklets, vulnerability sync, audit, reports, Splashtop remote control, and more), 14 MCP resources (including interactive MCP App UIs for compliance triage, patch-approval review, policy blast-radius review, remediation-apply review, and RBAC access certification), and 6 workflow prompts (audit_policy, investigate_device, onboard_group, patch_tuesday, security_posture, triage_failure). Read-only mode and modular tool loading are supported via optional configuration.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Application Security & Vulnerability Management
- Secondary Subcategories
- None listed
- Brand
- Automox
- Access
- Unknown
- First tracked
- 2026-08-12
- Tool count
- 133
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for Automox
Get updates when Automox’s Discoverability Score or category rank changes.
Claude Discoverability Score
Automox isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
133 tools agents can invoke
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.