A
licenseA
qualityD
maintenanceMCP server that enables AI assistants to automatically write and publish blog posts to CSDN with support for categories, tags, and drafts.
4
2
MIT
blog-generator-mcp
by jiwon11
Related Servers
Alternatives to blog-generator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for managing Ghost blogs from AI coding editors. Create, edit, publish, and sync blog posts directly from tools like Claude Code or Cursor.13 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI-powered content generation in multiple formats using Google Gemini and Tavily real-time research, accessible via MCP-compatible clients.1MIT
- AlicenseAqualityBmaintenanceAn MCP server that generates high-quality blog cover images using Google Gemini AI and automatically uploads them to Qiniu Cloud storage. It provides automated WebP conversion and compression to deliver optimized CDN URLs for generated images.35 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Alog, an AI × Human blog platform. Enables AI agents to post logs, create and publish articles, search content, and interact socially on alog.world.1916 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides access to Google Gemini models via Vertex AI, enabling text generation, multi-turn chat, image/video generation, and frontend design through Claude Code.21MIT
TDQS
A4.1/5.0
Scored across 10 tools
Disambiguation4/5
Most tools have clearly distinct roles: generation, status tracking, feedback, review, saving, and deployment. The main ambiguity is between standard and 'pro' variants (start_draft vs start_draft_pro, apply_feedback vs apply_feedback_pro), but they are explicitly separated by mode and input requirements.
Naming Consistency4/5
All tools share the 'blog_' prefix and mostly follow a verb_noun pattern (start_draft, apply_feedback, get_status). Minor deviations like blog_save and blog_deploy_github omit the object or use a platform target, but the pattern remains predictable.
Tool Count5/5
With 10 tools, the server is well-scoped for its purpose. Each tool maps to a distinct stage in the blog lifecycle, and the count is appropriate for a specialized generator.
Completeness5/5
The tool surface covers the full workflow: create draft, check status, apply feedback, finalize, review, apply review feedback, save locally, and deploy to GitHub. No critical operations are missing for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues