pinboard-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINBOARD_TOKEN | Yes | Your Pinboard API token in the format username:token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_bookmarkA | 指定した URL を Pinboard にブックマーク保存する。【重要】このツールを呼び出す前に、必ず以下の手順を踏むこと：(1) 記事の主張・背景・具体的な手法・結論・コード例などを網羅した日本語の詳細解説をユーザーに提示する。記事を読まなくても内容を把握できるレベルの情報量を目指し、文字数は制限しない。(2)「ブックマークしますか？」と確認を取る。(3) ユーザーが承認した場合のみ呼び出す。ツールに渡す summary は Pinboard 保存用の 140 コードポイント以内に凝縮した日本語要約であり、ユーザーへの提示内容とは別物にすること。tags は英小文字スラッグ（例: typescript, web-dev）で 1〜5 個とする。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion. save_bookmark has a single, clear purpose.
The single tool name follows a clear verb_object convention. There are no other tools to introduce naming inconsistency.
One tool is a thin but not absurd surface for a bookmarking service. It can support a narrow save-only workflow but feels limited for a full Pinboard MCP.
The Pinboard domain normally includes listing, updating, deleting, and searching bookmarks and tags. With only save_bookmark, users can create bookmarks but not retrieve or manage them, creating significant dead ends.