What It Does — A Complete Publishing Agent
BlogCast MCP is an open-source Model Context Protocol (MCP) server that automates the tedious multi-platform publishing workflow. It connects Claude to your Notion workspace, where you write your posts, and then handles the entire deployment process to Dev.to, Hashnode, and Medium.
The core value is automation of the grunt work:
- Image URL Handling: It automatically downloads images from Notion's expiring CDN links, caches them locally, and re-uploads them to each platform's own CDN.
- Platform-Specific Formatting: Converts your content to optimized Markdown for Dev.to/Hashnode and clean HTML for Medium.
- Analytics Sync: Pulls view counts, reactions, and comments from the platforms back into a linked Notion database.
- Scheduling & AI Checks: You can schedule posts via natural language ("schedule this for Friday 9am") and run pre-publish AI checks for missing excerpts or vague titles.
The entire system runs locally. Your API keys are stored encrypted on your machine, and no data is sent to a third-party server.
Setup — How to Install and Configure with Claude Code
Getting started requires cloning the repo and running a setup script. The project is a monorepo with three packages: the MCP server, an Express backend, and a React dashboard.
- Clone and install:
git clone https://github.com/TheCodeDaniel/blogcast_mcp.git cd blogcast_mcp npm run setup # Installs dependencies for all packages - Configure Environment: Copy the
.env.exampleto.envand fill in your API keys for Notion, Dev.to, Hashnode, and Medium. - Run the Services: Start the backend and frontend:
npm run dev:server npm run dev:client - Integrate with Claude Desktop: The project includes an auto-configuration script. Run
npm run configure-claudein themcp/directory. This automatically adds the BlogCast MCP server to your Claude Desktop configuration file (claude_desktop_config.json), so you don't have to edit JSON manually.
When To Use It — Your New Publishing Workflow
Once configured, your interaction moves from forms and buttons to conversation with Claude in Claude Code.
- To publish:
"Publish my latest draft on React state management to Dev.to and Hashnode." - To manage:
"Show me all drafts that are in review."or"What's the view count on my TypeScript post?" - To schedule:
"Schedule the 'CLAUDE.md best practices' post for tomorrow at 9 AM UTC."
The MCP server exposes tools like list_drafts, preview_post, publish_post, and sync_analytics. Claude Code uses these tools to execute your commands. This transforms Claude from a coding assistant into a full-stack publishing agent, handling the entire workflow from your Notion draft to live post across the web.
This follows a clear trend of MCP servers expanding Claude Code's capabilities beyond pure software development, turning it into a central hub for knowledge work. As noted in our recent coverage of tools like Airut and Weaviate Agent Skills, the ecosystem is rapidly moving towards giving Claude Code direct, secure access to more of your tools and data.
