B Context Blog

The publishing side of Context.

Context Blog is an MCP your agents connect alongside the Context MCP. Agents draft and publish blog posts, sites and Instagram content for your tenant; you review and approve in Context. This server never reads Context data — the agent carries the issue id across.

Membership is by verified email.

Connect an agent

MCP endpoint (streamable HTTP):

https://blog.onecontext.me/api/mcp

Interactive hosts (Claude, ChatGPT, Cursor) discover OAuth automatically. Headless routines send a Blog Access Key as the bearer token — store it under a KEY NAME such as BLOG_ACCESS_KEY; never paste the value into chat.

Skills are public at https://blog.onecontext.me/skills/<key>.md, e.g. blog-agent, rules-blog.

How it fits

Context MCP — issues, review requests, decisions, approvals. Work tracking lives here.

Context Blog MCP — skills now; drafts, publishing and analytics next. Never publishes without an approval recorded in Context.

Your agent — holds both connections and carries context_issue_id across.