Skip to content

Cursor Umbra open SAR archive stack_provenance

How to: Cursor Umbra open SAR archive stack_provenance

client:Cursor transport:streamable-http tool:stack_provenance

Add Umbra open SAR archive to Cursor

  1. 01

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

{
  "mcpServers": {
    "umbra-mcp": {
      "url": "https://api.umbra-py.space/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Umbra open SAR archive'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

Umbra open SAR archive will not start until these are set, so stack_provenance never becomes available.

  • UMBRA_CANOPY_TOKEN
  • UMBRA_INDEX_DB
  • ANTHROPIC_API_KEY
  • OPENAI_API_KEY

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.