honeybook-mcp 0.8.0 → 0.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -7,7 +7,7 @@
7
7
  },
8
8
  "metadata": {
9
9
  "description": "HoneyBook client-portal tools for Claude Code",
10
- "version": "0.8.0"
10
+ "version": "0.8.1"
11
11
  },
12
12
  "plugins": [
13
13
  {
@@ -15,7 +15,7 @@
15
15
  "displayName": "HoneyBook",
16
16
  "source": "./",
17
17
  "description": "HoneyBook client-portal MCP for Claude — view wedding-vendor contracts and invoices via MCP",
18
- "version": "0.8.0",
18
+ "version": "0.8.1",
19
19
  "author": {
20
20
  "name": "Chris Chall"
21
21
  },
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "honeybook",
3
3
  "displayName": "HoneyBook",
4
- "version": "0.8.0",
4
+ "version": "0.8.1",
5
5
  "description": "HoneyBook client-portal MCP for Claude — view wedding-vendor contracts and invoices via MCP",
6
6
  "author": {
7
7
  "name": "Chris Chall",
package/dist/bundle.js CHANGED
@@ -39509,7 +39509,7 @@ function bridgeErrorInfo(err) {
39509
39509
  // package.json
39510
39510
  var package_default = {
39511
39511
  name: "honeybook-mcp",
39512
- version: "0.8.0",
39512
+ version: "0.8.1",
39513
39513
  mcpName: "io.github.chrischall/honeybook-mcp",
39514
39514
  description: "HoneyBook client-portal MCP server for Claude",
39515
39515
  author: "Claude Code (AI) <https://www.anthropic.com/claude>",
@@ -39902,21 +39902,28 @@ var FlowClient = class {
39902
39902
  }
39903
39903
  }
39904
39904
  /**
39905
- * Explain a bare 400.
39905
+ * Explain an untyped 400.
39906
39906
  *
39907
- * A flow read that is missing a required input answers `400` with
39908
- * `"Unexpected server error"` and no `error_type` — nothing in the body says
39909
- * which input, and it reads exactly like an auth failure. Left alone it sends
39910
- * people to re-capture a credential that is fine, so the two known causes are
39911
- * named here and the auth reading is denied outright.
39907
+ * A 400 with no `error_type` says nothing about which input was wrong and
39908
+ * reads exactly like an auth failure; left alone it sends people to
39909
+ * re-capture a credential that is fine, so the auth reading is denied
39910
+ * outright.
39911
+ *
39912
+ * What can NOT reach here is the client version. Probed live 2026-08-31,
39913
+ * every version failure — stale, garbage, empty, omitted — answers 400 with
39914
+ * `error_type: HBWrongAPIVersionError` and `error_data.server_api_version`,
39915
+ * which `hbApiRequest` intercepts and retries once on the server's own
39916
+ * number, so it self-heals a layer below. `ctxc` cannot reach here either:
39917
+ * the API ignores it entirely (omitted, bogus, and `/client/`-less all return
39918
+ * the same 200, byte-identical), and naming it here only misdirected. So the
39919
+ * version is offered as the input to CHECK rather than as a known cause, and
39920
+ * this is deliberately vaguer than 0.8.0's message: no cause is confirmed.
39912
39921
  */
39913
39922
  badRequestError(err) {
39914
39923
  return new Error(
39915
39924
  `${err.message}
39916
39925
 
39917
- HoneyBook answers a flow read with a bare 400 when a required input is missing, without saying which. The two that do it:
39918
- 1. hb-api-client-version \u2014 sent as ${this.apiVersion}. It is read from /api/gon at startup, so it normally tracks HoneyBook; if HONEYBOOK_API_VERSION is pinned in your environment that value can have rotted, so unset it to re-read the live one.
39919
- 2. ctxc \u2014 the company id from /api/v2/flow/<flowId>/minimal, required on every /api/v2/client/\u2026 read.
39926
+ HoneyBook answered this flow read with a 400 carrying no error_type, so nothing in the response says which input it objected to. The input worth checking is hb-api-client-version, sent as ${this.apiVersion}: it is read from /api/gon at startup, so it normally tracks HoneyBook, but a pinned HONEYBOOK_API_VERSION can have rotted \u2014 unset it to re-read the live one. (A version HoneyBook actively rejects answers with error_type HBWrongAPIVersionError and is retried automatically, so it would not surface here.)
39920
39927
  This is NOT an auth failure \u2014 the credential is very likely fine, so re-running \`use_flow_link\` will not help.`
39921
39928
  );
39922
39929
  }
@@ -39960,7 +39967,7 @@ async function fetchFlowMinimal(flowId, opts) {
39960
39967
  const detail = body.slice(0, 300);
39961
39968
  const cause = response.status === 404 ? `no flow ${flowId} \u2014 it may have been deleted, or the id is wrong` : /WrongAPIVersion/i.test(body) ? `HoneyBook rejected hb-api-client-version ${opts.apiVersion}; this package's pinned value needs updating` : "that route is public, so this is a HoneyBook-side problem rather than a credential one";
39962
39969
  throw new Error(
39963
- `HoneyBook flow: GET /api/v2/flow/${flowId}/minimal answered ${response.status} \u2014 ${cause}. It is where the context id (ctxc) required by the questionnaire read comes from.` + (detail ? ` Response: ${detail}` : "")
39970
+ `HoneyBook flow: GET /api/v2/flow/${flowId}/minimal answered ${response.status} \u2014 ${cause}. It is where the context id (ctxc) the questionnaire read sends comes from.` + (detail ? ` Response: ${detail}` : "")
39964
39971
  );
39965
39972
  }
39966
39973
  return await response.json();
@@ -40003,21 +40010,17 @@ async function getFlow(args) {
40003
40010
  apiVersion: client.getApiVersion()
40004
40011
  });
40005
40012
  const contextId = flowContextId(minimal);
40006
- if (!contextId) {
40007
- throw new Error(
40008
- `HoneyBook flow: no context id for flow ${flowId}. The questionnaire read requires \`ctxc\`, the vendor company id, and GET /api/v2/flow/<flowId>/minimal did not carry one at branding_data.company_id. Calling /active without it answers a bare 400 that reads like an auth failure, so this stops here: it is not an auth problem and re-running \`use_flow_link\` will not help.`
40009
- );
40010
- }
40011
- const query = new URLSearchParams({ ctxc: contextId });
40013
+ const path = `/api/v2/client/flow/${encodeURIComponent(flowId)}/active`;
40012
40014
  const flow = await client.request(
40013
40015
  "GET",
40014
- `/api/v2/client/flow/${encodeURIComponent(flowId)}/active?${query}`
40016
+ contextId ? `${path}?${new URLSearchParams({ ctxc: contextId })}` : path
40015
40017
  );
40016
40018
  const head = {
40017
40019
  flowId,
40018
40020
  portalOrigin: client.credential.portalOrigin,
40019
- // Reported because it is a second input the read depends on: when this call
40020
- // fails, knowing which company id was used is half the diagnosis.
40021
+ // Reported because it is a second input the request carries: when this call
40022
+ // fails, knowing which company id was sent is half the diagnosis. `null` is
40023
+ // a normal outcome, not an error — the read does not require one.
40021
40024
  contextId
40022
40025
  };
40023
40026
  if (args.section === "raw") return textResult({ ...head, flow });
@@ -40040,7 +40043,7 @@ function registerFlowTools(server) {
40040
40043
  description: "Capture a HoneyBook QUESTIONNAIRE (flow) credential via the fetchproxy browser extension. Use this for a link shaped https://<vendor>.hbportal.co/flow/<flowId>?hash=\u2026 \u2014 for a client-portal link (/app/link/resolve/\u2026) use `use_magic_link` instead. Prerequisites: install the fetchproxy extension, open the questionnaire link in that browser and let the page render, then run this tool. It snapshots localStorage[\"HONEYBOOK_REACT_WEAK_AUTH_<flowId>\"] into ~/.honeybook-mcp/flows.json. A flow credential is HoneyBook's 'weak auth': it is scoped to that ONE questionnaire and cannot read portal workspaces, files, invoices or payment methods. Because the storage key contains the flow id, the extension asks you to re-approve the scope once per new questionnaire.",
40041
40044
  inputSchema: {
40042
40045
  flow_link_url: external_exports.string().url().describe(
40043
- "Full questionnaire link from the vendor email, e.g. https://<vendor>.hbportal.co/flow/<flowId>?hash=\u2026&userId=\u2026 The ?hash= parameter is the credential, so use the original link rather than the URL the page rewrites to."
40046
+ "Questionnaire link, e.g. https://<vendor>.hbportal.co/flow/<flowId>?hash=\u2026&userId=\u2026 Only the /flow/<flowId> segment is required: the credential is read out of the open page's localStorage, so the rewritten step URL (/flow/<flowId>/1-Questions) works too. The URL's ?hash= is used only as a fallback when the page stored none, so prefer the original email link if the capture reports no hash."
40044
40047
  )
40045
40048
  },
40046
40049
  annotations: { readOnlyHint: false }
@@ -40050,7 +40053,7 @@ function registerFlowTools(server) {
40050
40053
  server.registerTool(
40051
40054
  "get_flow",
40052
40055
  {
40053
- description: 'Read a HoneyBook questionnaire (flow) \u2014 its pages, questions and any answers already submitted \u2014 using a credential captured by `use_flow_link`. Requires a flow credential; a client-portal session will NOT work here, and vice versa. Defaults to the most recently captured flow. Makes two calls: the public /api/v2/flow/<id>/minimal for the vendor company id, then /api/v2/client/flow/<id>/active?ctxc=<companyId>. A questionnaire larger than the default ceiling answers with its size and top-level keys instead; call again with section="raw" for the whole thing.',
40056
+ description: 'Read a HoneyBook questionnaire (flow) \u2014 its pages, questions and any answers already submitted \u2014 using a credential captured by `use_flow_link`. Requires a flow credential; a client-portal session will NOT work here, and vice versa. Defaults to the most recently captured flow. Makes two calls: the public /api/v2/flow/<id>/minimal for the vendor company id, then /api/v2/client/flow/<id>/active, passing that id as ?ctxc= when /minimal supplied one. A questionnaire larger than the default ceiling answers with its size and top-level keys instead; call again with section="raw" for the whole thing.',
40054
40057
  inputSchema: {
40055
40058
  flow_id: external_exports.string().optional().describe(
40056
40059
  "Flow id to read. Omit to use the most recently captured flow credential. Run `list_active_sessions` to see the active flow ids."
@@ -40513,7 +40516,7 @@ var __dirname = dirname2(fileURLToPath(import.meta.url));
40513
40516
  await loadDotenvSafely({ path: join6(__dirname, "..", ".env"), override: false });
40514
40517
  await runMcp({
40515
40518
  name: "honeybook-mcp",
40516
- version: "0.8.0",
40519
+ version: "0.8.1",
40517
40520
  // x-release-please-version
40518
40521
  tools: [
40519
40522
  registerSessionTools,
@@ -73,23 +73,32 @@ export class FlowClient {
73
73
  }
74
74
  }
75
75
  /**
76
- * Explain a bare 400.
76
+ * Explain an untyped 400.
77
77
  *
78
- * A flow read that is missing a required input answers `400` with
79
- * `"Unexpected server error"` and no `error_type` — nothing in the body says
80
- * which input, and it reads exactly like an auth failure. Left alone it sends
81
- * people to re-capture a credential that is fine, so the two known causes are
82
- * named here and the auth reading is denied outright.
78
+ * A 400 with no `error_type` says nothing about which input was wrong and
79
+ * reads exactly like an auth failure; left alone it sends people to
80
+ * re-capture a credential that is fine, so the auth reading is denied
81
+ * outright.
82
+ *
83
+ * What can NOT reach here is the client version. Probed live 2026-08-31,
84
+ * every version failure — stale, garbage, empty, omitted — answers 400 with
85
+ * `error_type: HBWrongAPIVersionError` and `error_data.server_api_version`,
86
+ * which `hbApiRequest` intercepts and retries once on the server's own
87
+ * number, so it self-heals a layer below. `ctxc` cannot reach here either:
88
+ * the API ignores it entirely (omitted, bogus, and `/client/`-less all return
89
+ * the same 200, byte-identical), and naming it here only misdirected. So the
90
+ * version is offered as the input to CHECK rather than as a known cause, and
91
+ * this is deliberately vaguer than 0.8.0's message: no cause is confirmed.
83
92
  */
84
93
  badRequestError(err) {
85
94
  return new Error(`${err.message}\n\n` +
86
- 'HoneyBook answers a flow read with a bare 400 when a required input is missing, without ' +
87
- 'saying which. The two that do it:\n' +
88
- ` 1. hb-api-client-version — sent as ${this.apiVersion}. It is read from /api/gon at ` +
89
- 'startup, so it normally tracks HoneyBook; if HONEYBOOK_API_VERSION is pinned in your ' +
90
- 'environment that value can have rotted, so unset it to re-read the live one.\n' +
91
- ' 2. ctxc — the company id from /api/v2/flow/<flowId>/minimal, required on every ' +
92
- '/api/v2/client/… read.\n' +
95
+ 'HoneyBook answered this flow read with a 400 carrying no error_type, so nothing in the ' +
96
+ 'response says which input it objected to. The input worth checking is ' +
97
+ `hb-api-client-version, sent as ${this.apiVersion}: it is read from /api/gon at startup, ` +
98
+ 'so it normally tracks HoneyBook, but a pinned HONEYBOOK_API_VERSION can have rotted — ' +
99
+ 'unset it to re-read the live one. (A version HoneyBook actively rejects answers with ' +
100
+ 'error_type HBWrongAPIVersionError and is retried automatically, so it would not surface ' +
101
+ 'here.)\n' +
93
102
  'This is NOT an auth failure — the credential is very likely fine, so re-running ' +
94
103
  '`use_flow_link` will not help.');
95
104
  }
@@ -167,7 +176,7 @@ export async function fetchFlowMinimal(flowId, opts) {
167
176
  ? `HoneyBook rejected hb-api-client-version ${opts.apiVersion}; this package's pinned value needs updating`
168
177
  : 'that route is public, so this is a HoneyBook-side problem rather than a credential one';
169
178
  throw new Error(`HoneyBook flow: GET /api/v2/flow/${flowId}/minimal answered ${response.status} — ${cause}. ` +
170
- `It is where the context id (ctxc) required by the questionnaire read comes from.` +
179
+ `It is where the context id (ctxc) the questionnaire read sends comes from.` +
171
180
  (detail ? ` Response: ${detail}` : ''));
172
181
  }
173
182
  return (await response.json());
@@ -176,12 +185,14 @@ export async function fetchFlowMinimal(flowId, opts) {
176
185
  * The `ctxc` value: the vendor's company id.
177
186
  *
178
187
  * The app sets `params.ctxc` from `clientPortalConfigStore.clientPortalCompanyId`
179
- * in its request interceptor, and `branding_data.company_id` is that same id —
180
- * verified live as the only 24-hex value the `/minimal` response carries.
188
+ * in its request interceptor, and `branding_data.company_id` is that same id.
189
+ * (0.8.0's docblock called it the only 24-hex value in `/minimal`; it is not —
190
+ * `theme._id` is another — so this reads the field by name, as it always did.)
181
191
  *
182
- * Returns `null` rather than guessing: a wrong `ctxc` is the same bare 400 as a
183
- * missing one, so a fabricated value would be indistinguishable from a genuine
184
- * failure.
192
+ * Returns `null` rather than guessing, and `null` is a normal outcome: the read
193
+ * omits `ctxc` entirely in that case. The API ignores the value regardless —
194
+ * verified live 2026-08-31 that a bogus one returns the same 200 — so a
195
+ * fabricated id would be neither safer nor more honest than sending none.
185
196
  */
186
197
  export function flowContextId(minimal) {
187
198
  return minimal.branding_data?.company_id ?? null;
package/dist/index.js CHANGED
@@ -13,7 +13,7 @@ import { registerContractTools } from './tools/contracts.js';
13
13
  import { registerInvoiceTools } from './tools/invoices.js';
14
14
  await runMcp({
15
15
  name: 'honeybook-mcp',
16
- version: '0.8.0', // x-release-please-version
16
+ version: '0.8.1', // x-release-please-version
17
17
  tools: [
18
18
  registerSessionTools,
19
19
  registerFlowTools,
@@ -82,24 +82,22 @@ export async function getFlow(args) {
82
82
  apiVersion: client.getApiVersion(),
83
83
  });
84
84
  const contextId = flowContextId(minimal);
85
- // Refuse rather than calling /active without it. A missing ctxc produces the
86
- // same bare 400 as a stale client version, and a 400 here reads as an auth
87
- // failure — so falling through would send someone to re-capture a credential
88
- // that is perfectly good.
89
- if (!contextId) {
90
- throw new Error(`HoneyBook flow: no context id for flow ${flowId}. The questionnaire read requires ` +
91
- '`ctxc`, the vendor company id, and GET /api/v2/flow/<flowId>/minimal did not carry one ' +
92
- 'at branding_data.company_id. Calling /active without it answers a bare 400 that reads ' +
93
- 'like an auth failure, so this stops here: it is not an auth problem and re-running ' +
94
- '`use_flow_link` will not help.');
95
- }
96
- const query = new URLSearchParams({ ctxc: contextId });
97
- const flow = await client.request('GET', `/api/v2/client/flow/${encodeURIComponent(flowId)}/active?${query}`);
85
+ // `ctxc` is sent when /minimal carries one and simply omitted when it does
86
+ // not. It is NOT required: probed live on 2026-08-31 with a real credential,
87
+ // omitting it — and sending a bogus one, and dropping `/client/` — returns
88
+ // the same 200 with a byte-identical body. 0.8.0 refused here instead, which
89
+ // could only ever invent a failure for a flow whose /minimal lacks
90
+ // branding_data.company_id. The URL still matches the app's own request,
91
+ // because matching the shipped client is the cheap way to stay right if the
92
+ // server ever does start enforcing it.
93
+ const path = `/api/v2/client/flow/${encodeURIComponent(flowId)}/active`;
94
+ const flow = await client.request('GET', contextId ? `${path}?${new URLSearchParams({ ctxc: contextId })}` : path);
98
95
  const head = {
99
96
  flowId,
100
97
  portalOrigin: client.credential.portalOrigin,
101
- // Reported because it is a second input the read depends on: when this call
102
- // fails, knowing which company id was used is half the diagnosis.
98
+ // Reported because it is a second input the request carries: when this call
99
+ // fails, knowing which company id was sent is half the diagnosis. `null` is
100
+ // a normal outcome, not an error — the read does not require one.
103
101
  contextId,
104
102
  };
105
103
  if (args.section === 'raw')
@@ -126,12 +124,12 @@ export function registerFlowTools(server) {
126
124
  flow_link_url: z
127
125
  .string()
128
126
  .url()
129
- .describe('Full questionnaire link from the vendor email, e.g. https://<vendor>.hbportal.co/flow/<flowId>?hash=…&userId=… The ?hash= parameter is the credential, so use the original link rather than the URL the page rewrites to.'),
127
+ .describe('Questionnaire link, e.g. https://<vendor>.hbportal.co/flow/<flowId>?hash=…&userId=… Only the /flow/<flowId> segment is required: the credential is read out of the open page\'s localStorage, so the rewritten step URL (/flow/<flowId>/1-Questions) works too. The URL\'s ?hash= is used only as a fallback when the page stored none, so prefer the original email link if the capture reports no hash.'),
130
128
  },
131
129
  annotations: { readOnlyHint: false },
132
130
  }, useFlowLink);
133
131
  server.registerTool('get_flow', {
134
- description: 'Read a HoneyBook questionnaire (flow) — its pages, questions and any answers already submitted — using a credential captured by `use_flow_link`. Requires a flow credential; a client-portal session will NOT work here, and vice versa. Defaults to the most recently captured flow. Makes two calls: the public /api/v2/flow/<id>/minimal for the vendor company id, then /api/v2/client/flow/<id>/active?ctxc=<companyId>. A questionnaire larger than the default ceiling answers with its size and top-level keys instead; call again with section="raw" for the whole thing.',
132
+ description: 'Read a HoneyBook questionnaire (flow) — its pages, questions and any answers already submitted — using a credential captured by `use_flow_link`. Requires a flow credential; a client-portal session will NOT work here, and vice versa. Defaults to the most recently captured flow. Makes two calls: the public /api/v2/flow/<id>/minimal for the vendor company id, then /api/v2/client/flow/<id>/active, passing that id as ?ctxc= when /minimal supplied one. A questionnaire larger than the default ceiling answers with its size and top-level keys instead; call again with section="raw" for the whole thing.',
135
133
  inputSchema: {
136
134
  flow_id: z
137
135
  .string()
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "honeybook-mcp",
3
- "version": "0.8.0",
3
+ "version": "0.8.1",
4
4
  "mcpName": "io.github.chrischall/honeybook-mcp",
5
5
  "description": "HoneyBook client-portal MCP server for Claude",
6
6
  "author": "Claude Code (AI) <https://www.anthropic.com/claude>",
package/server.json CHANGED
@@ -6,12 +6,12 @@
6
6
  "url": "https://github.com/chrischall/honeybook-mcp",
7
7
  "source": "github"
8
8
  },
9
- "version": "0.8.0",
9
+ "version": "0.8.1",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "identifier": "honeybook-mcp",
14
- "version": "0.8.0",
14
+ "version": "0.8.1",
15
15
  "transport": {
16
16
  "type": "stdio"
17
17
  },