home / mcp / mcp blogger posting server
Automates posting to Google Blogger using MCP Tools with secure config and batch posting support.
Configuration
View docs{
"mcpServers": {
"beanspapa-mcp-blogspot-posting": {
"command": "npx",
"args": [
"-y",
"server-blogspot-posting"
],
"env": {
"BLOG_ID": "your-blog-id",
"GOOGLE_CLIENT_SECRET_PATH": "YOUR_PATH_TO_CLIENT_SECRET_JSON"
}
}
}
}You can automate posting to Google Blogger by running a focused MCP server that exposes blogger posting capabilities as MCP tools. This server blends the Google Blogger API with the MCP Tool protocol to enable both single and batch blog posts, while emphasizing secure configuration and easy client integration.
You use an MCP client to interact with the blog posting server. Look up the available tools, such as blog-post for a single post and blog-batch-post for multiple posts. Provide the required fields like title and content, and let the MCP client handle authentication and token management. If authentication is missing or expired, you will be prompted to authenticate before posting.
# Prerequisites
- Node.js is installed on your system
- Git is installed (optional but recommended)
# 1) Install dependencies and build
npm install
npm run build
# 2) Run the server in development mode
npm run devKey operational notes to help you run and manage the server efficiently.
Environment variables you typically configure include the Google OAuth2 client secret path and your target blog ID. These should be provided to the server as environment variables or via a secure client secret file path.
MCP client configuration example shows how to run the server as a local stdio process that the MCP ecosystem can start and talk to. The example uses npx to launch the server with explicit secret path and blog identifier.
{
"mcpServers": {
"blogspot_posting": {
"command": "npx",
"args": ["-y", "server-blogspot-posting"],
"env": {
"GOOGLE_CLIENT_SECRET_PATH": "/path/to/client_secret_xxx.json",
"BLOG_ID": "your-blog-id"
}
}
}
}Place sensitive files like client_secret JSON and environment files under your chosen secure path and ensure they are not committed to version control. Use a dedicated .env mechanism or secret manager for production deployments.
Keep a clean cache for blog IDs in the project root to avoid mismatches between blog URLs and IDs. The cache file should be ignored by version control and cannot be relied upon if moved to a different run directory.
Writes a single post to Google Blogger with title, HTML content, optional labels, and draft flag.
Writes multiple posts in a single operation to Google Blogger, each with its own title, content, labels, and draft flag.