Skip to content

Zed sanctions screening mcp server sanctions_resolve_entity

How to: Zed sanctions screening mcp server sanctions_resolve_entity

client:Zed transport:streamable-http tool:sanctions_resolve_entity

Add sanctions screening mcp server to Zed

  1. 01

    Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.

{
  "context_servers": {
    "sanctions-screening-mcp-server": {
      "url": "https://sanctions-screening.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Zed.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that sanctions screening mcp server's identifier in your config matches the one above exactly.

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

sanctions screening mcp server will not start until these are set, so sanctions_resolve_entity never becomes available.

  • MCP_LOG_LEVEL
  • SANCTIONS_MIRROR_PATH
  • SANCTIONS_FUZZY_MIN_SCORE
  • SANCTIONS_NORMALIZE_INPUTS

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.