convez.ai
MCP ServerAutomaçãoIntermediário
abstractwebunit

Markdown Publish — Publicador de Vault para GitHub Pages com MCP

abstractwebunit/markdown-publish-plugin

Publique seu vault Obsidian no GitHub Pages e acesse via MCP

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin que publica seu vault Obsidian/Markdown como site no GitHub Pages via skill `/publish-vault` e expõe os conteúdos através de MCP server para leitura por IA. Inclui busca, backlinks e grafo de conhecimento sem custo nem backend externo.

Instalação

$npx convez-ai abstractwebunit/markdown-publish-plugin

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Publicar base de conhecimento pessoal como site estático
  • Consultar notas via Claude/Cursor usando ferramentas de busca e backlinks
  • Compartilhar vault como site público sem infraestrutura

Veredito

Solução pronta e bem integrada para quem quer publicar vault Obsidian como site com busca IA nativa. Requer GitHub CLI e conta GitHub, mas zero custo de hospedagem e fluxo automatizado.

README

A tradução para o português deste README ainda está na fila.

markdown-publish — Claude Code plugin

Publish your Obsidian / Markdown vault as a website in one chat — then read it back through AI.

Engine License: MIT Docs

This plugin bundles two things that work together:

What it does
🚀 /publish-vault skillTell Claude "publish my vault" and it ships your notes to GitHub Pages — in your own account, for free.
🔌 MCP serverPoint any MCP client (Claude Desktop, Cursor, Claude Code) at your published site so the AI can search_notes, get_note, list_notes, and get_backlinks.

Both are powered by the markdown-publish static-site engine: an Obsidian vault → a fast, searchable site with backlinks, a knowledge graph, and canvas boards.


Install

From Claude Code:

/plugin marketplace add abstractwebunit/markdown-publish-plugin
/plugin install markdown-publish

That gives you the /publish-vault skill and the markdown-publish MCP server.


1. Publish a vault — the publish-vault skill

You: publish my Obsidian vault at ~/Notes

Claude walks you through it and always shows a plain-language summary before anything is created:

Готов опубликовать твой vault. Вот что получится:

  📁 Заметки из:   /home/me/Notes
  🌐 Адрес сайта:  https://me.github.io/notes/
  📦 Репозиторий:  github.com/me/notes  (публичный, создам новый)
  🏷  Название:     Notes
  🌍 Язык:         ru

Публикуем? (да / изменить / отмена)

Say да and it:

  1. validates the build locally (catches a broken vault early),
  2. creates a new public GitHub repo in your account,
  3. commits your vault + a GitHub Actions workflow,
  4. enables GitHub Pages and waits for the build,
  5. hands you the live URL.

Everything runs under your GitHub login — no backend, no cost, you own it.

Requirements: the gh CLI installed and authenticated (gh auth login).


2. Read your notes from AI — the MCP server

Once your vault is live (or even a local build), connect it to an AI client by setting one environment variable to your site:

MARKDOWN_PUBLISH_SOURCE = https://me.github.io/notes/

It also accepts a local directory (a built site / bundle root) so you can query notes before publishing:

MARKDOWN_PUBLISH_SOURCE = /path/to/built-site

Now the AI has four tools over your vault:

ToolDescription
search_notes(query, limit?)Keyword search → title, slug, url, snippet
get_note(slug)Full markdown of one note + its backlinks
list_notes()Every note (title, slug, url)
get_backlinks(slug)What links to this note

You: what did I write about dopamine in my notes?

Claude: (calls search_notes("dopamine") → get_note(...)) In your note "Habits & Reward" you wrote… [links to your real notes]

Manual MCP config (without the plugin)

The server is a single zero-dependency Node file. Any MCP client config:

{
  "mcpServers": {
    "markdown-publish": {
      "command": "node",
      "args": ["/path/to/markdown-publish-plugin/mcp/server.mjs"],
      "env": { "MARKDOWN_PUBLISH_SOURCE": "https://me.github.io/notes/" }
    }
  }
}

You can also pass the source as a flag: node mcp/server.mjs --source <url|dir>.


How it fits together

   ~/Notes  ──/publish-vault──▶  github.com/you/notes  ──Actions──▶  GitHub Pages
   (vault)        (skill)            (your repo)         (engine)      (live site)
                                                                          │
                                                            content/*.json bundle
                                                                          │
                                          MARKDOWN_PUBLISH_SOURCE ──▶  MCP server
                                                                          │
                                              Claude Desktop / Cursor / Claude Code

The published site emits a machine-readable content/ bundle (search-index.json, notes/<slug>.json, graph.json). The MCP server reads exactly those files — over HTTP for a published site, or from disk for a local build.


Links

License

MIT. Not affiliated with Obsidian.MD.

Ver o original no GitHub

Bom para

Relacionados