Connect Codex to GoodSender

Prerequisites

• Install the Codex CLI and have a browser available.
• Have a GoodSender account with access to the workspace and blog you intend to use.

Connect in three steps

1. Register the hosted server in Codex's shared CLI and IDE configuration:

   codex mcp add goodsender --url https://mcp.goodsender.com/

2. Start OAuth sign-in:

   codex mcp login goodsender

   Complete the GoodSender sign-in and authorization in the browser. No credential belongs in the command.
3. Run codex mcp list and confirm goodsender is saved. This checks configuration, not successful authenticated tool access.

Verify the connection

codex mcp list establishes configuration. Start Codex and make an actual read-only request using the prompt below to establish usable access; a saved entry alone does not prove that OAuth completed or tools can run.

Try safe prompts

• Read-only: “List my blog posts and show each title and status.” Expected: posts from the selected blog. An empty list is a successful result when the blog has no posts.
• Draft-only: “Create a draft about [topic], then show me its title and status without publishing it.” Expected: a new draft. Creating a draft does not publish the post or send email.

When you deliberately want to publish, follow the first-publish workflow to review the preview and distribution choices.

Troubleshooting

• Client or configuration missing: confirm codex is installed, repeat the add command, and check that codex mcp list names goodsender.
• Authentication incomplete or expired: repeat codex mcp login goodsender and finish the browser flow. The server entry may remain saved even when sign-in needs renewal.
• Wrong URL or network failure: the exact root URL is https://mcp.goodsender.com/, with no /mcp suffix. Check network access, then retry.
• Workspace, blog, or content missing: verify the signed-in account can access the intended workspace and that it has a blog. Empty post results can be valid and do not by themselves mean the connection failed.