Blog Publisher MCP Server

An automated blog publishing service that automatically copies Markdown articles from Obsidian to the blog directory, processes image links, and synchronizes them to GitHub when the user enters a specific command

Note-taking tools Developer tools #Blog Publishing #File Synchronization #Image Processing #Git Pushing .Python

rating : 2 points

downloads : 8.3K

update time : 2025-04-28

Open Site

What is the MCP Blog Upload Service?

This is an automated tool that helps users quickly convert Obsidian notes into blog posts. It can automatically handle file copying, image path conversion, and the GitHub publishing process.

How to use the MCP Blog Upload Service?

Simply enter the command 'blog+article title' in the input box, and the system will automatically complete the entire process from note to blog publishing.

Use Cases

Suitable for content creators who need to frequently convert technical notes into blog posts, especially users of Obsidian and GitHub Pages.

Main Features

One-Click Publishing

Automatically complete the conversion and publishing from notes to blogs through a simple command

Automatic Image Processing

Automatically identify and transfer images in Markdown and update image paths

GitHub Integration

Automatically commit changes and push them to the GitHub repository

Advantages

Simplify the publishing process and save time

Keep image links valid

Seamlessly integrate with the existing Obsidian workflow

Limitations

Currently only supports a specific directory structure

Requires pre-configuring the GitHub repository

Only supports Markdown format files

How to Use

Prepare the Article

Create and save a Markdown article in Obsidian

Trigger Conversion

Enter 'blog+article title' (without the .md suffix) in the input box

Wait for Completion

The system will automatically complete file copying, image processing, and GitHub pushing

Usage Examples

Publish Technical Notes

Quickly publish daily Android development notes as blog posts

Update an Existing Article

Republish the article after modifying it in Obsidian

Frequently Asked Questions

Why are my images not displayed correctly?

How to change the default output directory?

What should I do if the GitHub push fails?

Related Resources

Obsidian Official Website

Markdown note-taking tool

GitHub Pages Documentation

How to build a blog using GitHub Pages

Markdown Syntax Guide

Markdown format reference

🚀 MCP Blog Upload Service

This project aims to create an MCP (Model Context Protocol) blog upload service. When users input "blog+article name", the system will automatically copy the specified Markdown file from the local Obsidian directory to the designated target directory, handle the image links (copying images from the source folder to the target folder), and finally push all changes to GitHub.

🚀 Quick Start

When you input "blog+article name", the system will initiate the entire process.

✨ Features

Trigger Condition: The service is triggered when the user inputs "blog+article name".
File Copying: A Markdown file (.md, e.g., "article name.md") from the local Obsidian directory will be copied to the specified sub - directory under I:\B-MioBlogSites (default is I:\B-MioBlogSites\_Android).
Image Handling: All image links in the Markdown file will be detected and extracted. These images will be copied from the source folder I:\B-1 笔记\Android\Android\z. attachments to the target folder I:\B-MioBlogSites\assets\images, and the image paths in the Markdown file will be updated accordingly.
GitHub Push: All changes (including the modified Markdown file and newly copied images) will be committed to the local Git repository and pushed to the remote GitHub repository.

📚 Documentation

Overall Process

Input: The user inputs "blog+article name".
File Copy: The system locates the corresponding Markdown file in the Obsidian local directory and copies it to the target path.
Image Processing: Scan the Markdown file, extract all image links, copy the images from the source folder to the target folder, and update the image paths in the Markdown file.
GitHub Push: Commit all changes to the local Git repository and push them to the remote GitHub repository.

Directory Structure

Source Markdown File Directory: The local Obsidian directory where the Markdown files are stored.
Target Markdown File Directory: I:\B-MioBlogSites\_Android (default).
Source Image Directory: I:\B-1 笔记\Android\Android\z. attachments.
Target Image Directory: I:\B-MioBlogSites\assets\images.

Notes

Ensure that the local Git repository is properly configured and has the permission to push to the remote GitHub repository.
Make sure that the source Markdown file and image files exist in the specified directories.