LotsBlog for AI Builders — A fully programmable blog operating system

The problem

Why most CMSs don't work for agent workflows.

You've automated everything else in your stack. The content pipeline is still manual.

01

Most CMSs were built for humans clicking buttons.

They work for editors. They break under agents. Rate limits, inconsistent schemas, auth flows designed for browsers — not API calls.

02

You end up wrapping their APIs in brittle integrations.

You write a custom connector. It breaks on the next API change. You spend two hours debugging a publishing bug instead of building.

03

You need content infrastructure that speaks agent natively.

Not a CMS you have to wrap. One that was designed from the start to be driven programmatically.

How LotsBlog works for agents

Every dashboard action is an API call.

LotsBlog is designed to be driven by agents. The MCP server at api.lots.blog/mcp exposes the full content lifecycle. Your agent connects once and controls everything.

01

Connect via MCP or REST

Point to api.lots.blog/mcp. Authenticate with your API key. Done.

02

Create and manage posts

Create drafts, set metadata, schedule publish dates — all via typed API calls.

03

Build structured content

Title, slug, tags, schema, meta description — everything an LLM needs to produce publishable output.

04

React to events via webhooks

Get notified on publish, update, or draft — pipe events directly into your pipeline.

The developer stack

Infrastructure built for programmable content.

Not an afterthought. Designed to be driven by code from the start.

⇄

MCP server

Native MCP at api.lots.blog/mcp. Compatible with Claude, any MCP-capable agent, or your own system.

⎔

Headless CMS + API

Typed REST API. Your content, accessible anywhere. Typed responses, consistent schemas.

◷

Webhooks & events

Subscribe to post lifecycle events. React to drafts, publishes, and updates in real time.

Why build on LotsBlog

Content infrastructure that was designed to be driven by code.

An MCP-native CMS, not a CMS with an API bolted on

Most headless CMSs expose an API as an afterthought to a UI-first product. The schemas drift, the auth assumes a browser session, and anything the API can't do becomes a scraping job. For agent workflows, that surface area is where reliability goes to die.

LotsBlog inverts it. The MCP server at api.lots.blog/mcp exposes the same content lifecycle the dashboard uses — create, draft, interlink, schedule, publish, update — as typed, callable tools. Any MCP-capable agent (Claude, your own LotsAgent, or a custom system) connects once and operates the blog with no UI in the loop.

Typed REST and webhooks for the rest of your stack

Beyond MCP, every action is available over a typed REST API with consistent schemas, so you can drive LotsBlog from CI, internal tools, or a backend service without reverse-engineering responses. Authentication is an API key, not a browser flow.

Webhooks fire on the events that matter — draft created, post published, content updated — so you can pipe blog state into your own pipeline: trigger a social distribution job, sync to a data warehouse, or kick off downstream automation the moment something ships.

Part of an agent-native ecosystem

LotsBlog's own agent runs on LotsAgent under the hood, which is why programmatic control is a first-class path rather than a workaround. The same primitives your agent uses are the ones the product uses.

That makes LotsBlog a clean content layer for larger agent systems: hand long-form publishing to LotsBlog, let it prepare derivatives for LotsSocial, and keep your orchestration logic in your own stack. The blog becomes a programmable service, not a destination your users have to log into.

Questions

For AI builders — answered.

Still unsure? Talk to the agent.

Do you have a native MCP server?

Yes. The MCP server at api.lots.blog/mcp exposes the full content lifecycle as typed tools. Connect Claude, your own LotsAgent, or any MCP-capable agent with an API key and it can create, draft, interlink, schedule, and publish.

Is there a REST API as well?

Yes — a typed REST API with consistent schemas covers every dashboard action, plus webhooks for post lifecycle events. There is no GraphQL endpoint today; the surface is REST + webhooks + MCP.

What can an agent actually do through the API?

Everything the dashboard can: create and manage posts, set metadata and schema, interlink content, schedule and publish, and update existing posts. If you can do it in the UI, it's a call.

How do I react to changes?

Subscribe to webhooks for events like draft created, post published, and content updated. Pipe them straight into your pipeline to trigger distribution, sync data, or run downstream automation.

Which plans include API access?

API access is available on the Pro and Business plans (currently in Beta). The MCP server and REST API share the same authenticated surface.

How does this fit with the rest of the LotsTech ecosystem?

LotsBlog's agent runs on LotsAgent, so programmatic control is first-class. You can hand long-form publishing to LotsBlog, have it prepare derivatives for LotsSocial distribution, and keep orchestration in your own stack.

Your blog. Fully programmable.