valv MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  execFileSync(process.execPath, [cliPath, ...args], {

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  execFileSync(process.execPath, [cliPath, ...args], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 mcp -- npx -y @valv/mcp

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@valv/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@valv/mcp"]

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@valv/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@valv/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: DATABASE_URL (Database connection string. PostgreSQL, MySQL, SQLite, CockroachDB, or a ClickHouse HTTP URL.), VALV_PROVIDER (Datasource provider: postgresql, mysql, sqlite, or clickhouse. Inferred from DATABASE_URL when omitted.), VALV_DATABASE (Database name. Required for ClickHouse, whose URL does not carry one.), VALV_TABLES (Comma-separated allow-list of tables. When set, only these are exposed to the agent.), VALV_EXCLUDE (Comma-separated deny-list of tables, applied after the allow-list.), VALV_POLICY_FILE (Path to a policy module that takes full control of access. Without it, the server is read-only across all tables.), VALV_CONTEXT (JSON context object the policy reads, e.g. {"tenant":{"id":"acme"}}.), VALV_HTTP_PORT (Serve over Streamable HTTP on this port instead of stdio.). The author declared them in the registry entry; get the values from the project itself.