MCP Alpha

N2N Post2Site

N2N Post2Site is an MCP server that lets an AI assistant write and publish content for a website. The assistant first reads the site's content rules and existing content to avoid repeating topics, then drafts the article, checks it against the site's rules, produces a preview and can upload a selected image; nothing is published until the user explicitly confirms. It works through the content API the website provides and does not delete content or touch the database or server. You can try it first with the included mock backend and then connect a real website, for example a Laravel site with Laravel Post2Site installed.

What it does

Writing for a website with an AI assistant usually means copying text back and forth between the chat and the site's admin panel, and checking by hand whether a topic has already been covered and whether the article meets the site's requirements. N2N Post2Site connects the assistant directly to the website's content API. The website states what content it accepts, which editorial guidelines apply and what it has already published; the assistant works within those rules, and the website itself always decides what is stored and published.

How publishing works

  1. The assistant reads the site's description, content fields and editorial guidelines, reviews existing content and statistics, and checks whether a planned article overlaps with content that already exists, so that topics are not repeated.
  2. It drafts the article, either as new content or, where the website supports it, as an update to an existing item, and saves it on the website as a draft. Drafts can be listed and revised later.
  3. The draft is checked against the site's rules. The check separates problems that block publication from warnings, which the user can explicitly accept.
  4. The assistant gets a preview link so the user can see the article as it will appear on the site, and it can upload the image the user has selected, for example as a cover image.
  5. The article is published only after the user explicitly confirms it.

The assistant cannot delete content and has no access to the website's database or server; every action goes through the website's content API.

Who it is for

Website owners, editors and developers who want an AI assistant to help write articles for their own site while keeping full control over what goes live.

What you need

  • Node.js 22 or later, and an AI assistant or editor that supports MCP servers, including reading MCP resources (the assistant reads the site's rules from them).
  • A website that provides the Post2Site content API, with its address and an API key. On a Laravel site, Laravel Post2Site provides this API.
  • To try it before connecting a real website, the repository includes a mock backend that keeps its content in memory; start it as shown below and connect with the demo key.

N2N Post2Site is open source under the MIT license.

MCP Server AI Writing Website Publishing Open Source
Guides GitHub

MCP client configuration

{
  "mcpServers": {
    "n2n-post2site": {
      "command": "npx",
      "args": [
        "-y",
        "n2n-post2site"
      ],
      "env": {
        "CONTENT_API_BASE_URL": "https://example.com/your-content-api",
        "CONTENT_API_KEY": "your-content-api-key"
      }
    }
  }
}

Try it with the mock backend

git clone https://github.com/n2ns/n2n-post2site.git
cd n2n-post2site
node examples/mock-backend/server.mjs
# Then point the MCP server at it:
# CONTENT_API_BASE_URL=http://127.0.0.1:8787
# CONTENT_API_KEY=demo-key