How do I install Notipo?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Notipo need an API key?

No required environment variable is listed on this record.

When was Notipo last checked?

Last checked 2026-11-09. Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.

Notipo MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://app.notipo.com/api/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.kfuras-notipo https://app.notipo.com/api/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.kfuras-notipo": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://app.notipo.com/api/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.2.5
License

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Notipo

Open-source WordPress publishing for AI agents — MCP server, REST API, and CLI. Or sync from Notion.

Point your agent (Claude, Cursor, ChatGPT, n8n, any HTTP client) at Notipo and it publishes to your self-hosted WordPress — no plugin required. Notipo handles the full pipeline: markdown → Gutenberg conversion, image hosting in your WordPress media library, AI- or Unsplash-generated featured images, and Rank Math / Yoast / SEOPress / AIOSEO metadata applied automatically on publish.

Two ways to publish to WordPress

1. From Notion

Connect Notion, change a page status to Post to Wordpress or Publish, and Notipo handles the rest — markdown extraction, image caching to WP media library, featured image generation, SEO metadata via Rank Math / Yoast / SEOPress / AIOSEO.

2. From an AI agent, REST API, CLI, or n8n workflow

Notipo exposes a Model Context Protocol (MCP) server with 13 tools for AI agents, plus a REST API and a CLI. Claude Desktop, Cursor, Windsurf, Claude Code, ChatGPT — any MCP-compatible agent can publish posts end-to-end.

# CLI: publish a post end-to-end
npm install -g notipo
notipo posts create --title "Why Every Dev Should Have a Blog" --publish

# REST API: one call runs the full pipeline
curl -X POST https://app.notipo.com/api/posts/create \
  -H "X-API-Key: $NOTIPO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Hello","body":"## Intro\n\nMarkdown in, WordPress out.","publish":true}'

// MCP: drop into Claude Desktop config
{
  "mcpServers": {
    "notipo": {
      "type": "http",
      "url": "https://app.notipo.com/api/mcp",
      "headers": { "x-api-key": "your-api-key" }
    }
  }
}

See notipo.com/ai-agents for the full AI-agent integration story.

Hosted SaaS vs. self-hosting

The hosted version at notipo.com is the supported, batteries-included product — managed infrastructure, automatic upgrades, instant Notion webhook delivery, and a free tier with 5 posts/month. Pro is $19/month for unlimited posts plus AI featured images.

This repository is the same code that runs the hosted product. You can self-host it under the AGPL-3.0 license — see DEVELOPMENT.md for the local dev story and docker-compose.yml for production deployment with Traefik + Let's Encrypt.

Self-hosting is unsupported — no help beyond what's in this repo, no upgrade path. If you need any of those, the hosted product is faster, cheaper, and already running.

Tech stack

Backend: Fastify, TypeScript, Prisma, PostgreSQL 17
Job queue: pg-boss (Postgres-backed, no Redis)
Frontend (admin): Next.js 16 + shadcn/ui + Tailwind
AI: Google Gemini (featured images), Model Context Protocol (agent integration)
Other: Sharp (images), Stripe (billing), Resend (transactional email), Sentry (errors), PostHog (product analytics), Notion SDK, WordPress REST API
CLI: zero-dependency npm package, native fetch only

Monorepo (Turborepo + npm workspaces):

apps/
  api/     — Fastify backend, MCP server, job workers
  web/     — Next.js admin UI
packages/
  cli/     — `notipo` npm package (MIT-licensed thin client)
  shared/  — TypeScript types and enums
plugins/
  notipo-seo-meta-writer/  — WordPress plugin for Yoast/AIOSEO metadata bridge

Quick start (self-host)

You'll need: Docker, Docker Compose, a domain pointed at your server, a Notion integration, and a WordPress site with Application Passwords enabled (WP 5.6+).

git clone https://github.com/kfuras/notipo-app.git
cd notipo-app
cp apps/api/.env.example .env
# Edit .env — at minimum set DATABASE_URL, ENCRYPTION_KEY, API_KEY,
# DOMAIN, ACME_EMAIL, RESEND_API_KEY
docker compose up -d

The compose stack pulls multi-arch images (linux/amd64 + linux/arm64) from ghcr.io/kfuras/notipo-api and ghcr.io/kfuras/notipo-web, so it works on both x86 servers and Apple Silicon / ARM hardware.

The compose stack starts Traefik + the API + admin UI + Postgres, with Let's Encrypt TLS on first run. See docker-compose.yml for details.

For local development without Docker:

docker compose -f docker-compose.dev.yml up   # Postgres only
npm install
npm run migrate -w @notipo/api
turbo dev                                      # API on :3000, web on :3001

See DEVELOPMENT.md for the full development guide.

Documentation

API reference: notipo.com/docs/api/introduction
MCP server (13 tools): notipo.com/docs/api/mcp
CLI: notipo.com/docs/api/cli
n8n integration: notipo.com/docs/api/n8n
All docs: notipo.com/docs
Architecture & development: DEVELOPMENT.md and .claude/CLAUDE.md

License

This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0) — see LICENSE.

In plain English:

✅ You can use, modify, and self-host Notipo for any purpose, including commercial.
✅ You can fork it and contribute changes back.
⚠️ If you run a modified version as a hosted service, you must publish your modifications under the same license. This is the "Affero clause" — it closes the network-service loophole that plain GPL leaves open.
✅ The notipo CLI package is published to npm under MIT (it's just a thin API client wrapper).
✅ The notipo-seo-meta-writer WordPress plugin is published under MIT (compatible with WordPress's GPL ecosystem).

If you want to use Notipo's code in a proprietary hosted product without AGPL obligations, open an issue — commercial licensing may be available.

Contributing

PRs welcome. See CONTRIBUTING.md for guidelines and CODE_OF_CONDUCT.md for community standards.

For security disclosures, see SECURITY.md — please don't open public issues for vulnerabilities.

Notipo

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Notipo?

Does Notipo need an API key?

What transport does Notipo use?

When was Notipo last checked?

Documentation

Notipo

Two ways to publish to WordPress

1. From Notion

2. From an AI agent, REST API, CLI, or n8n workflow

Hosted SaaS vs. self-hosting

Tech stack

Quick start (self-host)

Documentation

License

Contributing

Links