@cmo-so/mcp

CMO.so's MCP server: let Claude, Cursor, VS Code or any MCP client check your website's results, review your LinkedIn and Facebook Page queue, and manage blog post ideas and drafts with Maggie.

Hosted (nothing to install)

Add a remote MCP server with the URL https://mcp.cmo.so/mcp and sign in when asked (OAuth). Works with ChatGPT, Claude.ai, Claude Desktop, Cursor and VS Code.

Local (stdio)

Sign in once with the CLI, then point your client at cmo-mcp:

npx @cmo-so/cli login

{
  "mcpServers": {
    "cmo-so": { "command": "npx", "args": ["-y", "@cmo-so/mcp"] }
  }
}

Or skip the login and pass an API key from your account settings:

{
  "mcpServers": {
    "cmo-so": { "command": "npx", "args": ["-y", "@cmo-so/mcp"], "env": { "CMO_API_KEY": "cmo_…" } }
  }
}

Claude Code: claude mcp add cmo-so -- npx -y @cmo-so/mcp

How changes work

Tools that change something take two calls: the first returns a preview (and what it costs, such as an AI generation or a post credit), and only a second call with confirm: true and the preview's confirmation runs it. The confirmation is bound to the exact arguments and expires after 10 minutes. Your client should show you the preview and ask before confirming.

Most tools take workspace (your website's domain); it can be left out when you have one website.