MagicSword MCP / Enterprise
Investigate your fleet. Shape your policies. Bring your intelligence. Put real MagicSword tools behind the questions you already ask.
Already have Enterprise? You need an API key from Settings.
New to MagicSword? Create your account or talk to us about Enterprise.
Connect once. Start asking.
Requires MagicSword Enterprise and a supported local MCP client. Terminal setup requires Node.js 22 or later. Setup connects your assistant to your organization.
In Settings → API Keys, select New API Key. Name it for your assistant and copy the key when it appears. An organization admin must create it.
Start with the default read scopes for policies, alerts, and endpoints. Add intelligence or write scopes when you need those workflows; each example below lists its permissions.
Open API key settingsThis is an API key, separate from the one-time token used to enroll your device. Enter it in the installer’s API-key field or the private terminal setup prompt. Keep it out of assistant conversations.
Run this in Terminal, PowerShell 7+, or Command Prompt on the computer where you use your assistant. Setup privately prompts for your API key and saves it locally.
npm install -g @magicsword-io/magicsword-mcp && magicsword-mcp configure --client claude-desktopRestart Claude Desktop after setup, then enable MagicSword in your conversation.
On Windows PowerShell 5.1, run the two commands separately, replacing && with a new line.
First conversation
Restart your client or start a new session. Ask your assistant to check both authentication and device access. A tool appearing in the list alone does not confirm access.
Use MagicSword to call whoami, then list_endpoints. Show the connected organization, my approved permissions, and my devices. Do not make any changes.
The current MagicSword package runs on your computer. It connects to Claude Desktop and the local clients above. Web connectors need a remotely reachable MCP server; this package does not provide one. Use a supported local client to get started today.
Read the current compatibility guideWhat will you ask first?
Explore with read access. When you are ready to make changes, use a connection or key with the matching permissions and review the proposal before asking your assistant to apply it. Policy assignments, enforcement switches, and upgrades include explicit confirmation steps.
01 / FLEET
List devices, inspect agent health, and see which policy each endpoint is running.
Use MagicSword to list my endpoints. Summarize their platforms, agent versions, and policy assignments. Show devices that need attention. Do not make changes.
Permissions: endpoints:read
Tools include: list_endpoints, show_endpoint
02 / INVESTIGATE
Search audit events and triage alerts with file, publisher, and device context.
Use MagicSword to find audited or blocked events from the last 24 hours and unacknowledged critical alerts. Investigate the highest-priority alert and explain the affected devices and evidence. Do not acknowledge, dismiss, or change anything.
Permissions: alerts:read
Tools include: list_events, find_alerts, triage_alert
03 / POLICY
Add or update rules on an existing policy using selected audit events or explicit rules.
Use MagicSword to list my Windows policies and recent audit events. Help me choose an existing policy and identify software to allow or block. Show the proposed rule changes and wait for my approval before applying them.
Permissions: policies:read, alerts:read, policies:write
Tools include: list_policies, manage_policy_rules
04 / ROLLOUT
Preview assigning an existing policy to enrolled devices. Confirm the targets before applying it.
Use MagicSword to list my existing Audit policies and enrolled Windows devices. Help me choose a policy and a small test group, then preview the assignment. Show the policy mode and exact devices. Wait for my approval before applying it. Keep the policy in Audit mode.
Permissions: policies:read, endpoints:read, policies:write
Tools include: apply_policy_to_endpoints
05 / INTELLIGENCE
Discover sources, create private feeds, update indicators, and attach feeds to policies.
Use MagicSword to list available intelligence sources, my private feeds, and my Windows policies. Help me choose a policy and a compatible source to attach, or draft a private feed for indicators I provide. Show the exact changes and wait for my approval before writing anything.
Permissions: intel:read, policies:read, intel:write, policies:write
Tools include: list_intel_sources, manage_customer_intel_feed, upsert_customer_intel_items, manage_policy_intel_sources
06 / OPERATIONS
Compare installed agent versions with available releases and preview a targeted upgrade.
Use MagicSword to compare my endpoint agent versions with available releases. Help me choose a small test group and preview an upgrade. Show the targets and proposed version. Wait for my approval before queueing any upgrades.
Permissions: endpoints:read, endpoints:write
Tools include: list_agent_releases, upgrade_endpoints
Create your initial policy in the portal, then use MCP to update its rules, attach intelligence, and assign it to enrolled agent-managed devices. MCP currently works with existing policies. Source availability also depends on your organization’s entitlements.
Explore every MCP tool