You can hand Grok Bot your WordPress blog and have it draft and publish for you. No custom plugin required. The setup is Application Passwords + the WordPress REST API, and once it’s working you can ask for a draft in plain English.
This is the exact path we use on Daily AI Blog. Copy it, swap in your site, and you’re done in about ten minutes.
What You’ll Need
- A self-hosted WordPress site (or WordPress.com with REST API access)
- An administrator (or Author+) account
- Grok Bot access (Cursor Ultra, Cursor Premium Teams, or SuperGrok Heavy)
- About 10 minutes
Step 1: Create a WordPress Application Password
Don’t give Grok Bot your normal login password. Application Passwords are revocable tokens made for API access.
- Log into WordPress admin
- Go to Users → Profile (or Users → Your Profile)
- Scroll to Application Passwords
- Name it something clear, like
Grok Bot - Click Add New Application Password
- Copy the password immediately — WordPress only shows it once
It looks like a spaced string, for example xxxx xxxx xxxx xxxx xxxx xxxx. Keep the spaces. You’ll paste it into Grok Bot once.
Tip: If you don’t see Application Passwords, your host may have disabled them, or you’re on a setup that requires HTTPS. Fix that first.
Step 2: Note Your Site URL and Username
Grok Bot needs three values:
- Site URL — e.g.
https://yoursite.com(no trailing path) - Username — the WordPress login username, not your display name
- Application Password — the token from Step 1
Quick check that REST is alive before you involve the Bot:
https://yoursite.com/wp-json/wp/v2/You should get JSON back in the browser. If that 404s, permalinks or REST access need fixing on the host.
Step 3: Hand the Credentials to Grok Bot
Open Grok Bot and say something like:
Connect to my WordPress site so you can draft and publish posts for me.
Site: https://yoursite.com
Username: your-wp-username
Application Password: xxxx xxxx xxxx xxxx xxxx xxxxAsk it to:
- Verify auth against
/wp-json/wp/v2/users/me - Confirm it can create drafts
- Store the credentials securely for later runs
A healthy response looks like: authenticated as your user, role Author/Editor/Administrator, and edit_posts / publish_posts enabled.
Security note: Prefer a dedicated Application Password per Bot. If anything looks off later, revoke that one password in your profile without changing your main login.
Step 4: Create Your First Draft
Once connected, keep the ask concrete:
Draft a blog post about [topic] in our usual style and save it as a WordPress draft.
Don't publish yet.Good briefs include:
- Topic and angle
- Audience (beginners, builders, etc.)
- Length target
- Whether to match existing posts
- Publish vs draft
Example:
Write a practical tutorial on setting up WordPress blogging with Grok Bot.
Match the tone of our recent Claude Code posts. Save as draft only.Step 5: Review, Then Publish
Have Grok Bot return:
- Post ID
- Title
- Admin edit link
- Public link (once published)
Review in wp-admin, then either publish yourself or say:
Publish post [ID].Keep publishing behind an explicit ask until you trust the workflow. Drafts are cheap. Accidental publishes are not.
Useful Prompts After Setup
Draft from a brief
Draft a post on [topic]. Use H2 sections, practical steps, and a short bottom line. Save as draft.Finish an existing draft
Open draft [ID], tighten the intro, add a checklist section, and keep it as draft.Publish intentionally
Publish post [ID] and send me the live URL.Daily cadence
Every weekday morning, draft one AI tooling post based on what's new, save as draft, and ping me the edit link.That last one is how you turn a one-off connection into a publishing habit.
Troubleshooting
401 / invalid credentials
- Username is wrong (use login name, not email/display name, unless your host accepts email)
- Application Password was copied without spaces or with an extra character
- Password was revoked
REST endpoint not found
- Visit
/wp-json/in a browser - Flush permalinks: Settings → Permalinks → Save
- Check security plugins that block REST for unauthenticated or application-password requests
Can draft but can’t publish
- User role lacks
publish_posts - Ask Grok Bot to leave posts as drafts and have an Editor publish
Want to disconnect
- Revoke the Application Password in Users → Profile
- Tell Grok Bot to forget the stored credentials
Optional: Make It a Standing Routine
Once the connection is solid, give Grok Bot a recurring job:
Create a weekday morning routine:
1) Research one timely AI topic
2) Draft a post in our style
3) Save it as a WordPress draft
4) Message me the title + edit link
Do not auto-publish.You stay in the approval loop. The Bot does the grind.
Bottom Line
- Create an Application Password
- Give Grok Bot your site URL, username, and that password
- Ask it to verify REST access
- Draft first, publish on purpose
- Turn the workflow into a routine when it feels reliable
That’s the whole setup. No marketplace connector required — WordPress already speaks REST, and Grok Bot already knows how to use it.
Share this article
Leave a Reply