Local Pinboard MCP Server

A locally-hosted MCP server that connects your AI assistant to Pinboard. Exposed over MCP by the local pinboard mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A locally-hosted Model Context Protocol server that connects your Pinboard account to any MCP-compatible AI assistant (such as Claude Desktop, Cursor, or similar tools).

Its toolset

Everything the assistant can do here goes through one of these:

• get_recent_posts — List your most recent Pinboard bookmarks, optionally filtered by up to three tags
• get_posts — Retrieve bookmarks matching a tag, a specific date, or a specific URL
• get_all_posts — Retrieve all bookmarks in your Pinboard account. Rate limited to once every 5 minutes
• add_post — Add or replace a bookmark. URL and title are required. By default, replaces any existing bookmark for the same URL
• delete_post — Permanently delete a bookmark by its URL. This action cannot be undone
• suggest_tags — Return popular (site-wide) and recommended (your history) tags for a given URL
• get_tags — Get all of your Pinboard tags with their usage counts. No parameters
• rename_tag — Rename a tag across all bookmarks, or fold it into an existing tag
• delete_tag — Delete a single tag from your account. Removes the tag from all bookmarks but does not delete them
• list_notes — List all of your notes (without body text). No parameters. Note creation/editing is unsupported in v1 API
• get_note — The get_note tool exposed by this server
• get_last_update — Returns the time of the most recent bookmark change. Use this to check if data has changed since your last fetch. No parameters

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: PINBOARD_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Local Pinboard MCP's toolset — get_recent_posts, get_posts, get_all_posts and 9 more — is a fair guide to whether it matches your workflow. It is maintained by mattriffle; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Local Pinboard MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Local Pinboard MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the local pinboard mcp mcp server does with a few real requests.