contentops mcp

Stop publishing weak, unoptimized, or broken content to your website. This MCP skill acts as a quality gate between your drafts and your live WordPress site, enforcing SEO standards and brand voice before anything goes live. It eliminates the manual work of checking meta descriptions, verifying internal links, and moving content from Notion to WordPress.

What it does

• Quality auditing: Scores drafts from 0-100 based on SEO, readability, and brand voice using rule-based logic.
• Automated staging: Creates WordPress drafts from Markdown content or directly from Notion databases.
• Link validation: Checks absolute internal links within your draft and flags 404s before they reach readers.
• Smart gating: Automatically pauses the publishing pipeline if high-severity issues like missing meta descriptions are found.
• Multi-channel notifications: Sends status updates and live URLs to Slack or via email using Resend once publishing is successful.
• Run tracking: Maintains a local JSON history of every workflow run for auditing and debugging.

How it works

1. Validation: Use qa_check to score a Markdown draft and receive a list of specific fixes for SEO or brand violations.
2. Staging: Invoke publish_with_qa to push content to WordPress as a draft and run the automated gate check.
3. Review: The agent reports the score; if the gate passes, the run waits in a paused state for human confirmation.
4. Deployment: Execute approve_and_publish to take the post live once you have reviewed the agent's feedback.

Frameworks & tools

Built with Python 3.10+, this skill utilizes the Model Context Protocol (MCP). It integrates with WordPress (REST API), Notion, Slack (Webhooks), and Resend.

Why this beats prompting it yourself

Standard prompts often fail to check technical constraints like exact character counts or link validity consistently. This tool uses deterministic code to verify links and SEO metadata, ensuring your publishing requirements are met every time without LLM hallucinations.

Use cases

• Automating the move from a Notion "Content Calendar" to WordPress drafts.
• Preventing broken internal links in technical blog posts.
• Enforcing brand voice by flagging banned hype words in marketing copy.
• Ensuring every post has a correctly sized meta description for SEO.

Known limitations

QA is rule-based and does not judge writing style or fact-check information. Link checking only validates absolute links on the same domain. Yoast or RankMath SEO fields are not populated.