Integration

DropInBlog Publishing integration

Publishes to a DropInBlog blog: create a post (draft, or live when published_at is set) and update an existing post by id or slug, including SEO title and description, keywords, featured image, categories and author. Reading posts, categories and authors uses a public key and lives in the separate DropInBlog integration; account registration is not exposed. Authentication is a private API key (created at app.dropinblog.com/me/apikeys) sent as a Bearer token, plus your blog ID.

Connect DropInBlog Publishing How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DropInBlog Publishing.Built from the 3 DropInBlog Publishing tools below, on the connection you add once.

What you can do with DropInBlog Publishing

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

create_postCreate postPOSTCreates a blog post from a title and HTML content. With published_at the post goes live on your blog for real; without it, it is saved as a draft. Returns the new post with its id.
update_postUpdate postPATCHUpdates a blog post by numeric id: only the fields you send change, so leave out a field to keep it. Setting published_at publishes the post on your blog. Changing slug changes its URL.
update_post_by_slugUpdate post by slugPATCHUpdates a blog post found by its current slug: only the fields you send change, so leave out a field to keep it. Setting published_at publishes it. Send slug to rename the post, which changes its URL.

Use DropInBlog Publishing from Claude Code, Cursor or Codex

Connect DropInBlog Publishing in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DropInBlog Publishing operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect DropInBlog Publishing

Create your workspace
Sign up free. Nothing to install.
Connect DropInBlog Publishing once
Add your DropInBlog Publishing connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.