linkding
MCP Server for Linkding self-hosted bookmarking service
claude mcp add --transport stdio chickenzord-linkding-mcp docker run --rm -i ghcr.io/chickenzord/linkding-mcp:latest stdio \ --env LINKDING_URL="https://your-linkding.example.com" \ --env LINKDING_API_TOKEN="your-api-token"
How to use
This MCP server exposes tools to interact with your Linkding bookmarks via the MCP (Model Context Protocol) interface. It supports three main actions: searching bookmarks, creating new bookmarks, and retrieving existing tags. You can run the server in stdio mode for direct command/response interactions, or in HTTP mode if you deploy it behind a web server. With stdio, you’ll issue MCP tool calls through your MCP client and receive structured responses; with HTTP, you’ll access endpoints that map to the same underlying tools. Typical workflows include asking the AI to search for bookmarks related to a topic, adding a new bookmark with a title and tags, or listing your current tags to refine search or categorization.
How to install
Prerequisites:
- A running Linkding instance (self-hosted) with an API token generated from the admin panel.
- Docker installed on the host (recommended for ease of use). Alternatively, you can build from source or install via Homebrew as shown in the repository README.
Option A: Docker (recommended)
- Pull and run the MCP server in stdio mode:
docker pull ghcr.io/chickenzord/linkding-mcp:latest
docker run --rm -i
-e LINKDING_URL="https://your-linkding.example.com"
-e LINKDING_API_TOKEN="your-api-token"
ghcr.io/chickenzord/linkding-mcp:latest stdio
Option B: Local binary (if you build from source)
- Ensure Go is installed and Linkding is accessible.
- Build the binary: go build -o linkding-mcp ./cmd/linkding-mcp
- Run in stdio mode: ./linkding-mcp stdio
Option C: HTTP mode (after building or using Docker image)
- Run the server to listen on a port, e.g. 8080, and expose the Linkding credentials via environment variables:
-e LINKDING_URL="https://your-linkding.example.com"
-e LINKDING_API_TOKEN="your-api-token"
-e BIND_ADDR=":8080" - Access MCP endpoints over HTTP per the MCP spec.
Additional notes
Environment variables:
- LINKDING_URL: URL of your Linkding instance (required)
- LINKDING_API_TOKEN: API token for Linkding (required)
- BIND_ADDR: HTTP server bind address (default is :8080 in HTTP mode) Security: When using HTTP mode, consider placing the MCP server behind an API gateway or reverse proxy and restrict access to trusted clients. If running in Docker, ensure the container has network access to your Linkding instance. The MCP tools exposed are:
- search_bookmarks: query and limit parameters
- create_bookmark: url, title, description, tags
- get_tags: limit If you need to adjust defaults, you can modify the tool call parameters in your MCP client configuration.
Related MCP Servers
mcp-language
mcp-language-server gives MCP enabled clients access semantic tools like get definition, references, rename, and diagnostics.
flux-operator
GitOps on Autopilot Mode
lingti-bot
🐕⚡ 「极简至上 效率为王 一次编译 到处执行 极速接入」的 AI Bot
kodit
👩💻 MCP server to index external repositories
github-brain
An experimental GitHub MCP server with local database.
bgg
BGG MCP provides access to BoardGameGeek and a variety of board game related data through the Model Context Protocol. Enabling retrieval and filtering of board game data, user collections, and profiles.