scrybe-mcp-server

Inbound MCP server: exposes Scrybe's editing capabilities as MCP tools that external agents (Claude Code, Codex, custom agents) can call. Python on the outside, Rust on the inside.

What it does

Implements the MCP JSON-RPC 2.0 protocol over stdio. An AI agent connects to this process and gains structured, safe access to open Markdown documents — reading, editing, searching, rendering, and managing the running app — without direct filesystem access.

Role in the architecture

scrybe-mcp-server is the agent-facing surface of Scrybe — a thin stdio shim over the shared scrybe-tools registry, the ONE tool registry (handlers, schemas, dispatch) it shares with the CLI, so the two surfaces match by construction. Stateful tools drive the running app over ~/.scrybe/sock; in-process tools (render, lint, embed, extract, export, mermaid_to_png, export_figures) work headless. Agents connect via:

claude mcp add scrybe -- scrybe-mcp-server stdio

Exposed tools

The authoritative list is scrybe-mcp-server tools (or MCP tools/list): open, read, section, edit, save, find, render, embed, extract, lint, list_tabs, mermaid_to_png, export_figures, export, logs, reload, close_tab, quit, state, set_theme, view_mode, set_vim. See AGENTS.md (repo root) for the full per-tool reference.

Key public types

Build and test

cargo build -p scrybe-mcp-server
cargo test -p scrybe-mcp-server

# Install the binary
cargo install --path .

The binary (scrybe-mcp-server) speaks MCP over stdio. Add it to any MCP client's server list with transport stdio.