BlogCaster MCP
Wire your coding agent into BlogCaster workflows so you can publish and manage blog or cast-style content without leaving Claude Code or Cursor.
Overview
BlogCaster MCP is a MCP server for the Grow phase that links AI agents to BlogCaster project operations over stdio or streamable-http.
What is this MCP server?
- Registers as BlogCaster MCP with npm stdio transport and a hosted streamable-http remote endpoint
- Version 1.0.1 package identifier blogcaster-mcp for local agent installs
- Dual deployment: Workers.dev remote URL plus local stdio for flexible agent setups
- Purpose-built MCP surface for the BlogCaster project rather than a generic REST wrapper skill
- Server version 1.0.1
- One npm stdio package: blogcaster-mcp
- One remote streamable-http endpoint on Workers.dev
What problem does it solve?
Solo builders using BlogCaster still context-switch out of their agent to run publishing or project tasks that should be one MCP call away.
Who is it for?
Indie builders already on BlogCaster who want Claude Code or Cursor to manage content workflows via MCP.
Skip if: Teams that do not use BlogCaster or need a full editorial CMS, SEO suite, or analytics stack from this server alone.
What do I get? / Deliverables
After you register BlogCaster MCP, your agent can invoke BlogCaster-oriented tools through MCP instead of manual dashboard or ad-hoc API scripts.
- MCP-registered BlogCaster tool surface inside your agent
- Choice of local stdio or remote streamable-http transport
Recommended MCP Servers
Journey fit
BlogCaster-oriented MCP servers typically support recurring publishing and audience-facing output, which maps to the grow phase where solo builders compound reach through content. Content is the canonical shelf for MCP bridges that help create, schedule, or distribute written or episodic material tied to a blog product.
How it compares
MCP integration for BlogCaster, not a standalone blogging skill or WordPress plugin.
Common Questions / FAQ
Who is BlogCaster MCP for?
Solo and indie builders who run on BlogCaster and want their AI coding agent to call BlogCaster workflows through the Model Context Protocol.
When should I use BlogCaster MCP?
Use it during Grow when you are publishing or maintaining blog or cast-style content and want agent-driven actions against BlogCaster without leaving your IDE.
How do I add BlogCaster MCP to my agent?
Add the npm package blogcaster-mcp with stdio transport in your MCP config, or point a compatible client at the streamable-http remote URL from the server manifest.