asimons81/wp-chatgpt-publisher — explained in plain English
Analysis updated 2026-05-18
Let an editorial team draft and revise WordPress posts through ChatGPT without giving out the admin password.
Set up scoped, revocable access for ChatGPT to manage images, tags, and SEO fields on a site.
Require an explicit one time confirmation before ChatGPT can publish or schedule a post.
Self host the connector service on your own infrastructure instead of a third party relay.
| asimons81/wp-chatgpt-publisher | 1476989162/vue-bill-print | 1e3pm/knowledge-chatbot | |
|---|---|---|---|
| Stars | 11 | 11 | 11 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs Docker, PostgreSQL, HTTPS, and two independently generated 32 byte secret keys.
Editorial Publisher for ChatGPT is an open source project that lets ChatGPT work directly on a WordPress website, searching for content, writing and revising drafts, managing images and tags, and adjusting SEO fields, without ever being given the site's main admin password or an OpenAI API key. Instead, the site owner logs into their own WordPress site and approves the connection there, similar to how you might approve a third party app to access an email account, and ChatGPT only ever gets a limited connection scoped to what was approved. Because there is no separate call to an AI provider, the project does not create a pay per use API bill of its own. Normal ChatGPT subscription limits still apply. The system has two halves: an open source service that ChatGPT talks to using an authentication standard called OAuth together with a protocol called MCP, and a WordPress plugin installed on the site itself that checks the connection, switches to the approving user's own account, and applies rules about what that user is allowed to do. Publishing or scheduling a post only happens after a short lived, one time confirmation step, so nothing goes live by accident. Running it locally for testing needs Node.js, Docker, and a few generated secret keys placed in a configuration file, after which a single Docker Compose command starts both WordPress and the connector service. For production use, the service can be deployed as a container image, run directly with Node, or hosted on Vercel, and needs a PostgreSQL database behind it. The WordPress plugin is installed separately from a downloadable zip file, and connections are organized into three access levels: read only, an editorial level that also allows drafting and tagging, and a publisher level that adds scheduling and publishing on top. The project is licensed under GPL 2.0 or later, and its documentation covers security details such as encryption, token handling, and how it treats content pulled from the website as data rather than as instructions.
Lets ChatGPT draft, edit, and publish WordPress posts through an approved connection, without sharing your admin password.
Mainly TypeScript. The stack also includes TypeScript, Node.js, Docker.
Free to use and modify, but if you distribute a modified version you must also release it under the same GPL license.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.