The Digback MCP server for your saved links
The Digback MCP server lets Claude and other MCP apps use your saved links as a tool. They can search your board by meaning, read a pin in full, write descriptions and tags, sort pins onto boards and save new links. It is a remote server over Streamable HTTP at app.digback.com/mcp, and it needs a personal token, not an AI key.
What can an AI app do with Digback over MCP?
Once connected, you just ask in plain words:
- “Find the Docker tutorials I saved last year.”
- “What did I save about Postgres indexes?”
- “Go through my pins that have no description and write one for each.”
- “Put everything tagged recipe on a board called Cooking.”
- “Make a smart board of design tools I saved from Reddit.”
- “Save this link with the note: pricing page to copy.”
Behind those, the server has 12 tools:
| Tool | What it does |
|---|---|
search_pins | Search saved links by meaning and by words at the same time, with filters for source, tag, board, type and date |
list_pins | Walk through pins by category, like needs_description, needs_image, no_board or inbox |
get_pin | One pin in full, including the text Digback pulled off the page |
similar_pins | Other pins on the same subject as one pin, each with why it matched |
update_pin | Change the title, description, image, tags, note or boards of one pin |
bulk_update_pins | Write descriptions, tags or images onto up to 25 pins in one call |
refetch_images | Ask Digback to fetch missing pictures itself, in the background |
add_pin | Save a new link, with a note, tags and boards |
list_boards | Every board, plus the total number of pins |
create_board | Make a board, or a smart board that fills itself from a search |
list_tags | Every tag with how many pins use it |
board_stats | Counts by source and status, and how many pins still need work |
There is no delete tool, on purpose.
How do I connect it?
Two steps: make a token in Digback, then give it to your app.
Step 1: make a token
Open Digback, go to Settings, then Claude (MCP), and press Create token. The token is shown once, so copy it then. Digback keeps only a hash of it. If you lose it, make a new one, and the old one stops working straight away.
Step 2: add Digback to your app
In every snippet below, replace YOUR_TOKEN with your token.
Claude Code
Run this in your terminal:
claude mcp add --transport http digback https://app.digback.com/mcp --header "Authorization: Bearer YOUR_TOKEN"
Check it with claude mcp list.
Claude Desktop and claude.ai
The connector screen cannot send a header, so use the address that carries the token. Open Settings, then Connectors, then Add custom connector, and paste:
https://app.digback.com/mcp/t/YOUR_TOKEN
Treat that address like a password, because it holds one. If it gets out, make a new token in Settings.
Claude Desktop with mcp-remote
If you would rather send a header, put this in claude_desktop_config.json:
{
"mcpServers": {
"digback": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://app.digback.com/mcp",
"--header",
"Authorization: Bearer YOUR_TOKEN"
]
}
}
}
Cursor
Add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"digback": {
"url": "https://app.digback.com/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
VS Code with Copilot
Add this to .vscode/mcp.json in your project:
{
"servers": {
"digback": {
"type": "http",
"url": "https://app.digback.com/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
Other apps
Digback’s Settings, Claude (MCP) screen builds the exact snippet for each of these, with your token already in it:
- ChatGPT: switch on Developer mode, create a connector, paste the address with the token inside it, and pick No authentication.
- Codex CLI:
codex mcp add digback --url https://app.digback.com/mcp --bearer-token-env-var DIGBACK_TOKEN - Gemini CLI:
gemini mcp add --transport http --header "Authorization: Bearer YOUR_TOKEN" digback https://app.digback.com/mcp - Windsurf, Antigravity and Zed: a JSON block for their MCP config file.
The Claude setups above are the ones written up and checked. The others follow each app’s own MCP format; if one does not connect, write to [email protected].
How does the server work?
| Detail | Value |
|---|---|
| Address | https://app.digback.com/mcp |
| Address for apps that only take a URL | https://app.digback.com/mcp/t/YOUR_TOKEN |
| Transport | Streamable HTTP, stateless, JSON responses |
| Auth | Personal token as a Bearer header, or inside the address |
| Rate limit | 60 calls a minute per token |
| Server name | digback |
| Tools | 12, with no delete tool |
A token reaches only the pins of the person who made it. Every call is recorded, and Settings, Claude (MCP) shows the last 50, so you can see what an app did and when.
Why use MCP for saved links?
Because you already ask an AI app questions all day. With Digback connected, “what was that tool I saved for resizing images” gets answered from your own saves, not from the whole web. And the boring jobs, like writing a line for 200 pins with no description, can be handed over in one sentence.