harnesses

Connect Postward to ChatGPT

Authorize the remote Postward MCP in ChatGPT and understand the local-execution boundary.

8 minutes

Beginner

ChatGPT users

Remote execution

What You Will Finish With

ChatGPT can work with campaigns, assets, runs, review, and publishing through Postward's hosted endpoint.

1
Open ChatGPT connector settings
Add a custom remote MCP connection using the Postward endpoint. The exact settings label can vary by ChatGPT release.
```
Server name: postward
Transport: Streamable HTTP
URL: https://postward.cc/mcp
Authentication: OAuth 2.1 with PKCE
Static API key: none
```
2
Authorize Postward
Start the connection, sign in in the browser, select a workspace, inspect the requested scopes, and approve.
3
Verify with a read-only request
Ask the agent: Check my Postward activation status and tell me the next incomplete step. A successful get_activation_status call proves transport, OAuth, and workspace access.
4
Respect the execution boundary
ChatGPT uses the remote Postward MCP. Do not follow the Docker or local Postward Creative steps in this tutorial: ChatGPT does not expose the local stdio/filesystem environment required by that server.
Important: For local Docker tools, use Claude Code, Codex, OMP, ZCode, Cursor, or another development harness with local stdio MCP support.
5
Create only after verification
Ask ChatGPT to summarize the active workspace before requesting a campaign. Keep approval and publication as separate, explicit actions.

Where to go next

Ask my agent

Copy a ready prompt for this tutorial and paste it into any agent connected to Postward.

Preview the prompt

Follow the Postward tutorial "Connect Postward to ChatGPT".

Outcome: ChatGPT can work with campaigns, assets, runs, review, and publishing through Postward's hosted endpoint.
Prerequisites to verify first: A Postward account; A ChatGPT experience that supports remote MCP connections.

Steps:
1. Open ChatGPT connector settings: Add a custom remote MCP connection using the Postward endpoint. The exact settings label can vary by ChatGPT release.
2. Authorize Postward: Start the connection, sign in in the browser, select a workspace, inspect the requested scopes, and approve.
3. Verify with a read-only request: Ask the agent: Check my Postward activation status and tell me the next incomplete step. A successful get_activation_status call proves transport, OAuth, and workspace access.
4. Respect the execution boundary: ChatGPT uses the remote Postward MCP. Do not follow the Docker or local Postward Creative steps in this tutorial: ChatGPT does not expose the local stdio/filesystem environment required by that server.
5. Create only after verification: Ask ChatGPT to summarize the active workspace before requesting a campaign. Keep approval and publication as separate, explicit actions.

First inspect my environment and existing configuration, and verify each prerequisite before acting.
Follow the current Postward documentation rather than assuming tool names.
Do not replace unrelated configuration.
Verify the result and report exactly what changed.

Prerequisites

A Postward account
A ChatGPT experience that supports remote MCP connections

Works With

ChatGPT remote MCP