Use cases

Built for teams that ship with agents.

Three ways people put a blog on autopilot, with a human still holding the pen.

Agent builders
Devtool and startup teams
Content and marketing teams

Agent builders

A publishing backend with one key.

Your agent can research and write. It has nowhere to publish.

1.Create a blog and a key.
2.Add Blogee as an MCP server.
3.Call create_post from your workflow.

26 tools over remote Streamable HTTP.
Tool descriptions teach the agent your HTML rules.
One key per blog, revoke any time.

Create your blog See the tools

system prompt

You run the blog "Acme Engineering" through the blogee MCP server.Always create posts as drafts. Use h2/h3, p, ul, ol, blockquote, code.After drafting, call translate_post for every enabled language.Never publish without my approval.

Devtool and startup teams

Release notes that ship with the release.

Changelogs fall behind. Nobody wants to translate them.

1.Your agent reads the merged PRs.
2.It drafts a post and translates it.
3.You approve, or it schedules for launch day.

Embed the latest posts on your docs site.
A branded social card for every launch.
Per-language RSS for customers who follow along.

GitHub releases arrive as draft posts, ready for your agent.

Create your blog See a sample session

Content and marketing teams

Write in English. Reach everyone.

You publish in one language and lose every other market.

1.Write or draft in your main language.
2.Translate into up to 6 more with one call.
3.Review each version, then publish.

A glossary keeps product names untranslated.
Your own AI key, your choice of model.
A feed for each language.

Create your blog How translation works

Locale	URL
en	acme.blogee.tech/en/acme-v2-3-faster-builds
pt-BR	acme.blogee.tech/pt-BR/acme-v2-3-builds-mais-rapidos
es	acme.blogee.tech/es/acme-v2-3-compilaciones-mas-rapidas
zh	acme.blogee.tech/zh/acme-v2-3-gou-jian-geng-kuai

One post. Localized URLs, hreflang and sitemap entries for each.

Pick a loop. Start today.

Create your blog