Documentation
Claude Code MCP guide

Connect Claude Code to GoodSender

Add GoodSender's hosted MCP server to Claude Code, sign in with OAuth, then confirm access with a read-only request before creating a draft.

Updated

Prerequisites

  • Install Claude Code 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. From the project where you will use Claude Code, register the hosted HTTP server:
    claude mcp add --transport http goodsender https://mcp.goodsender.com/
  2. Start OAuth sign-in:
    claude mcp login goodsender
    Complete the GoodSender sign-in and authorization in the browser. No credential belongs in the command.
  3. Claude Code uses local scope by default, so run the checks below from the same project. For user or project scope choices, see the official scope guide.

Verify the connection

Run claude mcp get goodsender or claude mcp list, then open /mcp in a Claude Code session. An added configuration alone is not proof that tools are usable: ask the read-only prompt below to confirm authenticated access.

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 claude is installed, run the add command in the intended project, and check that the server is named goodsender.
  • Authentication incomplete or expired: repeat claude mcp login goodsender and finish the browser flow; /mcp also shows when sign-in is required.
  • 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.

See the official Claude Code MCP reference for client behavior, or return to the GoodSender MCP overview.