PoolyPress is an open-source content platform for makers, small companies, and developers who need media management, publishing, i18n, and e-commerce — without the plugin sprawl of a traditional CMS.

It grew from 20 years of building on Joomla, Drupal, WordPress, Jekyll, Hugo, and Astro. The result is a single, self-contained Node.js stack with minimal dependencies that runs comfortably on a €5/month VPS.

First release is planned for May - 2026

Core Capabilities

📸 Media Management & Delivery

Upload-to-publish pipeline with automatic format conversion, responsive sizing, and video transcoding.

📱 Mobile & PWA

The frontend is a full Progressive Web App — installable, offline-capable, and shareable.

✍️ Content & Publishing

Widget-based pages with rich export options and aggregated feeds.

🌍 Internationalization

Widget-level translations, not page duplication. Update one paragraph without touching the rest of the layout.

🔍 SEO, Discoverability & AI-Readiness

Traditional SEO gets your pages indexed. But search is changing: Gartner forecasts a 25% drop in traditional search volume by 2026 as users shift to AI assistants for direct answers. PoolyPress addresses both worlds.

Classic SEO — Built In

Bot & Crawler Detection

The server identifies crawlers at the request level using two-tier User-Agent detection:

When a bot is detected, the server renders full static HTML with JSON-LD, Open Graph tags, and pre-rendered widget content — no JavaScript required. AI agents receive clean Markdown with frontmatter metadata instead. Human visitors get the standard SPA experience. Same URL, three response paths.

Answer Engine Optimization (AEO)

AI-driven search engines (Google AI Overviews, ChatGPT, Perplexity, Bing Copilot) increasingly serve direct answers instead of link lists. To be cited by these systems, content needs to be structured for extraction, not just ranking.

WebMCP — The Agentic Web

Google and Microsoft are incubating WebMCP at the W3C — a browser-native standard that lets AI agents call website functions directly via navigator.modelContext, rather than scraping HTML or interpreting screenshots. Chrome 146 Canary shipped an early preview in February 2026.

Why it matters for content publishers: as AI agents start transacting with websites on behalf of users, the sites that expose structured tool contracts will be reachable. Sites that don't become invisible to the agentic web.

PoolyPress is built for this shift. Its existing MCP server already exposes 17 tools over JSON-RPC 2.0 for content authoring. The same architecture — structured tool definitions, typed inputs, programmatic responses — aligns directly with WebMCP's declarative and imperative APIs. When browsers ship WebMCP support, surfacing PoolyPress capabilities to client-side AI agents is a configuration step, not a rewrite.

🛒 E-Commerce (Optional Module)

Any page or post can be turned into a product by tagging it with a price — no separate product database needed. This covers physical goods with cart, checkout, shipping, and returns, but also digital products: tag a VFS file or folder with a price, and the platform's ACL system handles access control automatically. Buyers get a scoped VFS grant; non-buyers see the listing but can't download. The same granular permissions that protect internal documents also gate paid content.

All pages marked as a product are automatically included in a Google Merchant XML feed — with pricing, availability, images, and descriptions pulled directly from the page's metadata. No manual feed management, no third-party plugin.

🤖 AI-Powered Authoring

AI tools are built into the editor, not bolted on.

🛡️ Security

Layered security applied consistently across all endpoints.

Editable Home & User Profiles

Home and user pages use the same widget system as content pages — no rigid templates.

Image

Image

Image

AI-Assisted Content Creation

AI tools are integrated at every stage of the authoring workflow — drafting, layout, and editing.

Image

Image

Image

Image

Image

Image

AI Image Wizard

A built-in studio for generating, editing, and versioning images with generative AI models.

Localization & i18n

Translations are managed at the widget level, not the page level. You can update a single paragraph without touching the rest of the layout.

Image

Image

Image

Security & Access Control

The platform applies security policies consistently across all endpoints. Beyond JWT auth and transport hardening, PoolyPress includes a granular Virtual File System (VFS) ACL system.

VFS Access Control Lists

The storage layer implements per-file, per-folder access control.

Platform Security Stack

MCP Agentic Integration

PoolyPress exposes its authoring capabilities as a Model Context Protocol (MCP) server — a single HTTP endpoint that lets AI agents in any MCP-compatible IDE create, search, edit, translate, and publish content programmatically.

How It Works

The MCP server speaks JSON-RPC 2.0 over a single endpoint. No SDK required — any HTTP client that can send JSON can be an MCP client. Authentication reuses existing Supabase JWT tokens.

flowchart TD
  A((Claude Code
Cursor
Windsurf)) -->|JSON-RPC 2.0| B{MCP Server}
  B --> C[Pages & Widgets]
  B --> D[Search & Categories]
  B --> E[VFS & Media]
  B --> F[Translations]
  B --> G[Image Generation]
  B -->|Research queries| H[Research Supervisor]
  H --> I[Site Content]
  H --> J[SerpAPI / Web]

All tools call server-side functions directly — no internal HTTP round-trips. The same caches, ACLs, and visibility rules that apply to the web UI apply to every MCP tool call.

Built-In Research Agents

Beyond content management, the MCP server includes a research supervisor that coordinates multi-source research. It searches your own PoolyPress content alongside the public web (via SerpAPI) to synthesize comprehensive answers — useful for competitive analysis, content gap research, or fact-checking before publishing.

The 17 Tools

Tool What It Does
search_content Full-text search across pages, posts, images, and files
find_pages / find_pictures / find_files Type-specific search
get_page_content Fetch a page's full widget tree, markdown, and metadata
create_page Create a new page with title, markdown, category, and tags
update_page_content Replace the primary markdown content of a page
update_widget / remove_widget Edit or delete individual widgets by instance ID
add_containers Append new widget containers (multi-column layouts, photo grids, tabs)
list_categories / find_by_category Browse and query the category hierarchy
generate_image Generate an AI image (Gemini) and upload it to storage
markdown_scraper Scrape any URL into clean Markdown
get_page_translations / set_page_translations Read and write per-widget translations
get_translation_gaps Find pages with missing or outdated translations
research_supervisor Coordinated internal + web research via SerpAPI

IDE-Native Content Workflows

Connect PoolyPress as an MCP server in Claude Code, Cursor, or Windsurf:

{
  "mcpServers": {
    "poolypress": {
      "url": "https://your-instance.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Once connected, you can combine PoolyPress tools with any AI skill — copy-editing, SEO auditing, content marketing — and run them against your live content.

What This Enables

Batch operations no CMS UI can match. A single agent session can audit 50 product pages, fix typos, standardize specs, fill in missing meta descriptions, and translate the results into three languages. Manually, that's days of clicking through admin panels. With MCP, it's one prompt — drawing on hundreds of available skills, internal documents, and web research.

Composability. PoolyPress tools are just functions. Combine them with a web scraper to turn competitor pages into comparison articles. Chain them with image generation to create product pages from a spreadsheet. Mix them with translation tools for a full localization pipeline.

Programmatic content as a first-class workflow. Authors, marketers, and developers all work from the same toolset. The CMS becomes an API you talk to, not a UI you click through.

Example Sessions

Content Audit
"List all products in the 'Products' category, review each page for typos, inconsistent specs, and weak copy — then apply the fixes."
Result: 16 pages audited, 13 updated in one session.

SEO Sweep
"Check all product pages for missing meta descriptions, duplicate titles, and keyword-stuffed headings. Fix them."

New Product Launch
"Create a product page for the new SJ40 extruder. Search existing Lydia pages for the format, generate a hero image, and file it under the Extruder category."

Multi-Language
"Translate the Elena injection machine page into Spanish and German. Keep the specs table formatting intact."

Competitive Research
"Scrape these three competitor pages, extract their feature lists, and draft a comparison article. Publish it to the Knowledge Base."

Image

References & Further Reading

SEO & Search

Social Commerce & Network Shopping

The storefront is moving from the website to the feed. By 2026, global social commerce is projected to surpass $2.1 trillion (CAGR 29%), with over $100 billion in the US alone. Platforms are no longer just discovery channels — they're closing the loop from impression to checkout without the user ever leaving the app.

Why it matters for PoolyPress: Every product page is already a Google Merchant XML entry with pricing, availability, images, and descriptions auto-generated from page metadata. The same structured product data (JSON-LD Product schema) that feeds Google Shopping is the foundation for TikTok, Instagram, and Meta catalog integrations. As social platforms converge on standardized product feeds, a CMS that outputs structured product data by default — rather than requiring plugins — is positioned to serve all channels from a single content source.

AI Personal Assistants & Agentic Commerce

The next layer beyond search engines and social feeds is the personal AI agent — software that browses, compares, and transacts on behalf of a user. By late 2026, an estimated 8.4 billion voice assistants will be active globally. The shift from "user searches for products" to "agent shops for user" changes what a website needs to expose.

What agents need from websites: Structured product data (JSON-LD), machine-readable content (Markdown, JSON), authenticated MCP tool endpoints, and predictable navigation. Agents don't click buttons or parse CSS — they call APIs and read schemas. Websites that only serve JavaScript-rendered SPAs with no structured fallback become invisible to the agentic layer.

Why it matters for PoolyPress: The platform already serves three response paths from every URL (SPA for humans, static HTML for crawlers, Markdown for AI agents) and exposes 17 MCP tools for programmatic interaction. When a user's OpenClaw agent or Gemini assistant needs to browse a product catalog, PoolyPress can respond with structured, authenticated, machine-readable content — no scraping required. The same architecture that serves today's bots will serve tomorrow's personal agents.