N2N Post2Site
A narrow MCP bridge that lets AI assistants draft and publish website content through a protected backend content API.
n2n-post2site is built around a strict boundary: AI can help draft content, but the website backend remains the source of truth. The MCP server validates tool input and forwards calls to a protected Content Publishing API; it does not hold the database, bypass review, upload arbitrary files, run shell commands, or deploy the site.
The product focuses on governance. It supports discovery, scoped context, draft creation, one-locale updates, draft resumption, and explicit publishing. Scoped content such as product guides is written after the assistant reads backend-provided context. This makes it useful for teams that want AI-assisted blog posts, guides, release notes, and localized drafts without giving an assistant broad admin access.
Publishing Boundary
Scoped Context
Let the backend define content scopes such as product guides and provide controlled context.
Thin MCP Bridge
Validate tool calls and forward them to a site-owned content API instead of storing content locally.
Draft Workflow
Create, update, list, and resume drafts one locale at a time.
Explicit Publishing
Keep drafting and publishing separate so review remains intentional.
MCP client setup
{
"mcpServers": {
"n2n-post2site": {
"command": "npx",
"args": ["-y", "n2n-post2site"],
"env": {
"CONTENT_API_BASE_URL": "https://your-site.com/api/v1/mcp",
"CONTENT_API_KEY": "your-api-key"
}
}
}
}
Documentation