Skip to main content

Postscript MCP

Postscript MCP lets you connect your SMS performance data to the AI assistant you already use. Ask questions like "which three campaigns drove the most revenue last month?" in Claude, ChatGPT, or Codex and get answers pulled straight from your Postscript account. In this article, we walk through how to set up the connector and how to get the most reliable results.

What Is the Postscript MCP?

MCP stands for Model Context Protocol, an open standard that lets AI assistants securely connect to outside data sources. The Postscript MCP is Postscript's connector built on that standard. Once connected, your AI assistant can pull your campaign, automation, popup, and shop-wide analytics and answer questions about them in plain language. For example, you can ask "Give me my SMS report for last week versus the week before" and get sends, revenue, and CTR without opening a dashboard or exporting a report.

The connector is read-only: it reports on your account and cannot create, edit, or send anything in Postscript.


​How the Postscript MCP benefits you:

  • Get your SMS numbers in the same chat where you already analyze your Shopify, Klaviyo, and Meta data

  • Pull weekly recaps, top-performer rankings, and year-over-year comparisons by asking

  • Export full result tables you can copy into a spreadsheet

Supported AI Clients

The Postscript MCP works with:

  • Claude (web and desktop) on all plans

  • Claude Code

  • ChatGPT on the web (Business, Enterprise, or Edu workspaces, or personal Plus/Pro accounts with developer mode)

  • Codex CLI

Mobile apps are not supported. Every setup path uses the same server URL: https://mcp.postscript.io/mcp

Connect in Claude (Web or Desktop)

All Claude plans work. Free accounts are limited to one custom connector.

On Team or Enterprise plans, an Owner must add the connector at the org level first: Organization settings > Connectors > Add, hover Custom, select Web, paste the server URL, and click Add. Each member then connects with the steps below. If you are not an Owner, ask your admin to do this step first.

  1. Open claude.ai or Claude Desktop. Go to Settings > Connectors.

  2. On Free, Pro, or Max: click +, then Add custom connector. Paste the server URL https://mcp.postscript.io/mcp and click Add.

    1. On Team or Enterprise: the connector is already listed once your Owner adds it — skip to the next step.

  3. Click Connect next to the connector. A browser window opens.

  4. Sign in to Postscript and approve access. This step links the connector to your shop.

  5. In a chat, click the + at the lower left, then Connectors, and toggle Postscript Analytics on.

You are ready. Ask a question about your SMS performance.

Connect in ChatGPT

Workspace Accounts (Business, Enterprise, or Edu)

A workspace admin sets the connector up once, and members connect with their own Postscript sign-in.

Admin setup:

  1. Enable Developer mode. In ChatGPT on the web, open Settings → Security and login and turn on Developer mode.

  2. Create the plugin. Open Plugins → Browse plugins, select the + button, and enter: Name Postscript Analytics, Connection Server URL, Server URL https://mcp.postscript.io/mcp, Authentication OAuth. Leave the icon, description, and Advanced OAuth settings at their defaults.

  3. Acknowledge and create. Read the custom-MCP risk notice, then select Create.

  4. Sign in. Select Sign in with Postscript Analytics and complete the OAuth sign-in.

  5. Grant access. Open Admin → Plugins, select Postscript Analytics, and configure availability. Creating the plugin does not automatically grant every member access.

For each workspace member:

  1. Find the plugin. Open Plugins → Browse plugins and search for Postscript Analytics.

  2. Install it. Click Install plugin (skip if your admin set it to install automatically).

  3. Connect your account. Click Connect, then Sign in with Postscript Analytics, and complete the OAuth sign-in with your own Postscript account.

Personal Accounts (Plus or Pro)

  1. Enable Developer mode. In ChatGPT on the web, go to Settings → Security and login and enable Developer mode.

  2. Create the plugin. Open Plugins → Browse plugins, click +, and enter: Name Postscript Analytics, Connection Server URL, Server URL https://mcp.postscript.io/mcp, Authentication OAuth.

  3. Acknowledge and create. Check the custom-MCP risk acknowledgement and click Create.

  4. Sign in. Click Sign in with Postscript Analytics and complete the OAuth sign-in.

The connection carries over to ChatGPT web, ChatGPT desktop, and Codex.

Connect in Claude Code or Codex CLI

Claude Code

  1. Add the connector. Run: claude mcp add --transport http postscript-analytics https://mcp.postscript.io/mcp

  2. Open the MCP menu. Start Claude Code and run /mcp.

  3. Sign in. Select the Postscript connector and complete the browser sign-in to link your shop.

Codex CLI

  1. Add and log in. Run: codex mcp add postscript-analytics --url https://mcp.postscript.io/mcp then codex mcp login postscript-analytics

  2. Approve access for your shop in the browser sign-in.

  3. Confirm the connection. Start Codex and run /mcp to verify Postscript Analytics is connected.

What You Can Ask

The connector answers questions about:

  • Campaign performance: sends, clicks, CTR, conversion rate, orders, revenue, and unsubscribes, per campaign

  • Automation performance: the same measures, per automation (whole flow)

  • Popup performance: per popup

  • Shop-wide trends: attributed revenue, messages sent, and subscribers as a time series by hour, day, week, month, or year

  • Rankings: top or bottom performers by any measure

  • Exports: tables of campaign and automation results you can copy into a spreadsheet

A few prompts to copy and adapt:

  • "Show me campaign and automation performance from [start date] to [end date]: sends, CTR, conversion rate, and revenue per campaign and flow."

  • "Which three campaigns or flows drove the most revenue from [start] to [end]?"

  • "Give me my SMS report for last week versus the week before: sends, revenue, and CTR."

  • "Compare this July to last July: sends, revenue, and revenue per send, split by campaigns versus automations."

  • "Show my subscriber count by month for the last 12 months."

  • "Give me every campaign and automation from [start] to [end] in one table: IDs, sends, clicks, orders, and revenue."

TIP: Use explicit dates ("June 1 to August 18") rather than relative ranges ("the last 90 days"), and name the measure and range you want. Specific questions return the most reliable results.

Things to Know

  • The connector is read-only. It reports on your account and cannot create, edit, send, or delete anything in Postscript. This is by design: we’re heavily monitoring accuracy and ease of use first, before expanding to write access.

  • Access is scoped to your shop. You sign in to Postscript via OAuth when connecting, and the assistant only sees the shop tied to your sign-in.

  • Expect two revenue numbers. Per-campaign and per-automation revenue uses click attribution with a 29-day window. The shop-wide revenue metric uses a wider definition that includes view attribution, so the shop total will always be larger than the sum of the reports. Both are correct: use the reports to compare campaigns and the shop metric for your account trend.

  • Recent sends are still accruing. Attribution runs 29 days from send, so numbers for recent sends keep rising until the window closes.

  • Skip strategy questions. The assistant sees your numbers but doesn't know Postscript best practices and products as well as we do, so bring "should I change this?" questions to your Postscript CSM.

Troubleshooting

  • The sign-in window loops or stalls. Close it, then disconnect and reconnect in your assistant's connector settings.

  • The assistant doesn't use the connector. Start a new chat, confirm the connector is toggled on, and ask a specific question, like "use Postscript Analytics to show my campaign revenue for last month."

  • You see the wrong shop's name. Disconnect, reconnect, and sign in with the correct Postscript account. Then let us know via support so we can look into it.

  • The connector doesn't appear. On Claude Team/Enterprise or a ChatGPT workspace, confirm your admin completed the org-level step. On a corporate network, your IT team may need to allow mcp.postscript.io.

  • To disconnect: in Claude, go to Settings > Connectors and remove Postscript Analytics. In Claude Code, run claude mcp remove postscript-analytics. In ChatGPT, go to Settings > Apps, select the app, and disconnect your account.

Common Questions

Can the connector make changes to my Postscript account? No. It's read-only. It can report on your campaigns, automations, and popups, but any changes to your program happen in Postscript.

Is my data safe? Can it see other shops? The connection uses OAuth: you sign in to Postscript and approve access, which links the connector to your shop. The assistant only sees the shop tied to your sign-in.

Who on my team can use it? Anyone with a Postscript login. On Claude Team/Enterprise plans and ChatGPT workspaces, an admin adds the connector at the org level once, then each member connects with their own sign-in.

A number looks different from the Postscript app. What do I do? First check the two-revenue-numbers note above, since attribution definitions explain most differences. If something still looks off, tell the assistant in plain words ("that revenue number doesn't match what I see in Postscript") and it records your comment for our team, attached to the exact answer you meant.

Get Support

Have questions? Please feel free to reach out to our Support team at [email protected] or via live chat.
​Need ongoing channel strategy guidance? Please fill out this form and we'll connect you to one of our certified partners.

Related Articles
Did this answer your question?