Homgorn MCP Stack

Локальный open-source Model Context Protocol (MCP) stack для Kwork, WordPress, WooCommerce, GitHub, filesystem-инвентаризации, snapshots, evidence и read-only automation.

Репозиторий собран как рабочая база для:

• индексации правил, страниц и структур;
• read-only мониторинга Kwork и конкурентов;
• подготовки кворков, FAQ, портфолио и SEO-контента;
• дальнейшего подключения Playwright browser-automation, scheduled monitoring и explicit write workflows;
• локального хранения wiki, research, runbooks и экспортов в Markdown, JSON и CSV.

Что уже есть

• typed config and manifest layer
• stdio MCP transport
• stateful Streamable HTTP MCP transport
• filesystem adapter for read-only root inspection
• WordPress adapter pack for read-only site inventory
• WooCommerce adapter pack for read-only store inventory
• GitHub adapter pack for read-only repository inventory
• safety layer with read-only defaults and confirmation gates
• evidence layer for URL, DOM, screenshot, and selector records
• snapshots layer for competitor, portfolio, and price snapshots
• exporters for Markdown, JSON, CSV, and WordPress import bundles
• style layer for human-readable response guidance
• Telegram notifier preview layer
• durable wiki and file index
• tests for core, server, HTTP, filesystem, WordPress, WooCommerce, GitHub, safety, evidence, snapshots, exporters, style, and telegram

Почему это не просто "ещё один MCP сервер"

Этот репозиторий держит отдельно:

• core - типы, manifest и policy primitives
• server - MCP runtime и transports
• adapters - доменные read-only пакеты
• docs - архитектура и roadmap
• wiki - живая проектная память и индексы

Такой слой легче расширять без спагетти-кода. WordPress и WooCommerce логично жить как отдельный сайт-пакет, GitHub - как read-only inventory pack, evidence/snapshots/exporters работают как исследовательский контур, а Telegram - как уведомления и handoff-канал.

Current packs

• filesystem for local root inspection
• wordpress for site inventory and REST index discovery
• woocommerce for store inventory and public API discovery
• github for repository inventory and API normalization
• safety for read-only defaults and write gates
• evidence for URL, DOM, screenshot, and selector records
• snapshots for competitor, portfolio, and price captures
• exporters for Markdown, JSON, CSV, and WordPress import bundles
• style for human response guidance
• telegram for notification planning and previewing

Быстрый старт

npm install
npm test
npm run typecheck
npm run dev:stdio
npm run dev:http

Конфиг

Смотри config/example.platform.json. Это шаблон для локальной машины, без cookies, паролей и session storage.

Wiki

• wiki/INDEX.md - центральный индекс
• wiki/ROADMAP.md - короткая дорожная карта
• wiki/TODO.md - ближайшие задачи
• wiki/PROJECT_MEMORY.md - принятые решения
• wiki/RESEARCH.md - research log
• wiki/FILE_INDEX.md - карта файлов

Documentation

• docs/architecture.md
• docs/roadmap.md
• docs/superpowers/plans/2026-06-21-mcp-platform-baseline.md

Safety

• Read-only first.
• No secret collection.
• No writes to external services without explicit confirmation.
• Keep local evidence, indexes and exports current so the stack can be resumed without context loss.

English

Homgorn MCP Stack is a local-first open-source Model Context Protocol (MCP) platform for Kwork support, WordPress and WooCommerce workflows, GitHub inventory, filesystem inspection, and read-only automation.

It is designed as a small core with adapter packs around it:

• core for config and manifest primitives
• server for MCP transports and runtime wiring
• adapters for read-only integrations
• docs and wiki for durable project memory

Current focus:

• Kwork site and competitor research
• content drafts and portfolio indexing
• SEO-ready exports for WordPress import
• future Playwright browser capture, scheduled monitoring, and explicit write workflows

The default operating mode is safe and read-only. Any action that could change account state should stay gated behind explicit confirmation.