Pinterest Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

MCP server for Pinterest: account, boards, pins. Needs a free Pinterest access token.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that connects an assistant to Pinterest accounts, boards and pins, using a free Pinterest access token.

What you can do
Work with Pinterest account data through the assistant, including account details, boards and pins, as described for this server. It runs locally over stdio and is intended for desktop use. No tool list is published, so the exact operations available are not documented here.
When to use it
Worth adding when you want an assistant to help with Pinterest content such as reviewing or organizing boards and pins from your own account, and you are willing to supply a Pinterest access token.
Requirements
Runs as a local process on the user's machine, installed from the npm package @mrfentmen/pinterest-mcp over stdio. A free Pinterest access token is required. The manifest declares no environment variables or headers, so how the token is supplied is not documented. Desktop only; not available as a web executable.
Before you install
You must provide a Pinterest access token, which is a credential granting access to your Pinterest account; keep it private and store it carefully. The server may read or change account, board and pin data, but the published description does not specify which operations write or delete. The provider is a third party, and no tool list or README is available to review before installing.

Installation

In SourceWeft

  1. Open Pinterest Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 1, 2026
  2. v1.0.0Sep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.