# honeybook-mcp [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/chrischall/honeybook-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 2514  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/honeybook-mcp

## Description
HoneyBook client-portal MCP server for Claude — view contracts and invoices from wedding vendors

## Tools
Capabilities this server exposes over MCP:

- **use_magic_link** — Capture a session from a magic-link URL
- **list_active_sessions** — Show active credentials, split by kind
- **use_flow_link** — Capture a questionnaire (flow) credential
- **get_flow** — Read one questionnaire and its answers
- **list_workspace_files** — Files from one vendor; filter by type
- **get_workspace_file** — Full detail for one file
- **get_workspace** — Workspace detail + status flags
- **list_payment_methods** — Saved payment methods (brand, last 4, expiry)
- **sign_contract** — Deep link to sign in portal (after you confirm)
- **pay_invoice** — Deep link to pay in portal (after you confirm)
- **list_projects** — Your projects with a vendor + their workspace ids
- **get_project** — Project details: date, location, people, custom fields
- **list_messages** — Messages (or the activity log) in a workspace, newest first
- **get_message** — One message in full: body, attachments, delivery status
- **send_message** — Send or reply through the portal (after you confirm)
- **mark_messages_seen** — Mark feed items seen (reads never do this on their own)
- **list_meetings** — Scheduled meetings with join links, latest time wins
- **list_tasks** — Tasks the vendor assigned you, with counts
- **list_notes** — Notes the vendor shared
- **list_attachments** — Loose images, files and bookmarks in a workspace
- **list_payments** — Payment schedule with paid/unpaid totals

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "honeybook-mcp": {
    "command": "npx",
    "args": ["-y","honeybook-mcp"]
  }
}
```

## Documentation

## What the honeybook-mcp MCP server does

The honeybook-mcp MCP server gives Claude access to the HoneyBook client portals associated with your own vendor relationships. It can inspect project details, workspace status, vendor files, contracts, invoices, payment schedules, saved payment methods, messages, meetings, assigned tasks, shared notes, and workspace attachments.

It also supports a narrower questionnaire workflow. A flow link can be captured separately and read with `get_flow`, including the questionnaire answers. Portal credentials and flow credentials are kept as different session types, so a questionnaire credential is not treated as a full portal login.

Read operations cover most of the client-portal information exposed by the listed tools. Write or consequential actions require confirmation: sending or replying to messages, marking feed items as seen, creating contract-signing links, and creating invoice-payment links. Signing and paying happen through a HoneyBook portal deep link rather than directly inside the MCP process.

## How it works

HoneyBook does not provide a public client-portal API for this use case. Instead, the honeybook-mcp MCP server uses the authentication state created when you open a vendor’s magic link in Chrome. The ContextMint Bridge extension snapshots the relevant session data from the signed-in portal tab; the server does not launch a headless browser or read data from a live browser request.

Call `use_magic_link` while the vendor portal tab is open to activate a portal session. Most tools use the most recently activated session, or you can provide an `origin` when working with multiple vendors. `use_flow_link` captures a separate questionnaire credential, which `get_flow` uses for that specific flow.

Active sessions are stored in memory and persisted under `~/.honeybook-mcp/sessions.json` with restrictive file permissions. Flow credentials are stored separately in `~/.honeybook-mcp/flows.json`. Expired credentials must be captured again from the relevant link.

## Setup and configuration

Install Node.js 22 or later, Claude Desktop or Claude Code, and the ContextMint Bridge extension. The documented browser setup uses Chrome: download the Chrome release archive, load it unpacked through `chrome://extensions`, and enable Developer mode. Safari is not currently available in the documented setup.

From source, clone the repository, run `npm install`, and build with `npm run build`. Configure Claude Desktop to start the generated `dist/bundle.js` file with Node. The repository states that no environment variables are required. Tools that modify or initiate actions use confirmation controls, including a required `confirm: true` for contract signing, invoice payment, and message sending.

Before activation, open each vendor’s magic-link URL in a normal Chrome tab. Then pass that URL to `use_magic_link`. A flow URL is a different link type and must be passed to `use_flow_link` instead.

## Tools and capabilities

- Capture and inspect active portal or questionnaire sessions.
- List projects, workspace files, attachments, notes, tasks, meetings, and messages.
- Read project fields, workspace status, file details, message bodies, delivery information, and questionnaire answers.
- Review payment methods and paid or unpaid payment totals.
- Generate confirmed deep links for signing contracts or paying invoices.
- Send or reply to portal messages after confirmation.
- Mark message-feed items as seen.

## Limitations and notes

The honeybook-mcp MCP server is intended for personal use with your own HoneyBook workspace. The repository is unofficial, is not affiliated with HoneyBook, and warns that its implementation has not received a human audit. Review the source and tool permissions before using it with an account.

The server calls internal HoneyBook endpoints, which may change without notice. HoneyBook’s terms may restrict automated data gathering, scraping, copying, or related uses, and the repository places responsibility for possible rate limits, account warnings, suspension, blocking, or other enforcement on the user. Do not use it for another business, bulk extraction, or a derivative SaaS product. These notes are not legal advice; HoneyBook’s current terms control.

Each new questionnaire may require a separate extension-scope approval because its flow identifier appears in the browser storage key. That approval behavior is expected by the documented extension setup.

_Full upstream README: https://allmcps.com/mcp/honeybook-mcp/readme_