bodark-host
v0.1.6
Published
Host-side MCP server for the Bodark PPT plugin — memory, logo fetching, and Mermaid rendering that live outside Cowork's ephemeral VM.
Readme
bodark-host
Host-side MCP server for the Bodark PPT Claude plugin. Provides durable memory, logo fetching, and Mermaid rendering that can't exist inside Cowork's ephemeral VM.
Install
npm i -g bodark-host
bodark-host setupsetup walks you through:
- Detecting Claude Code CLI and Claude Desktop
- Installing Chromium (~170 MB one-time download)
- Prompting for logointern.com credentials (stored in the OS keyring)
- Registering the MCP in
~/.claude.jsonandclaude_desktop_config.json - Initializing
~/.bodark/for memory + logo cache
Commands
| Command | Purpose |
|---|---|
| bodark-host setup | First-time install. Idempotent. |
| bodark-host stdio | Starts the MCP server on stdio (Claude calls this — you shouldn't). |
| bodark-host login | Re-authenticate to logointern.com. |
| bodark-host status | Diagnose install + credentials. |
| bodark-host --help | Full help. |
MCP tools exposed
| Tool | Purpose |
|---|---|
| read_memory(category) | Read Bodark memory (user-preferences / feedback-corrections / common-companies). |
| append_memory(category, entry) | Append a timestamped entry to a memory file. |
| fetch_logos(companies) | Fetch one or more company logos (cache-first, Playwright for misses). Returns inline base64. |
| render_mermaid(source, opts?) | Render a Mermaid diagram to PNG. Returns inline base64. |
| login_logointern(email, password) | Store logointern credentials in the keyring. Prefer the bodark-host login CLI for interactive entry. |
| status() | Diagnostic snapshot (version, paths, credentials, Chromium, cache sizes). |
Data locations
- Memory:
~/.bodark/memory/*.md(append-only markdown) - Logo cache:
~/.bodark/logos/*.png - Credentials: OS keyring (
bodark-logointernservice); fallback~/.bodark/.credentials.jsonchmod 600
Linux / libsecret
On Linux, the keyring backend (keytar) needs libsecret:
sudo apt-get install libsecret-1-devOn headless systems without a running Secret Service, bodark-host automatically falls back to a chmod-600 JSON file. bodark-host status tells you which backend is active.
Uninstall
npm uninstall -g bodark-host
rm -rf ~/.bodark
# macOS only:
security delete-generic-password -s bodark-logointern
# Then remove the bodark-host entry from:
# ~/.claude.json
# claude_desktop_config.jsonLicense
MIT
