HoneyBook MCP

A Model Context Protocol server that connects Claude to the HoneyBook client portal, giving you natural-language access to contracts and invoices sent by your wedding vendors.

[!WARNING] AI-developed project. This codebase was built and is actively maintained by Claude Code. No human has audited the implementation. Review all code and tool permissions before use.

What you can do

Ask Claude things like:

"Paste your magic link — I'll connect to your HoneyBook portal."
"Show me every unsigned contract."
"What invoices do I have due in the next month?"
"Summarize the contract from Silk Veil Events."
"Give me a deep link to sign the photographer's contract."

Requirements

Claude Desktop or Claude Code
Node.js 20.6 or later
Magic-link emails from the wedding vendors that use HoneyBook
Google Chrome — used by use_magic_link to capture each vendor's session

Installation

From source

git clone https://github.com/chrischall/honeybook-mcp.git
cd honeybook-mcp
npm install
npm run build

Add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "honeybook": {
      "command": "node",
      "args": ["/absolute/path/to/honeybook-mcp/dist/bundle.js"]
    }
  }
}

No environment variables are required.

Sessions

HoneyBook has no public client-portal API. This MCP reuses the same auth state your browser has after clicking a vendor's magic link.

Workflow:

Open a vendor's HoneyBook email and copy the magic-link URL.
In Claude, call use_magic_link with that URL. A headless Chrome window opens, follows the link, and captures the session automatically.
All other tools use the most-recently-activated session by default. Pass origin explicitly when multiple vendors are active.

Sessions are stored in memory and persisted to ~/.honeybook-mcp/sessions.json (mode 0600) so they survive MCP restarts. Re-run use_magic_link when a session expires.

Available tools

Tools that touch a vendor accept an optional origin argument (e.g. https://acme.hbportal.co). When only one session is active it is inferred.

Tool	What it does	Permission
`use_magic_link`	Capture a session from a magic-link URL	Confirm
`list_active_sessions`	Show currently active portal sessions	Auto
`list_workspace_files`	Files from one vendor; filter by type	Auto
`get_workspace_file`	Full detail for one file	Auto
`get_workspace`	Workspace detail + status flags	Auto
`list_payment_methods`	Saved payment methods	Auto
`sign_contract`	Deep link to sign in portal (requires `confirm:true`)	Confirm
`pay_invoice`	Deep link to pay in portal (requires `confirm:true`)	Confirm

Troubleshooting

"HoneyBook auth expired" — re-run use_magic_link with a fresh magic-link URL from the vendor's email.
"No active HoneyBook session" — call use_magic_link first.
"Google Chrome not found" — set PUPPETEER_EXECUTABLE_PATH to your Chrome binary, or install Chrome at the default path.

Security

Sessions are captured locally — auth tokens never leave your machine
~/.honeybook-mcp/sessions.json is written with mode 0600; directory with mode 0700
Write tools (sign_contract, pay_invoice) require confirm:true and return portal deep links rather than signing/paying headlessly

Development

npm test        # run tests
npm run build   # tsc + esbuild bundle

License

MIT

honeybook-mcp

Quick Install