Integration

DropInBlog integration

DropInBlog is an embeddable SEO blog platform. Read a blog's posts (list, search, by id or slug), categories and authors as JSON, or fetch pages, the sitemap and RSS/Atom feeds already rendered with the blog layout for embedding in a site. Creating and updating posts needs a private key and lives in the separate DropInBlog Publishing integration; the account-registration route is not exposed. Authentication is a public API key (created at app.dropinblog.com/me/apikeys) sent as a Bearer token, plus your blog ID.

Connect DropInBlog How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with DropInBlog

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.

Post, 4 operations

get_postGet postGETReturns one blog post by its numeric id, including its HTML content, SEO fields, author and categories.
get_post_by_slugGet post by slugGETReturns one blog post by its URL slug, including its HTML content, SEO fields, author and categories.
list_postsList postsGETLists blog posts, one page at a time, with title, slug, URL, summary, SEO fields, author and categories. By default only published public posts; filter by status, visibility, category, author, ids, slugs or dates.
search_postsSearch postsGETSearches blog posts by text (search, required), optionally by status, with pagination. Returns the same post fields as list_posts.

Rendered page, 4 operations

get_rendered_author_listGet rendered author listGETReturns the post list page of one author (by slug) fully rendered as head_html and body_html, ready to embed. Paginated.
get_rendered_category_listGet rendered category listGETReturns the post list page of one category (by slug) fully rendered as head_html and body_html, ready to embed. Paginated.
get_rendered_postGet rendered postGETReturns one post page (by slug) fully rendered with your DropInBlog layout as head_html and body_html, ready to embed.
get_rendered_post_listGet rendered post listGETReturns the main blog list page fully rendered with your DropInBlog layout: head_html (title, meta, CSS) and body_html, ready to embed in a page. Paginated.

Author, 3 operations

get_authorGet authorGETReturns one blog author by its numeric id.
get_author_by_slugGet author by slugGETReturns one blog author by its URL slug.
list_authorsList authorsGETLists the blog authors with id, name, slug, photo and bio. Use an id as author_id when publishing.

Category, 3 operations

get_categoryGet categoryGETReturns one blog category by its numeric id.
get_category_by_slugGet category by slugGETReturns one blog category by its URL slug.
list_categoriesList categoriesGETLists the blog categories with id, title, slug and SEO fields. Use an id in category_ids of list_posts or of the publishing tools.

Feed, 3 operations

get_rendered_author_feedGet rendered author feedGETReturns the feed of one author (RSS or Atom) as an XML string inside the JSON answer.
get_rendered_category_feedGet rendered category feedGETReturns the feed of one category (RSS or Atom) as an XML string inside the JSON answer.
get_rendered_feedGet rendered feedGETReturns the main blog feed (RSS by default, or Atom with type=atom) as an XML string inside the JSON answer, with its content type.

Sitemap, 1 operation

get_rendered_sitemapGet rendered sitemapGETReturns the blog sitemap XML as a string inside the JSON answer, with its content type.

Use DropInBlog from Claude Code, Cursor or Codex

Connect DropInBlog in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DropInBlog 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

Create your workspace
Sign up free. Nothing to install.
Connect DropInBlog once
Add your DropInBlog 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.