Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Latest commit

 

History

135 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Scrybe

Scrybe

MCP-native cross-platform Markdown editor. The document is the conversation: the desktop app, the CLI, and AI agents all drive the same live document through one tool contract.

Install

brew install --cask hartsock/scrybe/scrybe    # macOS app + matching CLI
npm install -g scrybe-ai                      # CLI via npm
pip install scrybe.ai                         # Python toolkit
cargo install scrybe-cli scrybe-mcp-server    # from source via crates.io

First Homebrew install (Homebrew 6+): a cask from a third-party tap must be trusted once. If you hit "Refusing to load cask from untrusted tap", run brew trust hartsock/scrybe (or the exact command Homebrew prints) and re-run the install.

Windows: choco install scrybe (package staged each release; community-feed publication pending — see #2). All installers are on GitHub Releases: dmg · setup.exe/msi · AppImage · deb · rpm.

For a direct macOS DMG install, drag Scrybe into Applications, open it, then choose Scrybe → Install or Repair 'scrybe' Command…. The operation is idempotent and conflict-safe: it repairs broken Scrybe links but never overwrites an unrelated file. Remove 'scrybe' Command… removes only the managed link.

All packages version in lock-step: one release, one version. The brew tap and choco feed are catching up to automation — they may lag a release until #1 / #2 land their publish secrets.

Quick start

scrybe file.md          # open a file in the GUI
scrybe ./               # open a directory
scrybe --help           # everything the CLI can do

# Connect to Claude Code as an MCP server
claude mcp add scrybe -- scrybe-mcp-server stdio

Every document and editor control has an agent equivalent and vice versa. Host installation controls are intentionally local-only: changing PATH is machine administration, not document editing. The full MCP tool surface — names, schemas, semantics — is frozen per release in docs/mcp-contract-0.6.json; the CLI↔GUI socket contract lives in docs/rpc-contract-0.6.md. Agent workflow guide: AGENTS.md.

Development

git clone https://github.com/hartsock/scrybe && cd scrybe
just check              # full lint + test suite
just dev                # Tauri dev server
just install            # app + toolkit + ~/.local/bin/scrybe
just repair-install     # safely re-run the idempotent installer
just uninstall          # remove development-install artifacts only

Architecture, crate map, and conventions: CLAUDE.md. Direction: ROADMAP.md — GitHub issues are the ground truth.

License

Apache-2.0. Use it, build on it, ship it. Your documents stay plain text and belong to you.

The desktop app bundles statically link a few MPL-2.0 crates from its GUI stack; the required notices ship with the app and live in THIRD-PARTY-LICENSES.md + LICENSE-MPL-2.0. The Python wheels and crates.io packages contain no MPL code.

About

MCP-native cross-platform Markdown editor

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages