harnesses

Connect Postward to Cursor

10 minutes

Beginner

Cursor users

Both execution

What You Will Finish With

Cursor can read your workspace and drive campaigns through the remote MCP, with one shared configuration for the editor and Cursor CLI.

1
Register the remote server
Use ~/.cursor/mcp.json for your own machine or .cursor/mcp.json in the repository when the whole team should discover Postward.
```
{
  "mcpServers": {
    "postward": {
      "url": "https://postward.cc/mcp"
    }
  }
}
```
2
Complete OAuth
Open Cursor's MCP settings, select Postward, and finish the browser sign-in. Choose the workspace you want to authorize. Never paste an access token into chat.
3
Verify the connection
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.
```
agent mcp list-tools postward
```
4
Optionally add local Creative
Register the Docker command as a local stdio server in the same configuration when you want offline trimming, captions, watermarking, or format conversion. Your files stay on your computer until you explicitly upload them.
```
docker run -i --rm -v postward-creative-output:/tmp/postward-creative ghcr.io/postward-cc/creative-mcp:latest
```
5
Create only after verification
Ask Cursor to list your workspaces before creating anything, then follow the first-campaign flow. 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 Cursor".

Outcome: Cursor can read your workspace and drive campaigns through the remote MCP, with one shared configuration for the editor and Cursor CLI.
Prerequisites to verify first: A Postward account; Cursor with MCP support; Docker only for local Creative.

Steps:
1. Register the remote server: Use ~/.cursor/mcp.json for your own machine or .cursor/mcp.json in the repository when the whole team should discover Postward.
2. Complete OAuth: Open Cursor's MCP settings, select Postward, and finish the browser sign-in. Choose the workspace you want to authorize. Never paste an access token into chat.
3. Verify the connection: 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. Optionally add local Creative: Register the Docker command as a local stdio server in the same configuration when you want offline trimming, captions, watermarking, or format conversion. Your files stay on your computer until you explicitly upload them.
5. Create only after verification: Ask Cursor to list your workspaces before creating anything, then follow the first-campaign flow. 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
Cursor with MCP support
Docker only for local Creative

Works With

Cursor editor
Cursor CLI