Magicsword MCP server
io.github.magicsword-io/magicsword-mcp·v0.1.6Manage MagicSword endpoints, alerts, policies, and private intelligence through MCP.
not scanned yet
0 stars623 downloads/wk
Reviews
Write oneNobody has reviewed Magicsword yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Magicsword tools
No tool declarations could be read from the package source. They show once the server is installed.
How Magicsword compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- Downloads a week
- 623
- more than 91% of 12,191 servers with a package
Release history: 5 versions in the registry since 2026-10-07, latest 2026-11-03, typically one every 4 days.
Install Magicsword in Claude Code, Cursor or VS Code
Runs npx -y @magicsword-io/magicsword-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add magicsword-mcp -- npx -y @magicsword-io/magicsword-mcp
What the publisher says
From the Magicsword repository's README, as published. We do not edit it. Read it on GitHub
magicsword-mcp
A Model Context Protocol server for MagicSword. Lets users running Claude Desktop, Cursor, or any MCP-aware client manage MagicSword conversationally — list endpoints, query alerts, triage findings, mint enrollment tokens, and preview / commit policy changes.
The server is a thin, opinionated wrapper around the /api/public/v1/ customer API exposed by the Magic Portal. It runs on the user's machine, holds an msk… API key, and speaks MCP over stdio.
Plan gate. The customer API is Enterprise-only. With a pilot-tier key
the server returns a clear "this MagicSword org needs the Enterprise plan
to use MCP" message; nothing else works until the org is upgraded.
Quick start
Requires Node.js 22+, an installed MCP client, and a MagicSword Enterprise API key from Magic Portal → Settings → API Keys.
Recommended: install and connect your client in one command. Setup prompts for your key privately and lets you choose Claude Desktop, Codex, Claude Code, or Cursor:
npm install -g @magicsword-io/magicsword-mcp && magicsword-mcp configureAlready know your client? Run the matching one-liner:
Prefer your client's own registration command? After saving your key locally, these also work without a global server install:
codex mcp add magicsword --env MAGICSWORD_BASE_URL=https://www.magicsword.io -- npx -y @magicsword-io/magicsword-mcp
claude mcp add --scope user --transport stdio magicsword --env MAGICSWORD_BASE_URL=https://www.magicsword.io -- npx -y @magicsword-io/magicsword-mcpThese are also a fallback when automatic registration cannot launch a client's CLI on Windows. Desktop launch still requires Node/npx to be available to that client; the recommended setup uses absolute paths instead.
Install buttons: Cursor and VS Code
First save your API key locally (once per machine):
npm install -g @magicsword-io/magicsword-mcp && magicsword-mcp configure --client manualThen click your client's button and approve its installation prompt:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Magicsword: common questions
- Is Magicsword MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Magicsword safety report
- How do I install Magicsword?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Magicsword need an API key?
- Yes. The registry entry asks for
MAGICSWORD_API_KEY. - Is Magicsword maintained?
- The last commit was 27 days ago (2026-10-07). The latest release is v0.1.6.
- How does Magicsword compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); downloads a week 623 (more than 91% of 12,191 servers with a package). Full comparison.