Log inSubmit server
Honeybook MCP logo

Honeybook MCP

Connects Claude to your HoneyBook client portals for contracts, invoices, messages, payments, meetings, and vendor files.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Honeybook MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "honeybook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeybook-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The honeybook-mcp MCP server connects Claude to HoneyBook client portals through authenticated browser sessions captured from vendor magic links. It exposes read tools for projects, workspaces, contracts, invoices, payments, messages, meetings, tasks, notes, attachments, and questionnaires, plus confirmed actions for messaging, signing, and paying. Use it when you manage vendor work through HoneyBook and want those portal details available in Claude. It relies on the ContextMint Bridge Chrome extension and internal HoneyBook endpoints rather than a public HoneyBook client API.

Use cases

  • Review unsigned vendor contracts
  • Check upcoming invoice due dates
  • Summarize vendor messages and checklists
  • Find meeting join links
  • Send a confirmed reply to a vendor

Key features

  • HoneyBook portal session capture
  • Project and workspace inspection
  • Contract and invoice access
  • Vendor messaging tools
  • Payment and meeting tracking
  • Questionnaire answer retrieval

Tools21

What Honeybook MCP lets your agent do. Expand a tool for its parameters.

Self-reported~301 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · honeybook-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.5kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed21Callable tools this server registers over MCP.

How Honeybook MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Honeybook MCP

honeybook-mcp is an MCP server that connects Claude to your HoneyBook client portals through browser sessions captured from vendor magic links. Its main tools list projects, files, messages, invoices, payments, meetings, tasks, and questionnaires, while confirmed actions can send messages or create links for signing contracts and paying invoices.

Install Node.js 22 or later, clone the repository, run `npm install` and `npm run build`, then configure Claude Desktop or Claude Code to launch `dist/bundle.js` with Node. Chrome and the ContextMint Bridge extension are also required for capturing vendor portal sessions.

Open the vendor’s magic-link URL in a signed-in Chrome tab, then call `use_magic_link` with that URL. The ContextMint Bridge extension captures the session from the portal page. Use `origin` when more than one vendor session is active.

Yes, but questionnaire links use a separate flow credential. Call `use_flow_link` with the flow URL, then use `get_flow` to retrieve that questionnaire and its answers. A flow credential does not provide access to the vendor’s full portal workspace.

Yes. Claude Desktop is a documented requirement, and its configuration starts the built `dist/bundle.js` file with Node. Claude Code is also listed as a supported runtime requirement.

Related MCP servers

All in Legal All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHoneybook MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/honeybook-mcp?style=directory)](https://allmcps.com/mcp/honeybook-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/honeybook-mcp"><img src="https://allmcps.com/api/badge/honeybook-mcp?style=directory" alt="Honeybook MCP on AllMCPs" /></a>