# Postscript [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/pipeworx-io/mcp-postscript  
**GitHub Stars:** 0  
**npm Downloads (last month):** 445  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/postscript

## Description
Postscript MCP Pack — SMS marketing for Shopify.

## Tools
Capabilities this server exposes over MCP:

- **postscript_list_subscribers** — List SMS subscribers for a Postscript (Shopify) shop. Supports filtering by email, phone number, Shopify customer ID, and created/updated timestamps, plus sorting. Page-based pagination: returns { page_info: { page, total_pages }, subscribers: [...] }; pass page to walk results.
- **postscript_get_subscriber** — Get a single SMS subscriber by Postscript subscriber ID. Returns phone number, email, subscription status, Shopify customer linkage, and custom properties.
- **postscript_list_keywords** — List all active SMS keywords for the shop. Keywords are the text-to-join words (e.g. "JOIN") subscribers text to opt in. Returns keyword IDs, the keyword text, and associated subscription settings.
- **postscript_get_keyword** — Get a single SMS keyword by its ID. Returns the keyword text, status, and configuration (welcome message, list assignment).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "postscript": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-postscript"]
  }
}
```

## Documentation

## What the Postscript MCP server does

The Postscript MCP server connects an MCP client to Postscript data for a Shopify shop. Its focused toolset covers SMS subscribers and the keywords customers use to opt in. This makes it suitable for inspecting subscriber records, checking subscription state, relating a subscriber to a Shopify customer, and reviewing keyword-based signup configuration.

The package does not describe campaign creation, message sending, order data, or subscriber mutations. Its documented operations are read-oriented: two tools retrieve subscriber information and two retrieve keyword information.

## How it works

You can connect through the hosted Pipeworx endpoint at `https://gateway.pipeworx.io/postscript/mcp`, or run `@pipeworx/mcp-postscript` locally as a stdio MCP server. Both access paths use the same pack tools. The hosted endpoint is part of the Pipeworx gateway and lists the Postscript tools together with shared gateway meta-tools. The local process responds over standard input and output and exposes only the Postscript pack tools.

The gateway also offers a full endpoint at `https://gateway.pipeworx.io/mcp`. A pack endpoint and the full endpoint reach the same gateway and data sources; the distinction is which pack tools are listed directly. The gateway's `ask_pipeworx` tool can route questions across the wider catalog, including when the client is connected to the Postscript endpoint.

## Setup and configuration

For a client that supports remote MCP connections, add the hosted endpoint as the server URL. A local configuration can start the package with `npx -y @pipeworx/mcp-postscript`. The package can also be run directly with the same command to verify that it starts.

Calls made through the HTTP tool API require the pack's own API key as `_apiKey`; the gateway does not provide that key on the user's behalf.

## Tools and capabilities

- `postscript_list_subscribers` retrieves subscriber pages and supports filters for email, phone number, Shopify customer ID, and created or updated timestamps. Sorting is available, and the response includes page information with the current page and total page count.
- `postscript_get_subscriber` retrieves one subscriber by Postscript subscriber ID, including phone, email, subscription status, Shopify customer association, and custom properties.
- `postscript_list_keywords` lists active SMS keywords for the shop. Results include keyword IDs, keyword text, and related subscription settings.
- `postscript_get_keyword` retrieves a keyword by ID, including its text, status, welcome message, and list assignment.

The Postscript MCP server therefore fits lookup and inspection workflows more closely than write automation. Subscriber pagination requires passing the requested page while walking through results.

## Limitations and notes

The hosted pack connection currently includes shared Pipeworx tools in addition to the four pack-specific tools, so `tools/list` may show more tools than this listing documents. The exact gateway scope is reported by the connection's `initialize` response. The standalone process avoids those shared meta-tools and does not provide `ask_pipeworx` routing.

The documented material does not state that the four Postscript tools can create, update, delete, send, or opt subscribers in or out. Treat the pack as a read-access interface unless the connected tool schema documents otherwise. The Postscript MCP server also requires the user's own API key for HTTP tool calls, and no key is supplied by Pipeworx.

_Full upstream README: https://allmcps.com/mcp/postscript/readme_