linkding

This MCP server acts as a bridge for a self-hosted Linkding instance. It exposes maintenance and integration tools to manage bookmarks, search indexing, or other Linkding interactions through the MCP protocol. The provided example uses a compiled binary built from the source; you can run the binary directly or use the JavaScript/JSR-based variant described in the README. To operate, start the server container or executable and connect other MCP clients to the documented endpoint. Provide the Linkding URL and an API key via environment variables so the MCP server can authenticate with the Linkding REST API.

The server's available tools rely on the Linkding API, enabling operations such as listing, creating, updating, or deleting bookmarks and interacting with tag and folder structures as supported by Linkding. If you opt to use the deno/jsr route, you can load the server module from the published package and run it through deno run with the appropriate environment configuration. Ensure your Linkding instance is accessible from the host running the MCP server and that the API key has the necessary permissions for the actions you intend to perform.

Prerequisites:

• A running environment (Linux/macOS/Windows) with network access to your Linkding instance
• Deno installed if you choose to compile from source using the deno task
• Optional: Node.js if you prefer running via deno.jsr package formatting (see alternatives in README)

Installation steps (compiled binary approach):

1. Clone the MCP server repository:

git clone https://github.com/uta8a/linkding-mcp-server.git
cd linkding-mcp-server

2. Compile the server to generate the dist/main binary:

deno task compile

3. Start the MCP server (replace with your actual path):

/path/to/linkding-mcp-server/dist/main

4. Configure your MCP client to point to the server and provide the required env vars:

"mcpServers": {
  "linkding-mcp-tools": {
    "command": "/path/to/linkding-mcp-server/dist/main",
    "env": {
      "LINKDING_URL": "https://your-linkding.example.com",
      "LINKDING_API_KEY": "xxx"
    }
  }
}

Alternative (deno/jsr package):

1. Ensure Deno is installed.
2. Run the server using the JSR package as shown in the README:

"mcpServers": {
  "linkding-mcp-tools": {
    "command": "/path/to/deno",
    "args": [
      "run",
      "-Ar",
      "jsr:@uta8a/linkding-mcp-server/server"
    ],
    "env": {
      "LINKDING_URL": "https://your-linkding.example.com",
      "LINKDING_API_KEY": "xxx"
    }
  }
}

Notes:

• Ensure LINKDING_URL uses the public URL of your Linkding instance and that the API key has the necessary permissions in Linkding's REST API integrations.
• If you switch from a compiled binary to the deno/jsr route, adjust the command and args accordingly in your MCP config.
• Firewalls or reverse proxies between the MCP server and Linkding may require proper TLS termination and health checks.
• Keep the API key secure; do not commit it to version control or expose it in logs.