Blog-Maker
Start free
Our WorkflowMCPDevelopersFeaturesPricingFAQBlogLog inStart free

Connect Claude to blog-maker

Add blog-maker as a connector in Claude once, then manage your article briefs and drafts just by chatting. Setup takes about two minutes and you only do it once per device.

Your connection URL

https://blog-maker.com/mcp

Before you start

You need a blog-maker account, and you should be signed in to blog-maker in the same browser you use to approve the connection.

Claude Desktop

  1. 1Open Claude Desktop, then Settings, then Connectors.
  2. 2Choose Add custom connector.
  3. 3Paste the connection URL above and confirm.
  4. 4A blog-maker tab opens. If you are signed in you go straight to the approval screen, otherwise sign in first.
  5. 5On the approval screen, check the access it asks for and choose Allow access.
  6. 6Back in Claude you are connected. Ask: what article ideas do I have?

Claude web (claude.ai)

  1. 1Open claude.ai, then Settings, then Connectors.
  2. 2Choose Add custom connector.
  3. 3Paste the connection URL above and confirm.
  4. 4Approve the connection in the blog-maker tab that opens.
  5. 5You are connected. Ask Claude about your briefs to test it.

Claude Code

  1. 1In Claude Code, run /mcp and add a connector.
  2. 2Use the connection URL above.
  3. 3Approve the connection in the browser window that opens.
  4. 4You are connected from the terminal.

What Claude can do

  • •Find new topic ideas from your content gaps and Search Console, then turn the good ones into briefs.
  • •Read, create and refine your article briefs, so the writing comes out better.
  • •Read your articles, polish a draft, and check its status and scores.
  • •Start the research and writing for an article you name (this uses your article quota).
  • •Create WooCommerce product texts the same way (Basic plan or higher).
  • •See where each brand publishes, so you know where content would go.

What stays in your hands

Claude reads and drafts for you. Publishing an article live is always a manual step you take in the blog-maker dashboard, so nothing goes public without your review.

Manage or disconnect

You can see and revoke the connection any time under Settings, then Connected apps. Revoking takes effect immediately.

Troubleshooting

Claude cannot add the connector or the connection is refused
Make sure the URL is exactly https://blog-maker.com/mcp with no trailing characters, and that you are signed in to blog-maker in the same browser.
The approval screen says access denied or nothing happens
You need to choose Allow access on the blog-maker approval screen. If you closed it, start adding the connector again to reopen it.
Claude says it is no longer authorized or the token expired
Reconnect from the Connect to Claude card on your dashboard, or check Settings, then Connected apps, in case the connection was revoked.
I revoked the connection by mistake
Just add the connector again with the same URL. A new approval creates a fresh connection.
Did Claude publish something on its own?
No. Claude can draft and prepare, but publishing is always a manual step you take in the dashboard.

Developer reference

blog-maker exposes a Model Context Protocol (MCP) server, so you can drive it from your own agent, not just from Claude's connector UI. This section is the technical contract.

Connection and OAuth

  • •Endpoint: https://blog-maker.com/mcp (canonical for both blog-maker.com and blog-maker.de), over Streamable HTTP.
  • •Auth is OAuth 2.1 with PKCE. Dynamic Client Registration (DCR) is supported, so your client can register itself.
  • •Protected-resource metadata is advertised at /.well-known/oauth-protected-resource (RFC 9728) and referenced from the 401 challenge.
  • •Access tokens last 1 hour, refresh tokens 30 days (request the offline_access scope). Idle sessions expire after 30 minutes.
  • •One connection grants access to all of your brands. Isolation is enforced per user at the tool layer, not through per-brand scopes.

Scopes

Nine resource scopes gate the tools. Request only what your client needs; each tool checks its scope before it runs.

  • briefs:readRead briefs and topic gaps.
  • briefs:writeCreate, edit and dismiss briefs.
  • articles:readRead articles, exports and usage.
  • articles:writeEdit article drafts and regenerate article images.
  • articles:convertGenerate an article from a brief (spends a credit).
  • products:readRead product texts and generation status.
  • brand:readRead brand details, analytics and publish targets.
  • brand:writeUpdate brand writing style, business goals and content-length settings; refresh the sitemap.
  • products:writeCreate, regenerate and optimize product texts.

Tool catalog

30 tools, grouped by the access they need. Reads never mutate and are not rate-limited; writes create or change content.

Read tools (19)

  • list_brandsbrand:read
    List brands you own or manage.
  • get_brandbrand:read
    Brand details: voice, language, compliance rules.
  • list_briefsbriefs:read
    List briefs for a brand.
  • get_briefbriefs:read
    Brief details and outline.
  • find_topic_gapsbriefs:read
    Discover topic opportunities from sitemap and pillars.
  • find_from_gscbriefs:read
    Discover keyword gaps from Google Search Console.
  • list_articlesarticles:read
    List articles for a brand.
  • get_articlearticles:read
    Get an article draft or its published version.
  • get_article_statusarticles:read
    Poll article generation progress.
  • get_article_exportarticles:read
    Export an article as Markdown plus frontmatter.
  • list_publish_targetsbrand:read
    List configured publishing destinations. "funnelexpert"-type targets use the content_blocks format (see /docs/content-blocks).
  • get_usagearticles:read
    Current credit usage and plan details: articles, podcast episodes and video conversions.
  • get_brand_analyticsbrand:read
    First-party traffic and engagement analytics.
  • get_gsc_performancearticles:read
    Raw Google Search Console performance data.
  • list_productsproducts:read
    List WooCommerce products for a brand.
  • get_productproducts:read
    Get a product's text.
  • get_product_statusproducts:read
    Poll product generation progress.
  • get_brand_healthbrand:read
    One-call onboarding checklist: briefs, GSC connection, length settings, clusters, remaining quota.
  • list_podcast_episodesarticles:read
    List a brand's podcast episodes: processing status, feed inclusion, duration and the linked article.

Write tools (11)

  • create_briefsbriefs:write
    Create content briefs for planning.
  • update_briefbriefs:write
    Edit a brief's outline, persona, keywords or title.
  • dismiss_briefbriefs:write
    Archive a brief.
  • refresh_brand_sitemapbrand:write
    Re-fetch and index the brand sitemap.
  • update_brandbrand:write
    Update writing style, business goals and content-length settings.
  • convert_brief_to_articlearticles:convert
    Generate an article from a brief (uses 1 credit, 3-5 min).
  • update_articlearticles:write
    Edit an article draft.
  • regenerate_article_imagesarticles:write
    Regenerate an article's images.
  • create_productproducts:write
    Generate WooCommerce product text (1 credit, Basic plan or higher).
  • regenerate_productproducts:write
    Regenerate an existing product text.
  • optimize_product_imagesproducts:write
    Optimize product image assets.

How find_topic_gaps clusters topics

find_topic_gaps groups its suggestions by topic and intent: it maps a new topic to an existing pillar when one clearly fits, or proposes a new shared cluster name across related suggestions when it does not. This is lightweight topical grouping from a single model call, not full SERP-overlap keyword research (no search volume, no competitor SERP analysis). If you need that depth, pair blog-maker with a dedicated SEO research tool and bring the resulting cluster names back into create_briefs.

Rate limits

Write tools are limited to 20 calls per minute per user. Read tools are not rate-limited. Exceeding the write limit returns the rate-limit error below; try again after a minute.

Errors

Tool-level errors come back as a normal tool result flagged as an error, with a plain-language message (there are no numeric error codes). Authentication failures are an HTTP 401 with a WWW-Authenticate header.

Missing or invalid Bearer token

HTTP 401 invalid_token: "A valid OAuth access token is required"

Token lacks the required scope

Missing required scope: <scope>

Too many write calls

Rate limit reached: too many write operations. Try again in a minute.

Write on a read-only shared brand

This brand is shared with you read-only; you cannot create or change its content.

The tool handler threw

The tool failed. Please try again.

No publish tool

There is deliberately no publish tool over MCP. Your agent can research, draft, edit and export, but taking an article live stays a manual step in the dashboard. Podcast hosting is mostly dashboard-only, too: uploading episode audio, editing show settings, cover upload and toggling feed distribution are not exposed. list_podcast_episodes and get_usage give your agent read-only visibility (processing status, feed inclusion, duration, and your remaining podcast/video-conversion quota) so it can reason about the show without touching it.

<- Back to home