Blogger MCP Server

An MCP (Model Context Protocol) server that provides Claude and other MCP-compatible AI assistants with full access to the Google Blogger API v3. Supports reading, creating, updating, publishing, and deleting blog posts through natural language.

Features

• Blog management — List all blogs under your account, get blog metadata

• Post lifecycle — Create drafts, edit, publish, revert to draft, delete

• Read operations — List posts, retrieve individual posts, search by keyword

• Draft-first workflow — Posts are created as drafts by default for safety, then published explicitly

• Dual authentication — API Key for read-only access, OAuth 2.0 for full read/write access

• File-based content — Load post content from local HTML files (recommended for content > 10KB)

• Automatic token management — OAuth tokens are cached, refreshed, and persisted automatically to ~/.config/mcp-blogger/

• Default blog — Set DEFAULT_BLOG_ID to skip passing blogId on every tool call

Project Structure

Prerequisites

• Node.js >= 22

• A Google Cloud project with the Blogger API enabled

• A Blogger API Key (for read operations) and/or OAuth 2.0 credentials (for write operations)

Installation

Authentication

This server supports two authentication methods. At least one must be configured:

• API Key only — read-only operations (get_blog_info, list_posts, get_post, search_posts)

• OAuth only — full read and write operations

• Both — API Key for reads, OAuth for writes

1. Get a Blogger API Key (read-only access)

1. Go to the Google Cloud Console

2. Create a project (or select an existing one)

3. Enable the Blogger API v3 under APIs & Services > Library

4. Go to APIs & Services > Credentials

5. Click Create Credentials > API key

6. Copy the generated API key

2. Get OAuth 2.0 Credentials (read + write access)

1. In the same Google Cloud project, go to APIs & Services > Credentials

2. Click Create Credentials > OAuth client ID

3. Select Web application as the application type

4. Add http://localhost:3000/oauth/callback to Authorized redirect URIs

5. Copy the Client ID and Client Secret

3. OAuth Flow (automatic)

On the first write operation, the server will automatically:

1. Start a temporary local HTTP server on port 3000

2. Open your browser to the Google OAuth consent page

3. After you grant access, capture the authorization code via the callback URL

4. Exchange the code for access and refresh tokens

5. Persist tokens to ~/.config/mcp-blogger/tokens.json

Subsequent write operations reuse cached tokens and refresh them automatically when expired. The OAuth flow times out after 5 minutes if not completed.

Configuration

Set the following environment variables in your MCP client configuration:

MCP Config Example

Add the server to your Agent MCP configuration file (such as mcp_config.json):

Claude Code

Add the server via the Claude Code CLI:

Tools

All tools that accept blogId will fall back to DEFAULT_BLOG_ID if set.

Typical Workflow

Dependencies

• @modelcontextprotocol/sdk — MCP server framework

• googleapis — Google API client (Blogger API v3)

• express — Local HTTP server for OAuth callback

• open — Opens browser for OAuth consent

License

MIT