Skip to main content
Glama
deenesjakoruzh
terryso

mcp-pinterest

by terryso
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Pinterest MCP Server

npm version NPM Downloads

A Model Context Protocol (MCP) server for Pinterest image search and information retrieval.

Features

  • Search for images on Pinterest by keywords

  • Retrieve detailed information about Pinterest images

  • Seamless integration with Cursor IDE through MCP

  • Support for headless browser mode

  • Limit control for search results

  • Search and download images from Pinterest

Related MCP server: FGCLIP-MCP

Prerequisites

Installation

Using NPX (Recommended)

The easiest way to use Pinterest MCP Server is via npx:

npx pinterest-mcp-server

You can configure the server with command-line options:

# Specify download directory
npx pinterest-mcp-server --downloadDir /path/to/downloads

# Specify filename template
npx pinterest-mcp-server --filenameTemplate "pinterest_{id}"

# Specify both options
npx pinterest-mcp-server --downloadDir ./images --filenameTemplate "pinterest_{id}"

Global Installation

To install the package globally and use it directly from the command line:

npm install -g pinterest-mcp-server

After installation, you can run the server with:

pinterest-mcp-server

With the same command line options as the NPX version:

pinterest-mcp-server --downloadDir /path/to/downloads --filenameTemplate "pinterest_{id}"

Installing via Smithery

To install mcp-pinterest for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install mcp-pinterest --client claude

Manual Installation

  1. Clone this repository:

    git clone https://github.com/terryso/mcp-pinterest.git pinterest-mcp-server
cd pinterest-mcp-server

  2. Install dependencies:

    npm install

  3. Build the server:

    npm run build

  4. Run the server:

    npm start

Configuring as MCP Server in Cursor

  1. Open Cursor IDE

  2. Go to Settings (⚙️) > Extensions > MCP

  3. Click "Add Server"

  4. Enter the following details:

    • Name: Pinterest MCP

    • Type: Command

    • Command: node

    • Args: ["/path/to/mcp-pinterest/dist/pinterest-mcp-server.js"]

    或者直接编辑Cursor的MCP配置文件（通常位于~/.cursor/mcp.json），添加以下内容：

    "pinterest": {
  "command": "node",
  "args": ["/path/to/mcp-pinterest/dist/pinterest-mcp-server.js"]
}

  5. Click "Save"

Alternative: Using NPX for Cursor Configuration

You can also configure Cursor to use the npx version of the server:

  1. Open Cursor IDE

  2. Go to Settings (⚙️) > Extensions > MCP

  3. Click "Add Server"

  4. Enter the following details:

    • Name: Pinterest MCP

    • Type: Command

    • Command: npx

    • Args: ["pinterest-mcp-server"]

  5. Click "Save"

Complete Configuration Example with Environment Variables

For the most flexibility, you can configure the server with environment variables in your Cursor MCP configuration:

"pinterest": {
  "command": "npx",
  "env": {
    "MCP_PINTEREST_DOWNLOAD_DIR": "/Users/xxx/Desktop/Images",
    "MCP_PINTEREST_FILENAME_TEMPLATE": "pin_{imageId}_{timestamp}.{fileExtension}",
    "MCP_PINTEREST_PROXY_SERVER": "http://127.0.0.1:7890"
  },
  "args": ["pinterest-mcp-server"]
}

This configuration:

  • Uses npx to run the server

  • Sets a custom download directory on your desktop

  • Uses a custom filename template with both image ID and timestamp

  • Configures a proxy server for users in regions where Pinterest might be blocked

Add this to your ~/.cursor/mcp.json file or set up through the Cursor IDE interface.

Available MCP Functions

The server exposes the following MCP functions:

  • pinterest_search: Search for images on Pinterest by keyword

    • Parameters:

      • keyword: Search term (required)

      • limit: Number of images to return (default: 10)

      • headless: Whether to use headless browser mode (default: true)

  • pinterest_get_image_info: Get detailed information about a Pinterest image

    • Parameters:

      • image_url: URL of the Pinterest image (required)

  • pinterest_search_and_download: Search and download images from Pinterest

    • Parameters:

      • keyword: Search term (required)

      • limit: Number of images to return (default: 10)

      • headless: Whether to use headless browser mode (default: true)

Example Usage in Cursor

Once configured, you can use the Pinterest MCP functions directly in Cursor's AI chat:

Search for robot images on Pinterest

The AI will use the MCP server to search Pinterest and display the results.

Example Screenshot

Pinterest Search Example

Screenshot showing a search for 20 images of 三上悠亚 with all images successfully downloaded.

Development

Project Structure

  • pinterest-mcp-server.ts: Main server file

  • dist/pinterest-mcp-server.js: Built JavaScript file for production

  • package.json: Project configuration and dependencies

Adding New Features

To add new MCP functions:

  1. Modify pinterest-mcp-server.ts

  2. Register new functions using the MCP SDK

  3. Implement the function logic

  4. Rebuild with npm run build

Troubleshooting

  • If the server fails to start, check if the port is already in use

  • Ensure all dependencies are correctly installed with npm install

  • Make sure TypeScript is properly configured with a tsconfig.json file

  • If you encounter build errors, try running npm install -D typescript @types/node

  • Verify network connectivity for Pinterest access

License

This project is licensed under the MIT License - see the LICENSE file for details.

Configuration Options

Command Line Options (NPX Mode)

When using the server via npx, you can configure it using the following command line options:

  • --downloadDir: Specifies the root directory for downloading images

    npx pinterest-mcp-server --downloadDir /path/to/downloads

  • --filenameTemplate: Specifies the filename template for downloaded images

    npx pinterest-mcp-server --filenameTemplate "pin_{imageId}_{timestamp}"

  • --port: Specifies the port for the server to listen on (default: 3000)

    npx pinterest-mcp-server --port 8080

  • --proxyServer: Specifies the proxy server to use for connecting to Pinterest

    npx pinterest-mcp-server --proxyServer "http://127.0.0.1:7890"

You can combine multiple options:

npx pinterest-mcp-server --downloadDir ./images --filenameTemplate "pinterest_{id}" --port 8080 --proxyServer "http://127.0.0.1:7890"

Environment Variables

The server also supports the following environment variables for configuration:

  • MCP_PINTEREST_DOWNLOAD_DIR: Specifies the root directory for downloading images. If not set, the default is the ../downloads directory relative to the server script.

  • MCP_PINTEREST_FILENAME_TEMPLATE: Specifies the filename template for downloaded images. If not set, the default is pinterest_{imageId}.{fileExtension}.

  • MCP_PINTEREST_PROXY_SERVER: Specifies the proxy server to use for connecting to Pinterest. Format should be protocol://host:port, for example http://127.0.0.1:7890 or socks5://127.0.0.1:1080.

These environment variables can be set in several ways:

  1. Directly in your terminal (as shown in the examples below)

  2. In your Cursor MCP configuration through the env field (see Complete Configuration Example)

  3. In a .env file in the project root directory

  4. Through command line options with npx (as shown in the Command Line Options section)

Usage

Setting Download Directory

  1. Using npx with command line options:

npx pinterest-mcp-server --downloadDir /path/to/your/download/directory

  1. Set the download directory using an environment variable:

# Linux/macOS
export MCP_PINTEREST_DOWNLOAD_DIR=/path/to/your/download/directory
npx pinterest-mcp-server

# Windows (CMD)
set MCP_PINTEREST_DOWNLOAD_DIR=C:\path\to\your\download\directory
npx pinterest-mcp-server

# Windows (PowerShell)
$env:MCP_PINTEREST_DOWNLOAD_DIR="C:\path\to\your\download\directory"
npx pinterest-mcp-server

  1. If the environment variable is not set, the server will use the default download directory (relative to the server script's ../downloads).

Setting Filename Template

  1. Using npx with command line options:

npx pinterest-mcp-server --filenameTemplate "pin_{imageId}_{timestamp}.{fileExtension}"

  1. Using an environment variable:

# Linux/macOS
export MCP_PINTEREST_FILENAME_TEMPLATE="pin_{imageId}_{timestamp}.{fileExtension}"
npx pinterest-mcp-server

# Windows (CMD)
set MCP_PINTEREST_FILENAME_TEMPLATE="pin_{imageId}_{timestamp}.{fileExtension}"
npx pinterest-mcp-server

# Windows (PowerShell)
$env:MCP_PINTEREST_FILENAME_TEMPLATE="pin_{imageId}_{timestamp}.{fileExtension}"
npx pinterest-mcp-server

The template supports the following variables:

  • {imageId}: The unique ID of the Pinterest image

  • {fileExtension}: The file extension (e.g., jpg, png)

  • {timestamp}: Current UTC timestamp in YYYYMMDDHHMMSS format

  • {index}: The index number when downloading multiple images (starts from 1)

Example templates:

  • pinterest_{imageId}.{fileExtension} (default)

  • pin_{timestamp}_{imageId}.{fileExtension}

  • pinterest_image_{index}_{imageId}.{fileExtension}

  • {timestamp}_pinterest.{fileExtension}

If the template is invalid (e.g., contains unsupported variables or has mismatched brackets), the server will log a warning and use the default template.

Setting Proxy Server

If you need to use a proxy to access Pinterest (especially in regions where Pinterest might be restricted), you can set the proxy configuration:

  1. Using npx with command line options:

npx pinterest-mcp-server --proxyServer "http://127.0.0.1:7890"

  1. Using an environment variable:

# Linux/macOS
export MCP_PINTEREST_PROXY_SERVER="http://127.0.0.1:7890"
npx pinterest-mcp-server

# Windows (CMD)
set MCP_PINTEREST_PROXY_SERVER=http://127.0.0.1:7890
npx pinterest-mcp-server

# Windows (PowerShell)
$env:MCP_PINTEREST_PROXY_SERVER="http://127.0.0.1:7890"
npx pinterest-mcp-server

Supported proxy protocols:

  • HTTP: http://host:port

  • HTTPS: https://host:port

  • SOCKS4: socks4://host:port

  • SOCKS5: socks5://host:port

The proxy configuration affects both the browser used for searching and the image downloading process.

Notes

  • The server will verify the existence and writability of the download directory when starting. If the directory does not exist, it will attempt to create it; if it cannot be created or written to, the server will exit.

  • Clients should not specify download paths or filename templates through parameters when calling download-related tools, as all downloads will use the server's environment variable configuration or defaults.

  • The server automatically sanitizes filenames by replacing illegal characters (such as /, \, :, *, ?, ", <, >, |) with underscores.

Interface Description

The server provides the following MCP tools:

  1. pinterest_search: Search for Pinterest images by keyword

  2. pinterest_get_image_info: Get detailed information about a Pinterest image

  3. pinterest_search_and_download: Search and download Pinterest images

For detailed interface parameter references, please refer to the MCP tool definitions.

⭐ Star History

Star History Chart

Available Tools

3 tools
pinterest_get_image_infoC

Get Pinterest image information

ParametersJSON Schema
NameRequiredDescriptionDefault
image_urlYesImage URL

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, and the description does not disclose any behavioral traits such as read-only nature, authentication requirements, or rate limits. It merely restates the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no unnecessary words. It is appropriately concise, though it could include more information without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema, but the description does not mention what information is returned. Without output schema, the agent has no indication of the response format or content, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides a description for the single parameter 'image_url' as 'Image URL'. The tool description does not add any additional meaning or context beyond the schema. With 100% schema coverage, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'Pinterest image information', distinguishing it from sibling tools like search and search_and_download. However, it does not specify what information is retrieved, which could be improved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. For instance, it could mention that this is used after searching to fetch details for a specific image.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

pinterest_search_and_downloadB

Search for images on Pinterest by keyword and download them

ParametersJSON Schema
NameRequiredDescriptionDefault
keywordYesSearch keyword
limitNoNumber of images to return and download (default: 10)
headlessNoWhether to use headless browser mode (default: true)

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavior. It only states the action, not side effects (e.g., file saving location, format, or any destructive operations). Minimal behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, efficient sentence with no wasted words. Could be slightly more structured but overall well-sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that downloads images, missing details on output format, file saving behavior, and how it differs from sibling tools. Incomplete for an agent to reliably invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds no extra meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'search and download' and resource 'images on Pinterest by keyword'. It distinguishes from siblings by combining both actions, though not explicitly differentiating from pinterest_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs siblings. The context is implied by the name and description, but lacks when-not-to-use or alternative mentions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0
Disambiguation5/5

Each tool has a distinct purpose: retrieving metadata, searching, and searching with download. The names and descriptions make it easy to distinguish between them.

Naming Consistency4/5

All tools use the 'pinterest_' prefix and snake_case, but 'pinterest_search_and_download' combines two verbs while the others use a single verb, introducing slight inconsistency.

Tool Count4/5

Three tools is a minimal but reasonable set for an image search and download service. It covers core functionality without being too sparse or excessive.

Completeness3/5

The set covers basic search and metadata retrieval, but lacks common Pinterest operations like board management, pinning, or user actions, leaving notable gaps for broader use.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/terryso/mcp-pinterest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server