Engrava MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add engrava -e 'ENGRAVA_DB_PATH=<ENGRAVA_DB_PATH>' -- uvx engrava-mcp

{
  "mcpServers": {
    "engrava": {
      "command": "uvx",
      "args": [
        "engrava-mcp"
      ],
      "env": {
        "ENGRAVA_DB_PATH": "<ENGRAVA_DB_PATH>"
      }
    }
  }
}

[mcp_servers.engrava]
command = "uvx"
args = ["engrava-mcp"]
env = { ENGRAVA_DB_PATH = "<ENGRAVA_DB_PATH>" }

{
  "mcpServers": {
    "engrava": {
      "command": "uvx",
      "args": [
        "engrava-mcp"
      ],
      "env": {
        "ENGRAVA_DB_PATH": "<ENGRAVA_DB_PATH>"
      }
    }
  }
}

{
  "servers": {
    "engrava": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "engrava-mcp"
      ],
      "env": {
        "ENGRAVA_DB_PATH": "<ENGRAVA_DB_PATH>"
      }
    }
  }
}

Put your own value in place of <ENGRAVA_DB_PATH> (Absolute path to the SQLite database file. Created if missing; its directory must exist. Enough on its own: full-text search, the graph and MindQL work, but vector search needs ENGRAVA_MCP_CONFIG). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: ENGRAVA_MCP_CONFIG (Absolute path to an engrava.yaml, for an embedding provider (vector search) and the thought/edge journal. When set, it takes precedence and ENGRAVA_DB_PATH is not read), ENGRAVA_MCP_READ_ONLY (Set to true to register no write tools).