Stylobridge

io.github.blockpal1Published by GitHub account blockpal1v1.0.2Updated Oct 24, 2026

Air-gapped Markdown/PDF to Word converter with brand templates and audit logging.

Overview

AI-generated overview

Converts Markdown or PDF documents into Word files using brand templates, with audit logging, running locally on the user's machine.

What you can do
Stylobridge is a local, air-gapped document converter that turns Markdown or PDF input into Word output. It applies brand templates from a configured template directory so generated documents follow a house style, and it records an audit log of conversions. It runs as a local process over stdio rather than as a remote service.
When to use it
Useful when an assistant needs to produce Word deliverables from Markdown or PDF sources while keeping documents on the local machine, for example applying a corporate template to reports or contracts. It suits workflows where offline operation and a conversion audit trail matter.
Requirements
Runs locally over stdio, launched with uvx from the stylobridge PyPI package or from the ghcr.io container image. Requires a license token in the STYLOBRIDGE_LICENSE environment variable, plus optional TEMPLATE_DIR for brand templates and WORKSPACE_ROOT to bound file access. Desktop only; no web execution.
Before you install
The STYLOBRIDGE_LICENSE variable holds a signed license token and must be treated as a secret. The server writes converted files, so WORKSPACE_ROOT should be set to limit which directories it can read and write. No authentication is declared for the local process.

Installation

In SourceWeft

  1. Open Stylobridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.