How to Connect Claude, ChatGPT and Other AI Apps to BlogAmplify

How to add BlogAmplify to each app

claude mcp add --transport http blogamplify https://api.blogamplify.com/mcp

{
  "mcpServers": {
    "blogamplify": {
      "url": "https://api.blogamplify.com/mcp"
    }
  }
}

{
  "servers": {
    "blogamplify": {
      "type": "http",
      "url": "https://api.blogamplify.com/mcp"
    }
  }
}

What the app can use

BlogAmplify gives the app these tools. They are the same as the in-app assistant's, with the same checks and limits. Tools that read never change anything; a read-only connection sees only those.

Ready-made workflows

Apps that show MCP prompts (Claude Code lists them as slash commands) offer these:

• SEO check-up: What improved, and the most valuable things to do this week.
• Fix Site Health issues: Works through open problems with the exact fix for each, then checks the fixes.
• Get listed outreach: Picks the best pages, drafts a pitch for each and prepares the emails for your approval.
• Review the content plan: Finds weak, overlapping or outdated topics and suggests better ones.
• Close AI visibility gaps: The questions AI answers without naming you, and what to do about each.
• Local search check-up: Your Google Business Profile, map rankings and directories, with what to fix first.

What needs your confirmation

• Proposals: writing or rewriting an article, a new content plan, publishing, Fix it for me and article updates. Apps that can show a confirmation ask you there; the others give you a link to BlogAmplify, where you confirm or reject it.
• Your own words: instructions every article follows, brand facts, the business description and owner answers. An app may have read text from anywhere, so these are saved only once you confirm them.
• Nothing about money: an app can read your plan and link to the billing page, but never buys, upgrades or cancels anything.

Text from other websites, search results and AI answers reaches the app as data, and BlogAmplify tells the app to treat it that way.

API keys, for apps that can't sign in

Some apps and your own scripts can't sign in through the browser. In Settings, Connected apps, click New API key, choose what it may do and on which websites, and copy the key: it is shown once. Send it as a header:

{
  "mcpServers": {
    "blogamplify": {
      "url": "https://api.blogamplify.com/mcp",
      "headers": {
        "Authorization": "Bearer bamcp_sk_..."
      }
    }
  }
}

Keep keys out of shared files and repositories. Remove a key in the same place, and it stops working at once.

For developers

• Remote MCP server over Streamable HTTP, protocol version 2025-11-25 (earlier versions work too), tools and prompts.
• OAuth 2.1 with PKCE (S256), dynamic client registration and Client ID Metadata Documents; discovery at /.well-known/oauth-protected-resource/mcp on the API. Scopes: read and write.
• Access tokens last an hour; refresh tokens are replaced on every use and last 90 days.
• Every tool that works on a website takes an optional website argument (a domain or the id from list_websites).
• Proposals use MCP elicitation for the owner's confirmation when the app supports it, else return a confirm link.