@striderlabs/mcp-pinterest
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINTEREST_EMAIL | Yes | Your Pinterest email address | |
| PINTEREST_HEADLESS | No | Set to 'false' to see browser | true |
| PINTEREST_PASSWORD | Yes | Your Pinterest password |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pinsC | Search for pins on Pinterest by query. |
| get_pin_detailsA | Get detailed information about a specific pin. |
| get_boardB | Get pins from a specific board. |
| get_user_boardsA | Get boards for a Pinterest user. |
| save_pinC | Save a pin to one of your boards. |
| create_boardB | Create a new board. |
| follow_userC | Follow a Pinterest user. |
| get_home_feedA | Get personalized home feed pins. |
| get_trendingB | Get trending pins and ideas on Pinterest. |
| get_my_boardsB | Get the authenticated user's boards. |
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 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.