Skip to content

Cline cisa cybersecurity mcp server cisa_list_reference

How to: Cline cisa cybersecurity mcp server cisa_list_reference

client:Cline transport:streamable-http tool:cisa_list_reference

Add cisa cybersecurity mcp server to Cline

  1. 01

    Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "cisa-cybersecurity-mcp-server": {
      "url": "https://cisa-cybersecurity.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cline.

  2. 03

    Ask for something cisa_list_reference does. Cline lists the server's tools on connect and calls cisa_list_reference itself — you do not invoke it by name.

  3. 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.

Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs

Set these first

cisa cybersecurity mcp server will not start until these are set, so cisa_list_reference never becomes available.

  • CISA_CLAMP_OVERSIZED_INPUTS
  • 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 14 November 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.