MCP returns 401
A 401 is normal until OAuth or a site-scoped token authenticates the client. Start from protected-resource discovery; do not work around it with a token in a prompt.
Open the related guide →Open-source help
Troubleshoot setup, MCP connections, draft delivery, and Search Console evidence without expanding agent authority.
MCP & Connections
A 401 is normal until OAuth or a site-scoped token authenticates the client. Start from protected-resource discovery; do not work around it with a token in a prompt.
Open the related guide →Content & Review
Reread the post and use its current expected_updated_at value. The conflict protects a newer edit from being overwritten.
Open the related guide →No. The highest agent authority is an approved CMS draft delivery.
Open the related guide →CMS Draft Delivery
Review the current packet, resolve its blocker, keep the destination explicit, and retry only with the current version.
Open the related guide →That is the intended boundary. BlogFactory creates CMS drafts for human review; it never live-publishes or deletes.
Open the related guide →Self-hosting
Health confirms the API process responds. Readiness confirms required dependencies are available for work.
Open the related guide →Docker Compose is the canonical installation. Railway has a guided topology; Vercel is expert-only and Netlify is unsupported.
Open the related guide →No. Your self-hosted app, data stores, and AI credentials remain in your infrastructure.
Open the related guide →Getting Started
No. Cloud is coming soon; there is no hosted signup, plan, billing, or SLA today.
Open the related guide →Search Growth
Reporting is delayed and limited. Use complete-day evidence and URL inspection or sitemaps for a narrow diagnosis.
Open the related guide →No matching answer. Check the docs or open a GitHub issue.
Still stuck?
Do not include credentials, tokens, or private content in an issue.
Open GitHub Issues →