Pinboard MCP integration for AI agents.
Connect AI agents to Pinboard through 6 structured actions, including get bookmarks, add bookmark, and delete bookmark. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Pinboard integration exposes
The Pinboard Agent App exposes 6 provider-backed actions for productivity and social work. Its current contract lets an authorized agent get pinboard bookmarks for a url, date, or up to three tags using the posts/get endpoint, add or replace a pinboard bookmark, and delete a pinboard bookmark by url. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Pinboard account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Pinboard capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_bookmarksREADGet Pinboard bookmarks for a URL, date, or up to three tags using the posts/get endpoint.
INPUTS: url / tags / date / includeMeta
add_bookmarkWRITEAdd or replace a Pinboard bookmark.
INPUTS: url / title / description / tags / createdAt
delete_bookmarkHIGH IMPACTDelete a Pinboard bookmark by URL.
INPUTS: url
get_last_updateREADGet the most recent time a Pinboard bookmark was added, updated, or deleted.
list_recent_bookmarksREADList the user's most recent Pinboard bookmarks, optionally filtered by one tag.
INPUTS: tag / count
list_tagsREADList the user's Pinboard tags and bookmark counts.
INPUT CONTRACTS
Know what the action needs before it runs.
get_bookmarks
urlOPTIONAL- Return the bookmark for this exact URL.
tagsOPTIONAL- Up to three tags to filter by. Pinboard treats multiple tags as a combined tag filter.
dateOPTIONAL- Return bookmarks created on this UTC date.
includeMetaOPTIONAL- Whether to include Pinboard change detection signatures.
add_bookmark
urlREQUIRED- The URL to bookmark.
titleREQUIRED- The bookmark title. Pinboard calls this field description.
descriptionOPTIONAL- The optional bookmark description or extended text.
tagsOPTIONAL- Pinboard tags to match or attach. Multiple tags are joined with spaces for the upstream API.
createdAtOPTIONAL- The bookmark creation time in UTC.
delete_bookmark
urlREQUIRED- The bookmarked URL to delete.
list_recent_bookmarks
tagOPTIONAL- A tag to filter by.
countOPTIONAL- The number of bookmarks to return. Pinboard allows up to 100.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Bookmarks
Get Pinboard bookmarks for a URL, date, or up to three tags using the posts/get endpoint. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_bookmarksControl Add Bookmark
Add or replace a Pinboard bookmark. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_bookmarkVerify with Get Last Update
Get the most recent time a Pinboard bookmark was added, updated, or deleted. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_last_updateSAFETY BOUNDARY
Operate Pinboard with explicit limits
- Authorize Pinboard with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_bookmark` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Pinboard rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Pinboard task completed successfully.
CONNECTION MODEL
API key
Pinboard API token in username:TOKEN form, sent as the auth_token query parameter. Find it on the Pinboard password settings page: https://pinboard.in/settings/password
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Pinboard.