Skip to main content
Glama
chrischall

honeybook-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

use_magic_link

Capture your HoneyBook client-portal session from an open, signed-in browser tab using the fetchproxy extension, storing credentials for other tools to use.

Instructions

Capture a HoneyBook client-portal session via the fetchproxy 0.3.0 browser extension. Prerequisites: install the fetchproxy extension in Chrome/Safari, then open the vendor's magic-link URL in that browser so you're signed into their portal and leave that tab open. This tool then snapshots the auth fields out of the page's localStorage["HONEYBOOK_REACT_CURR_USER"] into ~/.honeybook-mcp/sessions.json. The tab only needs to be open and signed in — nothing is sniffed off a live request, so it does not matter whether the page is idle. All other tools use the most-recently-activated session by default. The magic_link_url arg is used only to derive the portalOrigin (cache key) — the tool does NOT open or navigate to it. For a QUESTIONNAIRE link (https://.hbportal.co/flow/?hash=…) use use_flow_link instead — that link writes a different, flow-scoped credential and this tool refuses it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
magic_link_urlYesFull magic-link URL from the vendor's HoneyBook email, e.g. https://<vendor>.hbportal.co/app/workspace_file/<id>/... Used only to derive the portal origin; you must already have this URL open in a Chrome tab with the fetchproxy extension installed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.3.1

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description reveals key behaviors: it reads localStorage['HONEYBOOK_REACT_CURR_USER'], writes to ~/.honeybook-mcp/sessions.json, does not sniff live requests, derives only the portalOrigin from the argument, and refuses questionnaire links. This is rich, non-obvious behavior that an agent must know before calling the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average, but every sentence carries useful operational information: prerequisites, mechanics, parameter semantics, behavior, and sibling routing. It is front-loaded with the core purpose and remains dense rather than redundant, though it could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one parameter, notable prerequisites, side effects, and no output schema, the description covers everything needed to call it correctly: setup steps, parameter meaning, session persistence, default session selection, and the alternative tool path. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents magic_link_url thoroughly at 100% coverage, so the baseline is 3. The description adds meaningful nuance beyond the schema: the URL is used only to derive a cache key/origin and is never opened or navigated to, saving the agent from a plausible misunderstanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Capture a HoneyBook client-portal session via the fetchproxy 0.3.0 browser extension.' It also differentiates from the sibling use_flow_link by explicitly warning that questionnaire links require the sibling tool and that this tool refuses them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit prerequisites (install fetchproxy, open and sign in to the magic-link URL, leave the tab open), clarifies the tool does not open or navigate to the URL, and names the exact alternative tool for questionnaire links. This leaves no ambiguity about when and how to invoke it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools