Skip to main content
Glama
pinterest-business-mcp

pinterest-business-mcp

by NordicsSys

Pinterest Business MCP

Local Model Context Protocol server for Pinterest Business workflows. This repository includes a stdio MCP server, Pinterest OAuth connection tools, encrypted local token storage, and server status reporting.

Requirements

  • Node.js 22+

  • pnpm 11+

  • A Pinterest developer app with the redirect URI below

Related MCP server: pinterest-mcp

Pinterest developer dashboard setup

  1. Sign in at Pinterest Developers.

  2. Create or open your app.

  3. Under Configure, add this exact redirect URI:

    http://127.0.0.1:3333/oauth/callback

  4. Copy your App ID and App secret key.

  5. Request the scopes your workflow needs. At minimum, connection testing commonly uses read scopes such as boards:read, pins:read, and user_accounts:read.

  6. For sandbox testing, keep PINTEREST_ENVIRONMENT=sandbox. Pinterest uses the same OAuth authorize page for both environments; token exchange uses the sandbox API host when sandbox is selected.

Local setup

pnpm install
cp .env.example .env

Edit .env and set at minimum:

PINTEREST_ENVIRONMENT=sandbox
PINTEREST_APP_ID=your-app-id
PINTEREST_APP_SECRET=your-app-secret
PINTEREST_TOKEN_ENCRYPTION_KEY=your-base64-key
PINTEREST_OAUTH_SCOPES=boards:read,pins:read,user_accounts:read

Generate an encryption key:

openssl rand -base64 32

Development

pnpm dev          # watch mode (tsx)
pnpm build        # compile to dist/
pnpm start        # run compiled server
pnpm verify       # typecheck, lint, test, build

MCP client configuration (Cursor)

Add a project-scoped MCP server entry in .cursor/mcp.json (recommended) or your user MCP settings. Do not commit real secrets.

{
  "mcpServers": {
    "pinterest-business": {
      "command": "node",
      "args": ["/absolute/path/to/pinterest-business-mcp/dist/index.js"],
      "env": {
        "PINTEREST_ENVIRONMENT": "sandbox",
        "PINTEREST_APP_ID": "your-app-id",
        "PINTEREST_APP_SECRET": "your-app-secret",
        "PINTEREST_TOKEN_ENCRYPTION_KEY": "your-base64-key",
        "PINTEREST_OAUTH_SCOPES": "boards:read,pins:read,user_accounts:read",
        "PINTEREST_WRITES_ENABLED": "false",
        "LOG_LEVEL": "info"
      }
    }
  }
}

Restart Cursor after changing MCP configuration.

Connecting your Pinterest Business account

  1. Start the MCP server in Cursor.

  2. Call pinterest_get_authorization_url.

  3. Open the returned authorization URL in your browser.

  4. Approve the Pinterest app when prompted.

  5. Wait for the local callback page at http://127.0.0.1:3333/oauth/callback to report success.

  6. Call pinterest_connection_status to confirm the connection.

The MCP server never asks for your Pinterest password. Authentication happens only on Pinterest's official OAuth page.

Sandbox setup

  • Set PINTEREST_ENVIRONMENT=sandbox.

  • Use the same redirect URI: http://127.0.0.1:3333/oauth/callback.

  • OAuth authorization still starts at https://www.pinterest.com/oauth/.

  • Token exchange and refresh use https://api-sandbox.pinterest.com/v5/oauth/token.

Tools

pinterest_server_status

Returns server metadata and configuration flags only — never credential values.

pinterest_get_authorization_url

Starts the local callback listener on 127.0.0.1:3333, creates a single-use OAuth state value, and returns the Pinterest authorization URL plus safe instructions. Tokens are never returned by this tool.

Optional input:

  • scopes: array of official Pinterest scopes. If omitted, PINTEREST_OAUTH_SCOPES is used.

pinterest_connection_status

Reports whether a Pinterest account is connected locally, including scope and expiry metadata. Tokens are never returned. Expired access tokens are refreshed automatically when a valid refresh token is available.

pinterest_disconnect

Securely removes locally stored OAuth authorization data. To revoke access on Pinterest itself, remove the app from Pinterest settings under Security and logins → Apps.

Environment variables

See .env.example for the full list.

Variable

Required

Description

PINTEREST_ENVIRONMENT

Yes

sandbox or production

PINTEREST_APP_ID

OAuth

Pinterest app ID

PINTEREST_APP_SECRET

OAuth

Pinterest app secret

PINTEREST_TOKEN_ENCRYPTION_KEY

OAuth

Base64 or passphrase used for AES-256-GCM token encryption

PINTEREST_TOKEN_STORE_PATH

No

Encrypted token file path (default: .tokens/pinterest-oauth.enc)

PINTEREST_OAUTH_SCOPES

OAuth

Default scopes unless overridden by the authorization tool

PINTEREST_WRITES_ENABLED

No

true or false (default: false)

LOG_LEVEL

No

debug, info, warn, or error

Troubleshooting

Problem

What to check

Callback port already in use

Another OAuth attempt or process is using 127.0.0.1:3333. Wait for it to finish or stop the other process.

Redirect URI mismatch

The Pinterest app must contain the exact URI http://127.0.0.1:3333/oauth/callback.

Missing scopes

Set PINTEREST_OAUTH_SCOPES or pass scopes to pinterest_get_authorization_url.

Connection not stored

Confirm PINTEREST_TOKEN_ENCRYPTION_KEY is set and writable, then repeat the OAuth flow.

Sandbox token exchange failed

Keep PINTEREST_ENVIRONMENT=sandbox so token exchange uses the sandbox API host.

Refresh failed

Reconnect with pinterest_get_authorization_url if the refresh token expired or was revoked.

Token revocation and disconnect

  • Local disconnect: call pinterest_disconnect.

  • Pinterest-side revocation: open Pinterest settings → Security and logins → Apps and remove this app.

  • Pinterest's remote revocation endpoint is unreliable in some app states, so local disconnect plus manual app removal is the supported recovery path.

Security

See SECURITY.md for credential handling and threat boundaries.

License

MIT

Available Tools

4 tools
pinterest_connection_statusA

Returns whether a Pinterest account is connected locally without exposing tokens.

Inputs: no named parameters.

pinterest_disconnectA

Securely removes locally stored Pinterest OAuth authorization data without returning tokens.

Inputs: no named parameters.

pinterest_get_authorization_urlA

Starts the local Pinterest OAuth callback listener and returns the authorization URL plus safe connection instructions.

Inputs: scopes.

pinterest_server_statusA

Returns Pinterest Business MCP server configuration status without exposing secrets.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a distinct aspect of OAuth lifecycle: server config status, authorization URL retrieval, connection status, and disconnection. There is no overlap in their purposes, making misselection unlikely.

    Naming Consistency3/5

    All tools share the 'pinterest_' prefix and use lowercase with underscores, but verb usage is inconsistent. 'server_status' and 'connection_status' are noun phrases, while 'get_authorization_url' uses a verb and 'disconnect' is a bare verb. This mixed convention is readable but not fully predictable.

    Tool Count5/5

    With 4 tools, the server is tightly scoped to OAuth connection management. Each tool is essential and there is no bloat, making the count ideal for the apparent purpose.

    Completeness4/5

    The tool set covers the main lifecycle: check server config, initiate authorization, verify connection, and disconnect. A minor gap is the absence of an explicit token refresh or explicit callback handling, but these are likely handled implicitly or are beyond the server's intended scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with eBay APIs for account verification, item search, and browsing via OAuth 2.0 authentication, with support for token refresh and sandbox/production environments.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Pinterest boards and pins, create and update pins, and track analytics via the Pinterest API v5.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage Pinterest accounts through the Pinterest API v5, including creating and editing pins, organizing boards, searching public content, and retrieving pin and account analytics.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read and manage an account's boards, pins, sections, and analytics, run full-text search over its own content, and complete OAuth token flows through the Pinterest API v5. It exposes 35 typed tools that run either as a local stdio subprocess or as a stateless remote HTTP endpoint with built-in OAuth 2.1 support.
      35
      28 npm
      2
      MIT