An MCP server for SEO and content distribution.

List the workspace's generated posts. Free (rate-limited, not billed). Optional filters: domain_id, platform, status, limit.

Generate draft posts for an atomized page — one per connected channel of the page's domain. Metered against the workspace's API credit balance; costs nothing when every channel is already covered.

Fetch a URL, extract content atoms with the LLM, and store the page. The URL's domain must already exist in the workspace. Metered against the API credit balance.

Search Pexels and Unsplash for a photo (the same library the dashboard's picker uses). Free. Pass a result straight to attach_image.

Attach an image to a page so generated posts carry it. Free. Use image_url for your own image, or source_url from a search_images result. Attach BEFORE generate — Pinterest cannot publish a post with no image.

Publish a generated post now, or schedule it with scheduled_at (ISO-8601, future). Metered; an X/Twitter publish additionally debits the X credit wallet, same as from the dashboard.

List the workspace's domains (sites). Free. Every Network tool takes a domain_id from here.

A domain's Network at a glance: each network (a ranking page with posts pointing at it), drafts waiting for review, and the autopilot mode. Free.

The best-ranking published posts and the host pages (threads, answers, articles) with nothing pointing at them yet — good places to start a network. Pass one to start_network as kind + id. Free.

The domain's connected channels that can carry a link — the account_ids a campaign, a connection or autopilot may post from. Free.

One network: the page at its centre and every post pointing at it (drafts included), with impressions, clicks and rank. Free.

Published posts ranked by how they're doing (impressions, clicks, engagement), best first. A winner is a good node to start a network from (start_network with kind 'post'). Free.

The planner's best next connections: which account should post at which ranking page next, with the reasons. Write one with write_network_connection. Free.

Write one suggested connection: the account writes a post pointing at the node. Billed like a generated post. If the domain's autopilot is 'auto', the post is scheduled to go live; otherwise it waits for review.

Turn a page into a network node: either any URL (a thread, answer, article, or one of your posts) with domain_id, or a candidate from list_network_start_candidates as kind + id. Writes no posts and is free — follow with create_network_campaign.

The domain's campaigns — what keeps posts pointing at each node, and when each runs next. Free.

Put posts behind a node from start_network: a campaign that writes posts pointing at it on a schedule, from the accounts given. Writes the first post now unless write_first_post is false (billed like a generated post); later posts use the plan's amplification allowance. Under autopilot 'auto', posts go live on their own.

Set a campaign to active, paused or cancelled. Cancelling can't be undone. Free.

Write the campaign's next post now instead of waiting for its schedule. Billed like a generated post; free when nothing could be written.

How a domain's Network autopilot is set: auto, review or off, plus posts per day and accounts. Free.

Turn a domain's Network autopilot to 'auto' (writes the best posts daily and publishes them live), 'review' (writes them; they wait for approval) or 'off'. Fields left out keep their value. Needs an admin's API key. Free; posts it writes later use the plan's allowance.

Schedule every network draft waiting for review on the domain (or one network's, with node_id) at each platform's next open slot. Billed per post published, like publish_post.

What is an MCP server, and why does this one exist?

MCP (Model Context Protocol) is the standard way an AI assistant connects to an outside tool. This server exposes the same pipeline the dashboard runs - atomize, generate, publish - so you can drive distribution from a conversation, or from an agent, instead of clicking through the app.

Does the MCP server do anything the API doesn't?

No, deliberately. Every tool call is forwarded to the same /api/v1 endpoint a curl would hit, carrying the same key, through the same auth, rate limiting and metering. MCP is a thin adapter over the REST API, not a second path with its own rules.

Will it publish something without asking me?

It can't publish anything you haven't set up: publishing requires a paid plan with a connected channel, and the tool that publishes is flagged destructive, so clients confirm before running it. Generation stops at drafts, which land in the same review queue the dashboard uses.

What does it cost to run?

Reads are free. Atomizing a page is $0.40, generating is $0.15 per post actually created, and publishing is $0.05 per post. The balance is checked before any work runs, so an out-of-credits call is refused and costs nothing.

Which clients does it work with?

Any MCP client that speaks Streamable HTTP. Claude (claude.ai and the desktop app) connects with OAuth - you sign in and click Allow. Claude Code and other clients can use OAuth too, or send an API key in the Authorization header. The Claude Code plugin is a packaged version of the same connection.

Is automated distribution against search engine guidelines?

Publishing original, platform-native content with a contextual link to your own page is normal distribution. What draws penalties is fabricated engagement, fake personas, and the same text duplicated everywhere - none of which this does. Each post is generated from a distinct content angle.