See what's holding up patching.
Failed installs, pending restarts and devices that stopped checking in, as one follow-up list.
Bring CapaOne into the AI assistant your team already uses. Investigate issues, understand your exposure and turn endpoint data into clear priorities, simply by asking. In beta today for questions, investigations and reports, with actions coming next.
Sign in with CapaOne from Microsoft 365 Copilot, ChatGPT, Claude and other AI assistants, or connect any MCP client or agent platform with an API key.
AI endpoint management means an AI agent works through your endpoint platform instead of next to it, connected to CapaOne through the open Model Context Protocol (MCP).
The beta answers questions and builds reports from your live fleet. Next, the agent takes on the daily work, under rules you set.
Start with the work on your desk. The assistant brings the data together.
Failed installs, pending restarts and devices that stopped checking in, as one follow-up list.
Crashes, errors, memory, free disk space and drivers for one user's device. Observations, not a diagnosis.
A technical overview and a short summary for management, built from the same data.
A new CVE's score and CISA status, and the devices running the version you name.
Watch the CISO storyMissing encryption, local administrators and unsupported drivers, device by device.
Older models, low memory, Windows 10 and repeated crashes, as a shortlist to review.
What to fix next, in one list instead of filters and exports.
More for this roleOpen exposure and baseline gaps for the CIO and CISO, with the data behind each answer.
More for this roleWhere work stalls, and where the team's time should go.
More for this roleContext on one user's device before the remote session.
More for this roleThe beta investigates and reports. Next, agents take over the routine work, within the rules your team sets.
Planned workflow. Actions that change devices are not part of the beta.
Add the CapaOne MCP Server as a connector in your AI assistant.
Use your CapaOne login and allow access. No keys to copy.
The agent picks the tools and answers from live data.
Disconnect at any time. Approval rules arrive with actions.
Patch status per application and device your assistant can ask about today, and the packaging and deployment the agent takes on next.
Explore Application ManagerVulnerabilities, patch compliance and security posture your assistant can ask about.
Explore Security MonitorThe Windows crash and error events behind the questions support hears every day.
Explore Experience MonitorAdmin On Demand elevations per user, per process and per device.
Explore Privilege ManagerAn MCP server lets an AI agent call tools in another system through the open Model Context Protocol. The CapaOne MCP Server gives AI clients such as Claude, GitHub Copilot and Cursor tools to search devices and read inventory, patch compliance, vulnerabilities, security posture, events and Admin On Demand elevations from CapaOne.
Not in the beta, which answers questions and builds reports. We are building toward packaging, deployment and patching, with your team deciding which actions need approval.
To answer a question, CapaOne returns the data the answer needs, such as device names, user names, installed software or event descriptions, to the AI client and model you connect. That provider then processes it under its own terms. Access is limited to one CapaOne organization and to the products it has a contract for. Connect only clients and models that your organization allows to process device and user data.
The Windows endpoints CapaOne manages. Answers come from the CapaOne products your organization has a contract for: vulnerabilities and security posture need Security Monitor, crash events need Experience Monitor, and Admin On Demand elevations need Privilege Manager.
Add the CapaOne MCP Server as a connector in your AI assistant and sign in with your CapaOne login. For clients and agent platforms that do not support sign-in, a user with the Manager role can create an API key in the CapaOne console instead. Keys expire after 30 days, 90 days or one year, and a revoked key stops working on the next request.
See the CapaOne MCP Server answer questions about a real Windows fleet, and ask us about joining the beta.