Agent instructions: connect Postward

Connection contract

Name: postward
Transport: Streamable HTTP
URL: https://postward.cc/mcp
Authentication: OAuth 2.1 with PKCE
Static API key: none

Execution procedure

1. 1

   Detect the client

   Inspect the current environment and determine whether it is Codex, Claude Code, Cursor, Windsurf, or another MCP-capable client. Prefer the client's supported CLI or configuration interface.

2. 2

   Install the server

   Register one remote server named postward at https://postward.cc/mcp. Make the smallest appropriate configuration change and do not modify unrelated MCP servers.

3. 3

   Hand off consent

   Start the client's OAuth flow. When browser interaction is required, pause and clearly ask the user to sign in, choose a workspace, review scopes, and approve. Never request the user's password, OAuth code, access token, or refresh token in chat.

4. 4

   Resume and verify

   After the user confirms consent, reconnect or refresh the client's MCP tool list if necessary. Call get_activation_status. If unavailable, call list_workspaces as the compatibility check.

5. 5

   Report the result

   State which client was configured, which workspace is active, whether a real tool call succeeded, and the nextAction returned by Postward. Include an actionable error and recovery step if setup did not complete.

Client-specific installation

codex mcp add postward --url https://postward.cc/mcp
codex mcp login postward

claude mcp add --transport http --scope user postward https://postward.cc/mcp
# Then use /mcp and authenticate Postward.

{
  "mcpServers": {
    "postward": {
      "url": "https://postward.cc/mcp"
    }
  }
}

Safety and stopping conditions

• Do not ask for or create a Postward API key; OAuth discovery is built into the server
• Do not expose tokens, authorization codes, passwords, or storage credentials
• Do not overwrite unrelated MCP configuration
• Do not create campaigns or mutate workspace configuration during connection verification
• Do not approve, schedule, or publish content as part of setup
• Stop and explain the exact manual action only when browser consent or client UI interaction cannot be completed by the agent

Success criteria

Setup is complete only when Postward appears in the client's tool inventory and get_activation_status (or list_workspaces) returns successfully. Installing configuration or completing OAuth alone is not sufficient proof.