Desktop Management MCP Server
MCP server for managing devices via JAMF Pro and Microsoft Intune APIs, enabling AI assistants to query and control device management tasks.
README
Desktop Management MCP Server
Standalone Model Context Protocol (MCP) servers for JAMF Pro and Microsoft Intune. AI assistants (Claude Code, Gemini CLI, OpenCode, etc.) connect over HTTP and call device-management tools.
Architecture
MCP Client ──HTTP──▶ jamf-server (port 3001) ──▶ JAMF Pro REST API
MCP Client ──HTTP──▶ intune-server (port 3002) ──▶ Microsoft Graph API
Each server is a stateless Express app using @modelcontextprotocol/sdk. Every POST to /mcp creates a fresh StreamableHTTPServerTransport. Secrets are injected at runtime by Bitwarden Secrets Manager — no credentials are stored in the repo.
Prerequisites
- Node.js 24+
- BWS CLI (
bwsin PATH) - A Bitwarden Secrets Manager project with the secrets listed in
bws-secrets.map - JAMF Pro API client credentials (OAuth2)
- Azure AD app registration with Microsoft Graph permissions (for Intune)
Quick Start
# Install dependencies and build
npm install && npm run build
# Set your BWS machine account access token
export BWS_ACCESS_TOKEN="<your-token>"
# Start whichever server(s) you need
./start-jamf.sh # JAMF MCP on http://localhost:3001/mcp
./start-intune.sh # Intune MCP on http://localhost:3002/mcp
See bws-secrets.map for the secret names to create in your BWS project.
Environment Variables
Injected by bws run from your BWS project (see bws-secrets.map):
JAMF Pro:
JAMF_URL— e.g.https://yourorg.jamfcloud.comJAMF_CLIENT_ID,JAMF_CLIENT_SECRET
Microsoft Intune:
AZURE_TENANT_ID,AZURE_CLIENT_ID,AZURE_CLIENT_SECRET
Azure AD Graph Permissions
The Intune app registration needs these Application permissions (with admin consent):
Device.Read.AllDeviceManagementManagedDevices.Read.AllDeviceManagementApps.Read.AllDeviceManagementConfiguration.Read.AllGroup.Read.AllUser.Read.All
Client Configuration
Claude Code (~/.claude/claude_desktop_config.json or MCP settings)
{
"mcpServers": {
"jamf": {
"type": "http",
"url": "http://localhost:3001/mcp"
},
"intune": {
"type": "http",
"url": "http://localhost:3002/mcp"
}
}
}
Gemini CLI (~/.gemini/settings.json)
{
"mcpServers": {
"jamf": { "httpUrl": "http://localhost:3001/mcp" },
"intune": { "httpUrl": "http://localhost:3002/mcp" }
}
}
OpenCode (~/.config/opencode/opencode.json)
{
"mcp": {
"jamf": { "type": "remote", "url": "http://localhost:3001/mcp", "enabled": true },
"intune": { "type": "remote", "url": "http://localhost:3002/mcp", "enabled": true }
}
}
MCP Tools Reference
JAMF Pro Tools
| Tool | Description | Parameters |
|---|---|---|
jamf_get_computer |
Computer details by name | computerName |
jamf_get_computer_by_serial |
Computer details by serial number | serialNumber |
jamf_get_computers_by_user |
Macs by username / name / email | userIdentifier |
jamf_get_mobile_device |
Mobile device details by name | deviceName |
jamf_list_smart_groups |
List smart groups | type ("computer" or "mobile_device") |
jamf_get_smart_group_members |
Members of a smart group | groupId |
jamf_list_sites |
All JAMF sites | — |
jamf_list_scripts |
Scripts (with optional filter/pagination) | name?, page?, pageSize? |
jamf_list_packages |
Packages (with optional filter/pagination) | name?, page?, pageSize? |
jamf_list_inventory_preload |
Inventory preload records | page?, pageSize? |
jamf_list_prestage_configs |
Computer prestage assignments | — |
jamf_list_static_groups |
Static computer groups | — |
jamf_list_policies |
Policies list | — |
jamf_get_policy |
Policy details | policyId |
jamf_list_configuration_profiles |
Configuration profiles | — |
jamf_list_patch_policies |
Patch policies | — |
jamf_list_categories |
Categories | — |
jamf_list_departments |
Departments | — |
jamf_get_filevault_status |
FileVault encryption status | computerName |
jamf_send_mdm_command |
Send MDM command to a device | deviceId, command |
jamf_update_computer |
Update computer inventory fields | computerId, fields |
jamf_flush_mdm_commands |
Flush pending MDM commands | deviceId |
Microsoft Intune Tools
| Tool | Description | Parameters |
|---|---|---|
intune_get_autopilot_status |
Autopilot profile & status | serialNumber?, deviceName? |
intune_get_device_by_name |
Managed device by name | deviceName |
intune_get_device_by_serial |
Managed device by serial number | serialNumber |
intune_get_devices_by_user |
All devices for a user | userIdentifier |
intune_get_device_groups |
Device group memberships | deviceName?, deviceId?, serialNumber? |
intune_get_device_apps |
Detected & assigned apps | deviceName?, deviceId?, serialNumber? |
intune_list_configuration_policies |
Configuration policies (classic + settings catalog) | policyName?, platform? |
intune_troubleshoot_device_policies |
Device-level policy deployment diagnostics | deviceName?, deviceId?, serialNumber? |
intune_get_policy_assignments |
Assignment targets for a policy | policyId, source? |
intune_troubleshoot_policy |
Correlates policy assignment + device state | policyId, deviceName?, deviceId?, serialNumber?, source? |
intune_list_app_deployments |
Intune app deployments | appName?, publisher?, platform? |
intune_get_app_assignments |
Assignment targets for an app | appId |
intune_troubleshoot_app |
Correlates app assignment + device app status | appId, deviceName?, deviceId?, serialNumber? |
Running Tests
Tests are live integration tests against a real JAMF Pro instance:
export BWS_ACCESS_TOKEN="<your-token>"
bws run --access-token "$BWS_ACCESS_TOKEN" -- \
TEST_COMPUTER_NAME="<name>" \
TEST_COMPUTER_SERIAL="<serial>" \
TEST_USER_EMAIL="<email>" \
npm test
Add JAMF_TEST_WRITE=1 to enable destructive write tests (MDM commands, inventory updates).
Project Structure
├── src/
│ ├── mcp/
│ │ ├── jamf-server.ts # JAMF standalone MCP server (port 3001)
│ │ └── intune-server.ts # Intune standalone MCP server (port 3002)
│ ├── jamf/
│ │ └── jamf-api.ts # JAMF Pro REST + Classic API client
│ ├── intune/
│ │ └── graph-api.ts # Microsoft Graph / Intune client
│ └── utils/
│ └── logger.ts # Output formatting helpers
├── start-jamf.sh # BWS-wrapped launcher for JAMF server
├── start-intune.sh # BWS-wrapped launcher for Intune server
└── bws-secrets.map # Required BWS secret names and descriptions
Additional Resources
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。