Gemini CLI drafts it. You approve it. PostDelegate posts it.DEV.to: Markdown articles with tags, a cover and a canonical URL.
How to post to DEV.to from Gemini CLI
- Add PostDelegate to Gemini CLI. Add the server to ~/.gemini/settings.json as below. Sign in with PostDelegate when Gemini CLI prompts you.
~/.gemini/settings.json
{ "mcpServers": { "postdelegate": { "url": "https://app.postdelegate.com/mcp-oauth-dynamic" } } } - Connect DEV.to in PostDelegate. In your DEV Community account settings, under Extensions, generate an API key. DEV owns that screen, so its wording may change.
- Ask Gemini CLI for a draft. Describe the post in plain words. Gemini CLI checks your DEV.to channel's rules, creates the post and sends back a preview link.
Teach Gemini CLI the posting rules
Save PostDelegate’s AGENTS.md in your repository and point to it from your GEMINI.md, so Gemini CLI follows the posting rules there. Agent files has the steps.
What to ask Gemini CLI
Mention any DEV.to setting in plain words and Gemini CLI fills it in. Gemini CLI can also read text files in your project, such as a changelog or a draft in Markdown.
- Draft a DEV.to article from this outline, with the tags javascript and webdev, and a canonical URL pointing to our blog.
- Schedule my DEV.to article for Tuesday at 15:00 under our organization, with the cover image from my media library.
- Turn docs/how-we-test.md into a DEV.to article with up to four tags, saved as a draft.
What Gemini CLI can do on your DEV.to channel
- Check the rules first. Before writing, it reads your DEV.to channel's length limit and required settings.
- Draft, schedule or post. It creates a draft, a scheduled post or an immediate post, and runs the same checks as the app.
- Use your media. It attaches files from your media library or adds one from a public link.
- Review and fix. It lists what is scheduled, changes the DEV.to settings of a post that has not gone out, and deletes posts you no longer want.
DEV articles are written in Markdown, and PostDelegate's composer switches to a Markdown editor when you select a DEV channel. You can set the title, up to four tags, a cover image, an optional organization and a canonical URL, then choose when the article goes out.
DEV.to settings Gemini CLI can fill in
| Setting | Notes |
|---|---|
| Title | Required, at least 2 characters. |
| Cover image | Optional. |
| Canonical URL | Optional. Use it when the article first appeared elsewhere. DEV rejects a canonical URL it already has. |
| Organization | Optional. Publish under one of your DEV organizations. |
| Tags | Up to 4, picked from DEV's tag list. |
Before you start
- DEV publishes the article straight away when the post goes out. Keep a draft in PostDelegate to hold it back.
- DEV rejects a canonical URL another article already uses.
The DEV.to channel guide has every field, and MCP tools lists exactly what an assistant can and cannot do.
Questions
Will Gemini CLI publish to DEV.to without asking me?
Do I need an API key to connect Gemini CLI?
Does it cost extra to use Gemini CLI with PostDelegate?
Can Gemini CLI attach images or video to a DEV.to post?
Can I set a canonical URL on a scheduled DEV.to article?
Will DEV keep my article as a draft until I publish it?
DEV.to from other assistants
Other networks from Gemini CLI
- YouTube
- Bluesky
- Mastodon
- Google Business Profile
- Telegram
- Discord
- Slack
- Tumblr
- Lemmy
- Nostr
- Twitch
- Kick
- Dribbble
- Medium
- WordPress
- Hashnode
- Listmonk (email)
Prefer to plan DEV.to posts yourself? See the DEV.to scheduler.