Integrations

MCP server

Give Claude, Cursor or any MCP-compatible agent the ability to write, read and edit reblogger articles — using your plan and credits.

Overview

reblogger.ai runs a remote Model Context Protocol server. Point your AI client at it with an API key and it can generate full SEO articles, wait for them, read them back and refine titles or meta descriptions — all in one conversation.

POSThttps://reblogger.ai/api/mcp

Transport: Streamable HTTP (stateless). No local install needed for clients that support remote servers.
Auth: Authorization: Bearer rb_live_… — the same API keys as the REST API, with the same scopes.
Available on every plan. Articles cost the same credits as through the API or dashboard.

Setup

Create an API key under Settings → API keys (consider a dedicated key named “Claude” so you can revoke it independently), then add the server to your client.

Claude Desktop

Open Settings → Developer → Edit config and add reblogger to claude_desktop_config.json. The mcp-remote bridge connects Claude Desktop to remote servers and needs Node.js 18+.

claude_desktop_config.json

{
  "mcpServers": {
    "reblogger": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://reblogger.ai/api/mcp",
        "--header",
        "Authorization:${REBLOGGER_AUTH}"
      ],
      "env": {
        "REBLOGGER_AUTH": "Bearer rb_live_…"
      }
    }
  }
}

Restart Claude Desktop; the reblogger tools appear under the tools icon. The one-line equivalent for other launchers is npx -y mcp-remote https://reblogger.ai/api/mcp --header "Authorization: Bearer rb_live_…". Putting the token in env as above avoids a known issue with spaces in arguments on Windows.

Claude Code

Shell

claude mcp add --transport http reblogger https://reblogger.ai/api/mcp \
  --header "Authorization: Bearer rb_live_…"

Add --scope user to make it available in all projects. Check the connection with claude mcp list or /mcp inside a session.

Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then enable it under Settings → MCP.

~/.cursor/mcp.json

{
  "mcpServers": {
    "reblogger": {
      "url": "https://reblogger.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer rb_live_…"
      }
    }
  }
}

Other clients

Any client that supports remote Streamable HTTP servers with custom headers works. For example VS Code:

.vscode/mcp.json

{
  "servers": {
    "reblogger": {
      "type": "http",
      "url": "https://reblogger.ai/api/mcp",
      "headers": { "Authorization": "Bearer ${input:reblogger-key}" }
    }
  },
  "inputs": [
    { "id": "reblogger-key", "type": "promptString", "description": "reblogger.ai API key", "password": true }
  ]
}

Clients that only support local (stdio) servers can use the mcp-remote bridge shown for Claude Desktop.

Tools

MCP tools
Tool	What it does	Scope
`generate_article`	Write an article from a url or topic with all API options (language, length, tone, model, focus_keyword…). Returns ids immediately; wait_seconds (≤ 50) waits for the result.	articles:write
`get_generation`	Status, stage and progress of a generation.	articles:read
`get_article`	The full article with SEO metadata; format markdown (default), html or blocks (Gutenberg).	articles:read
`list_articles`	Your articles, newest first, with status and language filters and cursor pagination.	articles:read
`update_article`	Edit title, slug, meta fields, tags, categories, status or the Markdown body.	articles:write
`list_models`	Available text and image models with credit costs and plan access.	articles:read
`get_account`	Plan, credit balance and plan features.	account:read
`extract_url`	Readable Markdown of any public page — free, nothing is generated.	articles:read

Tool inputs mirror the REST parameters. Results include both readable text for the model and structured JSON. The server also sends instructions that teach the agent the workflow: create → poll get_generation → read with get_article.

Generation takes a minute or two

generate_article returns immediately unless you (or the agent) pass wait_seconds (max 50). Agents then poll get_generation until the status is succeeded.

Example prompts

“Use reblogger to write a friendly, medium-length article about cold brew coffee for beginners, in German, with an FAQ.”
“Rewrite https://example.com/blog/our-launch as a fresh article for small agencies. Then give me three alternative meta titles.”
“List my last 10 reblogger articles and update the tags of the cold brew one to coffee, brewing, recipes.”
“How many reblogger credits do I have left, and which premium models can I use?”

Protocol details

The server is stateless and answers JSON-RPC over POST with JSON responses (no session id, no standalone SSE stream). Clients must send Accept: application/json, text/event-stream. To test it by hand:

curl https://reblogger.ai/api/mcp \
  -H "Authorization: Bearer $REBLOGGER_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

Troubleshooting

401 / “Unauthorized” — the header is missing or the key was revoked. Check there is exactly one space after Bearer and that the key starts with rb_live_.
The client opens a browser to log in — it didn't send the header and fell back to OAuth discovery. Re-check the header configuration for your client.
Tool errors such as insufficient_credits or plan_required come back as normal tool results with an explanation, so the agent can tell you what to do.
Rate limits — 120 MCP requests per minute per key and 20 new articles per minute. See Rate limits.