Skip to content
mcp/harbor

Cursor California Slip & Fall Evidence Checker | JSM Injury Firm check_slip_fall_evidence

How to: Cursor California Slip & Fall Evidence Checker | JSM Injury Firm check_slip_fall_evidence

client:Cursor transport:streamable-http tool:check_slip_fall_evidence

Add California Slip & Fall Evidence Checker | JSM Injury Firm to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "caslipandfall-com": {
      "url": "https://caslipandfall.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that California Slip & Fall Evidence Checker | JSM Injury Firm'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

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.

California Slip & Fall Evidence Checker | JSM Injury Firm MCP server