OmniCon runs a public MCP (Model Context Protocol) server at https://mcp.omnicon.cloud/. It exposes almost every CMS action — create articles, build books, upload media, curate galleries, plan category trees, send press releases, run a community — as callable tools that Claude Desktop, Claude Code, Codex, or any MCP-compatible client can invoke.
Why use it
- Draft and publish content from a conversation with Claude instead of the web editor.
- Plan a channel's folder/category structure before you write a single article — titles, descriptions, sort order, all from chat.
- Script bulk operations (migrations, reorgs, backfills) without writing against the API directly.
- Curate image galleries — portfolios, event recaps, product ranges — without leaving chat.
- Run a community — approve pending posts, change roles, ban abusers — from chat instead of clicking through the admin.
- Let agents handle repeatable work — scheduled posts, translations, press list maintenance.
Transport and auth
The server speaks Streamable HTTP at the root path (https://mcp.omnicon.cloud/) and authenticates via OAuth 2.0 with PKCE. Your client walks a standard authorization-code flow in the browser and gets a scoped token tied to your OmniCon account. No API keys to manage.
Related topics: