pinterest-business-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug, info, warn, or error | |
| PINTEREST_APP_ID | Yes | Pinterest app ID | |
| PINTEREST_APP_SECRET | Yes | Pinterest app secret | |
| PINTEREST_ENVIRONMENT | Yes | sandbox or production | |
| PINTEREST_OAUTH_SCOPES | Yes | Default scopes unless overridden by the authorization tool | |
| PINTEREST_WRITES_ENABLED | No | true or false (default: false) | |
| PINTEREST_TOKEN_STORE_PATH | No | Encrypted token file path (default: `.tokens/pinterest-oauth.enc`) | |
| PINTEREST_TOKEN_ENCRYPTION_KEY | Yes | Base64 or passphrase used for AES-256-GCM token encryption |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pinterest_server_statusA | Returns Pinterest Business MCP server configuration status without exposing secrets. |
| pinterest_get_authorization_urlA | Starts the local Pinterest OAuth callback listener and returns the authorization URL plus safe connection instructions. |
| pinterest_connection_statusA | Returns whether a Pinterest account is connected locally without exposing tokens. |
| pinterest_disconnectA | Securely removes locally stored Pinterest OAuth authorization data without returning tokens. |
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 4 tools
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.
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.
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.
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.