@striderlabs/mcp-pinterest
Related Servers
Alternatives to @striderlabs/mcp-pinterest
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that lets Claude interact with Pinterest — browsing, creating, and managing boards, pins, sections, and user profiles via the Pinterest API v5.1526 npmMIT
- AlicenseAqualityCmaintenanceA minimal MCP server for the Pinterest API v5 that reads boards, pins, and analytics and publishes new pins and boards, with human sign-off required before any public changes.8MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for exposing Pinterest boards, sections, pins, and imagery as a visual reference library. Enables ChatGPT and other clients to list, search, and retrieve Pinterest content through natural language.MIT
- AlicenseAqualityDmaintenanceMCP server connector for YouTube — search videos, manage playlists, subscriptions, and watch history via Playwright browser automation.1015 npmMIT
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to Pinterest data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcp5MIT
- AlicenseAqualityAmaintenanceMCP server for parsing, validating, classifying, and normalizing Pinterest URLs locally, supporting pins, profiles, boards, and ideas URLs across Pinterest country domains without network requests.334 npmMIT
TDQS
Scored across 10 tools
Tools are mostly distinct, but get_user_boards and get_my_boards both retrieve boards, differing only by user scope. get_board retrieves pins from a specific board, while get_user_boards lists boards, so the boundary is clear with descriptions.
All tool names follow a consistent verb_noun pattern in lower_snake_case (search_, get_, save_, create_, follow_). No mixed conventions or vague verbs like 'process' or 'run'.
10 tools is well within the ideal 3-15 range for a domain-specific server. Each tool covers a distinct Pinterest action, and there is no redundancy or bloat.
The surface covers core Pinterest workflows: searching, viewing pins/boards, saving pins, creating boards, following users, and feed/trending. Missing update/delete operations for pins and boards, but these are less critical and can be worked around.