convez.ai
MCP ServerIntegração & APIsIntermediário
jedwards1230

My Wiki MCP Server

jedwards1230/my-wiki

Obsidian headless + frontend estático + MCP server em um binário Go

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP em Go que expõe um vault Obsidian como website, API REST e agente de IA. Um único binário renderiza markdown nativamente, servindo conteúdo estático, REST e MCP sobre stdio ou HTTP, com suporte a K8s e deployment via Helm.

Instalação

$npx convez-ai jedwards1230/my-wiki

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á 3 dias
Versão
v0.12.15
Issues abertas
15
Contribuidores
1

Casos de uso

  • Integrar vault Obsidian com agentes Claude via MCP
  • Expor base de conhecimento como API REST e website
  • Manutenção automatizada de vault (lint, validação de links, relatórios)
  • Deployment em Kubernetes com múltiplas instâncias de wiki

Veredito

Solução completa e bem arquitetada para quem quer expor Obsidian como MCP server. Excelente para builders que precisam de agentes acessando conhecimento estruturado; requer familiaridade com Go, Docker e deployment em infraestrutura.

README

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

my-wiki

A single Go binary (wiki-server) that serves an Obsidian vault as a website, a REST API, and an MCP server for AI agents. A native Go renderer turns markdown into HTML; the same binary handles static/REST delivery and MCP. It runs as a long-lived K8s deployment or an on-demand stdio MCP server.

Quickstart

# Docker Compose — serves the rendered vault at http://localhost:8080
WIKI_VAULT=/path/to/obsidian-vault docker compose up --build
# Build from source
go build -o wiki-server ./cmd/wiki-server

# HTTP server (browser + REST). Add `--mcp-port 8081` to also start MCP in-process.
./wiki-server serve --vault /path/to/vault --port 8080

# MCP over HTTP (streamable-http)
./wiki-server serve mcp http --vault /path/to/vault --port 8081

# MCP over stdio (Claude Code / .mcp.json) — no HTTP or auth
./wiki-server serve mcp stdio --vault /path/to/vault

Content paths

PathServes
/pathRendered HTML
/path.mdPlain markdown from the vault
/raw/pathNative source files (PDFs, images) with dir listings
/api/*REST API (pages, search, lint, activity, ...)

CLI

One-shot vault-maintenance commands sharing the --vault flag:

./wiki-server lint      [all|frontmatter|tags|links|orphans|size|clippings|stub|log]
./wiki-server directory                              # list all pages with metadata
./wiki-server log       [today|YYYY-MM-DD|lint]      # view / lint the activity log
./wiki-server activity  <type> <title> [--summary X] # append a structured log entry

A macOS LaunchAgent for daily lint (--instance-name is appended to the plist label so multiple vaults coexist):

./wiki-server --vault /path/to/vault --instance-name work-wiki launchd install
./wiki-server --instance-name work-wiki launchd status
./wiki-server --instance-name work-wiki launchd uninstall

Deployment

Helm chart: oci://ghcr.io/jedwards1230/charts/my-wiki. Images: ghcr.io/jedwards1230/my-wiki. Both released by release.yml on push to main (semver via semver:patch|minor|major PR labels).

Key Helm values (see deploy/helm/my-wiki/values.yaml for the full list): instanceName sets WIKI_INSTANCE_NAME and is surfaced by the whoami MCP tool so agents can distinguish multiple wiki instances. obsidianSync.standalone: true moves obsidian-headless to a separate Deployment (requires an RWX PVC).

Documentation

  • docs/OVERVIEW.md — architecture and design choices
  • docs/SERVER-MODES.md — per-mode feature matrix
  • docs/RENDERER.md — native renderer pipeline and assets
  • CLAUDE.md — agent repo guide (build commands, conventions, env vars)
  • internal/cli/envvars.go — canonical WIKI_* environment variable inventory
Ver o original no GitHub

Bom para

Relacionados