Documentation

Start here

Five steps, about ten minutes. Nothing is contacted until you finish the first one.

1. Choose a providerSettings, Connect a provider. The free ones are at the top. Nothing is chosen for you.
2. Paste the keyEach provider has a link to the page on its own site where the key is issued. A model on your own machine needs no key. Save.
3. Pick a modelPress "Show the models on my account". Never type an id from memory.
4. Describe your voiceTwo sentences on your subject and your reader. Or press "Learn from my posts".
5. Write one postGive it a topic and read the score before you publish anything.

Connecting a provider

Dicecodes AI Blog Writer has no AI of its own. It uses your account, and your provider bills you directly.

Every request goes from your site straight to the provider you chose, and is billed to you by them. Nothing passes through a server of ours, because there is not one.

Pick the provider you already have an account with. If you have none, Groq and Google both have free tiers large enough to write with, and Ollama runs a model on your own machine for nothing at all.

Three fields matter: the provider, the key, and the model id. Take the model id from your provider's own model list rather than copying an example, because these get retired without notice. Leave the base URL blank unless you are pointing at something of your own.

1. ProviderGrouped by what it costs, free first. Nothing is preselected.
2. KeyFollow the link to the provider's own site, where the key is issued. A local model needs none.
3. Model idTake it from your own account, not from an example. Retired ids fail with an error that does not say so.

• Free, no key, no account: Ollama, LM Studio, Jan, llama.cpp. They run on this machine and contact nobody.
• Free tier, a key but no card: Google, Groq, Mistral, Hugging Face. On OpenRouter the free ids end in :free.
• Nothing is held back on a free provider. There is no paid tier here to unlock.
• On WordPress 7.0 and later, "WordPress AI Client" appears when a provider plugin is installed. No key here at all.
• Leave the base URL blank unless you are pointing at a proxy of your own.

Writing from Claude or ChatGPT

Use the subscription you already pay for. No API key, and usually no token either.

There are two ways to run this plugin. The other has your site call a provider using your key. This one is the reverse: an application you already pay for connects to your site and does the writing, while the writing rules, the checks and the publishing all stay on your site. If you already have a Claude or ChatGPT subscription, this costs nothing extra.

It works with anything that speaks the Model Context Protocol — Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code and others. Switch it on, issue a token, and paste the address and the token into that app. Your site has to be reachable over HTTPS from the internet for the app to find it.

A connected client can read your rules, score and revise drafts, and publish above your threshold — adding the pictures, tags and links as it goes. It cannot write on a schedule, touch a post it did not create, or use your research sources. Scheduled writing needs an API key, because something has to be running when nobody is watching.

A token is a key to this site. It is shown once, stored only as a fingerprint, and stops working the moment the person it was issued to loses permission to write here. Revoke any you are not using.

1. Choose the AI client waySettings. The first question on the screen is which way you want to write. Pick the second one.
2. Copy the addressThe Settings screen shows the address at the top, with a button that copies it.
3. Paste it into your appClaude: Settings, Connectors, Add custom connector. ChatGPT: Settings, Connectors, Advanced, Developer mode, Create.
4. Approve the connectionThe app sends you back here. Sign in if you are asked, read what it will be allowed to do, then press Approve.
5. Ask it to write"Read my writing rules and write a post about X for my site."

• Claude Code, Cursor and VS Code take one command instead. The Settings screen shows the exact command, ready to copy.
• Your permalinks must not be set to Plain. On that setting the address an app looks up to find the sign-in never reaches WordPress.
• The app then reports that your site is not an MCP server, which is not what is wrong with it.
• Your site must be reachable over HTTPS from the internet. A laptop install will not work.
• If an app cannot sign in, issue a token on the Settings screen instead, and set that app to no authentication.
• Then add a request header named Authorization, with the value Bearer followed by a space and the token.
• If a token is refused, your server is stripping the Authorization header. Add CGIPassAuth On to your .htaccess, or ask your host to pass it through.
• A connected app can read your rules, score and revise drafts, and publish above your threshold.
• Publishing adds the pictures, the search title, the tags and the links from older posts, same as the other way.
• It still cannot write on a schedule, or touch a post it did not create.
• Scheduled writing needs a provider key on the other path, because something has to be running when nobody is watching.
• Disconnect an app at any time from the same card. Revoking its token cuts it off immediately.

Describing your voice

Sent with every request. The reason two blogs on the same model do not read alike.

If you already have posts published, use "Learn from my posts". It measures how you actually write — sentence length, paragraph length, whether you use em dashes or contractions, whether you say "I" or "you" — and drafts the descriptions from your own titles. Nothing is saved until you press save.

The experience field is the one worth spending time on. It is the only part of a post a model cannot produce, and it is what stops the writing being a summary of pages that already exist.

• Two sentences on your subject and your reader is enough to start.
• "Learn from my posts" measures how you actually write and fills the fields in. Nothing saves until you press Save.
• Posts Dicecodes AI Blog Writer wrote are left out of that. Learning from its own output ends with every post sounding like the first.
• The experience field is the one worth time. It is the only part of a post a model cannot produce.

How it writes

The standing brief every post is written to.

• Start from a shape — guide, listicle, tutorial — and about twenty fields are set at once. All stay editable.
• Or paste the address of an article you admire. Its structure is measured and becomes your rules.
• Structure only. No wording is copied, kept, or shown to a model.
• Anything shown in monospace is measured on the finished draft, not merely asked for.

Writing a post

One required field. Everything else already has an answer.

1. TopicA sentence beats a keyword: "how to choose a standing desk for a small office".
2. What only you knowYour figures, prices and results. Used as fact, and checked for on the finished draft.
3. The tabs beneathPictures holds the art direction. Publishing sets the category, tags, author and time.

• Stuck on the second one? A button asks you four specific questions instead. It never answers them for you.

Research

The biggest single lever on whether a post is worth reading.

Without sources it writes from memory, which dates badly and which search engines discount.

Every source starts off. Wikipedia and Hacker News need no key, so switching one on is all they need. Tavily and SerpApi are paid but return more current results. A SearXNG instance is free if you host one.

Anything found here is also used to check the finished draft: if the article merely restates its sources, the score says so and the rewrite is told to fix it.

• Off, the model writes from memory. On, it writes from current sources.
• Everything starts switched off. Turning a source on is how you consent to it.
• Wikipedia and Hacker News need no key. Tavily and SerpApi are paid and more current.
• A SearXNG instance you host is free. You can also list URLs to be read for every post.
• What is found also checks the draft: merely restating your sources costs points.

Pictures

The article decides what a picture shows. These controls decide how it looks.

Pictures come from a different kind of service than the writing does, so they are set up separately. Nothing here is required, and nothing runs until you switch pictures on — that switch is how you tell the plugin it may contact a picture service. Pollinations needs no key and is the one it starts on.

The model that wrote the post describes the scene it should show, and the Pictures controls on the How it writes screen decide how that scene looks.

fal.ai, OpenAI, Gemini and Grok charge per picture. They are only ever used when you pick one of them, never as a fallback, so an image is never billed to you by accident. If you already write with OpenAI, Google or xAI, choosing the same one here uses the key you have already entered.

Pexels and Pixabay search real photographs rather than drawing anything. Their keys are free.

• The model that wrote the piece describes the scene — the difference between a useful image and clip art of the headline.
• Pollinations needs no key. fal.ai, OpenAI, Gemini and Grok charge per picture and run only when you pick them.
• Writing on OpenAI and pictures on OpenAI? Leave the image key blank and one key does both.
• Text is kept out of generated images by default. Image models render lettering as convincing gibberish.

What is checked

Every draft is measured before it becomes a post, and each failure is written back into the rewrite as an instruction.

• Does the opening answer the question in its first two sentences?
• Does every section stating a figure carry a link beside it?
• Does the draft say anything its sources do not already say?
• Is the subject in the title, a heading, the address and the first hundred words?
• Did the figures you supplied actually reach the page?
• A check that cannot be assessed is skipped, not failed. The score is what was earned out of what was offered.
• Two limits: the figure check does not open the link to confirm the number, and the originality check only sees the sources it was given. It is not a plagiarism service.
• Anything below your threshold is held for review instead of published.

Where posts go

A finished post is a normal WordPress post.

• Written as real blocks, so every paragraph and heading is editable in the editor.
• Saved as a draft by default. You will find it under Posts.
• Anything below your threshold is set to pending and listed under "Needs review".
• Images are downloaded into your Media library, not hotlinked. Alt text comes from the heading each one illustrates.

Automation

Not needed to write a post by hand. Switch it on once the writing already looks right to you.

Automatic posts are saved as drafts unless you say otherwise, and anything scoring below your threshold is held for review whatever you chose. The daily cap and the monthly token cap are both there to make a mistake cheap.

Pictures are optional. Pollinations needs no key. fal.ai and OpenAI charge per image and are only ever used when you pick one of them, never as a fallback.

• Automatic posts are saved as drafts unless you say otherwise.
• A daily cap and a monthly token cap are both there to make a mistake cheap.
• WordPress runs scheduled work only when somebody visits, so a quiet morning can push a post past the hour you chose.

Checking it works

The test on the settings screen sends one short request and reports exactly what came back.

It costs a fraction of a penny, and it is the fastest way to tell a wrong key from a wrong model id from a provider that is simply down.

Saving a key runs this automatically, so a mistake is caught at the moment you make it rather than on a cron tick nobody is watching.

• It costs a fraction of a penny, and it separates a wrong key from a wrong model id from a provider that is down.
• Saving a key runs it automatically, so a mistake is caught when you make it.
• If a post fails, Activity says why.
• Rate limits are waited out rather than counted as failures.

What leaves your site

Dicecodes AI Blog Writer contacts no servers of its own and sends nothing to the plugin author.

• No analytics, no telemetry, nothing phoning home.
• Only the services you configure, and only while a post is being written.
• Your topic, your style settings and any gathered research go to the provider you chose.
• Keys are stored encrypted, never rendered back into the page, and stripped from every log line.
• The full list of services, with their terms and privacy policies, is in the readme under External Services.

Looking for an alternative?

Most AI writing plugins work one of two ways: you buy credits, or you pay a monthly subscription.

Dicecodes AI Blog Writer is the third way: you bring your own API key. The plugin is free and open source, the AI account is yours, and the bill comes from the provider at their own rates with nothing added.

If you arrived here looking for a free AI writer for WordPress, an AI content generator with no monthly subscription, a plugin that uses your own OpenAI or Gemini key, an open source alternative to credit-based writing tools, an autoblogging plugin that is genuinely free, or a way to run AI blog writing on a local model with no key at all — that is what this is.

If you delete this plugin

Deleting Dicecodes AI Blog Writer leaves your settings, your writing rules and your posts exactly where they are.

The setting on the Settings screen changes nothing about how posts are written. It decides one thing: whether deleting the plugin also deletes what it has stored.

Left alone, everything survives. That is deliberate — a plugin that quietly erases years of settings because somebody deleted it to reinstall it is a plugin nobody trusts twice, and dropping database tables cannot be undone.

Your posts are never affected either way. They are ordinary WordPress posts from the moment they are created, and they stay whatever happens to this plugin.

• Install it again and everything is as you left it.
• Deliberate: WordPress asks whether you meant to delete the plugin, not whether you meant to delete the rest.
• There is a box in Settings if you do want it all gone. Ticking it is the only confirmation there will be.
• Your posts are never affected either way. They are ordinary WordPress posts from the moment they are created.