Cursor cisa cybersecurity mcp server cisa_get_alerts
How to: Cursor cisa cybersecurity mcp server cisa_get_alerts
Add cisa cybersecurity mcp server to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"cisa-cybersecurity-mcp-server": {
"url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something cisa_get_alerts does. Cursor lists the server's tools on connect and calls cisa_get_alerts itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that cisa cybersecurity mcp server's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
cisa cybersecurity mcp server will not start until these are set, so cisa_get_alerts never becomes available.
-
MCP_LOG_LEVEL -
CISA_KEV_REFRESH_CRON -
CISA_CSAF_MIRROR_PATH -
CISA_CSAF_MIRROR_AUTO_INIT -
CISA_CSAF_REFRESH_CRON -
CISA_VULNRICHMENT_CACHE_TTL_SECONDS -
CISA_FEED_CACHE_TTL_SECONDS -
CISA_HTTP_TIMEOUT_MS
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.