MCP and API

Give AI agents and your own integrations read-only access to the devices and fleet summaries in your CapaOne organization. The MCP server and the REST API use the same API key.

Beta: every tool and endpoint can change

The MCP server and the REST API are in beta. All MCP tools and all API endpoints are subject to change: names, arguments, parameters and response fields can change, and tools or endpoints can be removed, without notice. Don’t build anything yet that can’t handle a breaking change.

Choose a way in

	URL	Use it to	Start with
MCP server	https://mcp.capaone.com/mcp	Let an AI agent such as Claude, Microsoft Copilot, GitHub Copilot or Cursor answer questions about your devices in plain language.	Connect an MCP Client
REST API	https://mcp.capaone.com/api	Query your devices from scripts, dashboards and your own integrations.	Quickstart

What you can do

The MCP server and the REST API can both:

Task	For example	MCP tool	REST endpoint
Search devices	Windows 10 devices that have not checked in for 30 days	search_devices	GET …/mcp/device/search
Count devices per value	How many devices of each computer model, or which TeamViewer versions are installed	group_devices	GET …/mcp/device/group-by
Read a device’s details	OS version, last check-in, users, missing patches	get_device	GET …/mcp/device/{id}
Read a device’s inventory	Installed software, disks, BitLocker, antivirus, firewall rules, local administrators, your own custom inventory	get_device with include	GET …/mcp/device/{id}/inventory/{inventory}
See which organization you are connected to	Its name, ID and products	get_organization	GET …/mcp/organization

Search filters on status, operating system, patch and driver compliance, users, tags, and any value of the hardware, software, driver and custom inventory. Filtering Devices describes them all.

Everything is read-only and limited to the organization your API key belongs to. You can’t change devices or settings, and you can’t see other organizations.

Before you start

• An API key for your organization, created in the CapaOne console. See Authentication.
• For the REST API, your organization ID: the number in every path, for example /api/organizations/123456/…. It’s shown on the organization’s card under Users & Organization in the console. The MCP server works it out from the key.
• An active CapaOne contract for that organization.

In this section

• Quickstart — list the devices in your organization with one request, then narrow it down with a filter.
• Authentication — create, send and revoke the organization API keys the MCP server and the REST API use.
• Connect an MCP Client — connect Claude, GitHub Copilot, Cursor, the OpenAI API or any MCP client to the CapaOne MCP server.
• Connect Microsoft Copilot — add the MCP server to a Copilot Studio agent, then use it in Microsoft 365 Copilot and Teams.
• MCP Tools — the tools the MCP server gives an AI agent, and what to ask them.
• Build a Dashboard with Claude — prompt Claude to build a dashboard of your patch compliance and vulnerabilities.
• Filtering Devices — conditions, operators, fields and inventory filters for the device list.
• Rate Limits and Errors — rate limits, other limits and the status codes the API returns.
• API Reference — every REST endpoint, with parameters, responses and a request console. Also available as an OpenAPI document.