Magicsword MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 548 installs a week from npm. Last commit 29 Oct 2026.
Manage MagicSword endpoints, alerts, policies, and private intelligence through MCP.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const result = spawnSync(cli, args, { encoding: 'utf8', timeout: 30_000, windowsHide: true, maxBuffer: 1024 * 1024 });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add magicsword-mcp -e 'MAGICSWORD_API_KEY=<MAGICSWORD_API_KEY>' -- npx -y @magicsword-io/magicsword-mcp
{
"mcpServers": {
"magicsword-mcp": {
"command": "npx",
"args": [
"-y",
"@magicsword-io/magicsword-mcp"
],
"env": {
"MAGICSWORD_API_KEY": "<MAGICSWORD_API_KEY>"
}
}
}
}
[mcp_servers.magicsword-mcp]
command = "npx"
args = ["-y", "@magicsword-io/magicsword-mcp"]
env = { MAGICSWORD_API_KEY = "<MAGICSWORD_API_KEY>" }
{
"mcpServers": {
"magicsword-mcp": {
"command": "npx",
"args": [
"-y",
"@magicsword-io/magicsword-mcp"
],
"env": {
"MAGICSWORD_API_KEY": "<MAGICSWORD_API_KEY>"
}
}
}
}
{
"servers": {
"magicsword-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@magicsword-io/magicsword-mcp"
],
"env": {
"MAGICSWORD_API_KEY": "<MAGICSWORD_API_KEY>"
}
}
}
}
Put your own value in place of
<MAGICSWORD_API_KEY> (MagicSword Customer API key from Portal settings).
The author’s registry entry marks it as required.
ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests.
Manage incidents, on-call schedules, escalation policies, and alert notifications
Market & competitive intelligence for Claude & AI assistants: trends, alerts, keywords & more.
Competitive intelligence and technology monitoring: alerts, sources and news.
AI-powered website change monitoring - manage monitors and alerts via MCP.
Remote MCP server for hotel rate monitoring, parity checks, and pricing intelligence via Apify.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
Track page and price changes over time: diffs, history, and alerts through simple tracking
Answers built from our own checks of this server.