Blogger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLOGGER_API_KEY | No | Google Blogger API key for read-only access | |
| DEFAULT_BLOG_ID | No | Default Blog ID, used when blogId is omitted from tool calls | |
| GOOGLE_CLIENT_ID | No | OAuth 2.0 Client ID for write operations | |
| GOOGLE_CLIENT_SECRET | No | OAuth 2.0 Client Secret for write operations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_blogsA | List all blogs for the authenticated user (OAuth required) |
| get_blog_infoB | Get information about a blog by URL or ID |
| list_postsC | List posts from a blog |
| list_draftsB | List draft posts from a blog |
| get_postC | Get a specific post by ID |
| search_postsC | Search for posts in a blog |
| create_postC | Create a new blog post |
| update_postC | Update an existing blog post |
| change_post_statusB | Publish a draft post or revert a published post to draft |
| delete_postC | Delete a blog post |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: list_blogs vs. get_blog_info, list_posts vs. search_posts vs. list_drafts, and create/update/delete/change_status for posts. No ambiguity exists between tools.
All tools follow a consistent verb_noun pattern with snake_case (e.g., create_post, list_blogs, update_post). The naming is predictable and uniform across all 10 tools.
With 10 tools, the server is well-scoped for a blogging platform, covering blog management, post CRUD operations, and listing/searching functions. Each tool earns its place without bloat.
The tool set provides complete CRUD/lifecycle coverage for the blogging domain: create, get, update, delete, and status change for posts, plus blog listing/info and post listing/searching. No obvious gaps exist for core workflows.