Skip to content

Cline APIShield WAF v4.0 MCP Resource/APIShield WAF v4.0 x402 v2 Manifest

How to: Cline APIShield WAF v4.0 MCP APIShield WAF v4.0 x402 v2 Manifest

client:Cline transport:streamable-http resource:APIShield WAF v4.0 x402 v2 Manifest

Add APIShield WAF v4.0 MCP 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": {
    "mcp": {
      "url": "https://apishield-waf.run402.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cline.

  2. 03

    APIShield WAF v4.0 x402 v2 Manifest is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that APIShield WAF v4.0 MCP is connected and that you are looking at its resources rather than its tools.

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

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 18 October 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.