Linkwarden MCP Server

What the code does

We read the source, 3 d ago · rules ccca72095570

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.

  'metadata.google.internal',

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 linkwarden-mcp -- npx -y linkwarden-mcp

{
  "mcpServers": {
    "linkwarden-mcp": {
      "args": [
        "-y",
        "linkwarden-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.linkwarden-mcp]
command = "npx"
args = ["-y", "linkwarden-mcp"]

{
  "mcpServers": {
    "linkwarden-mcp": {
      "args": [
        "-y",
        "linkwarden-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "linkwarden-mcp": {
      "args": [
        "-y",
        "linkwarden-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: LINKWARDEN_URL (Base URL of the Linkwarden instance, e.g. https://links.example.net (without /api/v1)), LINKWARDEN_TOKEN (Access token from Settings -> Access Tokens), LINKWARDEN_READ_ONLY (Set to true to register only the 11 read tools and no write tools), LINKWARDEN_ALLOW_TOOLS (Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)), LINKWARDEN_DENY_TOOLS (Comma-separated tool names or list_* prefixes to remove from whatever LINKWARDEN_ALLOW_TOOLS left), LINKWARDEN_INSECURE_TLS (Set to true to accept self-signed certificates for this connection only). The author declared them in the registry entry; get the values from the project itself.