Laver 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 laver-mcp -e 'LAVER_API_KEY=<LAVER_API_KEY>' -- npx -y @laver/mcp

{
  "mcpServers": {
    "laver-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@laver/mcp"
      ],
      "env": {
        "LAVER_API_KEY": "<LAVER_API_KEY>"
      }
    }
  }
}

[mcp_servers.laver-mcp]
command = "npx"
args = ["-y", "@laver/mcp"]
env = { LAVER_API_KEY = "<LAVER_API_KEY>" }

{
  "mcpServers": {
    "laver-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@laver/mcp"
      ],
      "env": {
        "LAVER_API_KEY": "<LAVER_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "laver-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@laver/mcp"
      ],
      "env": {
        "LAVER_API_KEY": "<LAVER_API_KEY>"
      }
    }
  }
}

Put your own value in place of <LAVER_API_KEY> (A workspace-scoped API key, created in Laver under Admin → API keys. It acts as the person who created it, so it holds exactly their access and can be revoked without touching their account. Supply this or LAVER_API_KEY_FILE). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: LAVER_API_KEY_FILE (Alternative to LAVER_API_KEY: a path to a file holding nothing but the key, or a .env-style file carrying a LAVER_API_KEY= line. Use this to keep the key out of your client's config file), LAVER_API_URL (Overrides the API host. Defaults to https://api.laver.app, and must be https except for localhost).