@charisol/plexo-mcp 1.0.7 → 1.0.9

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.
@@ -147,15 +147,23 @@ class PlexoClient {
147
147
  /**
148
148
  * Creates a new page nested under an existing landing page (its home page
149
149
  * for a top-level page, or another sub-page's id to nest deeper) — how a
150
- * single landing page becomes a multi-page site. Starts blank; use
151
- * updateTemplate() with the returned templateId to add content.
150
+ * single landing page becomes a multi-page site. Starts blank unless
151
+ * htmlContent is given, in which case it's created as a RAW_UPLOAD page
152
+ * instead — see updateTemplate() (BUILDER) / updateRawLandingPage()
153
+ * (RAW_UPLOAD) to add/edit content afterward, depending on which mode.
152
154
  */
153
155
  async createLandingPageSubpage(params) {
154
156
  this.checkAuth();
155
157
  const res = await fetch(`${this.baseUrl}/api/templates`, {
156
158
  method: "POST",
157
159
  headers: this.getHeaders(),
158
- body: JSON.stringify({ name: params.name, parentId: params.parentTemplateId, slug: params.slug }),
160
+ body: JSON.stringify({
161
+ name: params.name,
162
+ parentId: params.parentTemplateId,
163
+ slug: params.slug,
164
+ htmlContent: params.htmlContent,
165
+ acceptAup: params.acceptAup,
166
+ }),
159
167
  });
160
168
  const data = (await res.json());
161
169
  if (!res.ok) {
@@ -163,6 +171,68 @@ class PlexoClient {
163
171
  }
164
172
  return data;
165
173
  }
174
+ /**
175
+ * Creates a landing page from raw HTML supplied directly (no designJson),
176
+ * served byte-for-byte as given — a different storage mode from
177
+ * createLandingPage/publishLandingPage, which are for the drag-and-drop
178
+ * BUILDER pages built from designJson. Same endpoint upload-raw's REST
179
+ * multipart path uses, but with a JSON body — this client has no real
180
+ * file to upload.
181
+ */
182
+ async createRawLandingPage(params) {
183
+ this.checkAuth();
184
+ const res = await fetch(`${this.baseUrl}/api/v1/templates/upload-raw`, {
185
+ method: "POST",
186
+ headers: this.getHeaders(),
187
+ body: JSON.stringify(params),
188
+ });
189
+ const data = (await res.json());
190
+ if (!res.ok) {
191
+ throw new Error(data?.error || `Raw landing page creation failed with status ${res.status}`);
192
+ }
193
+ return data;
194
+ }
195
+ /**
196
+ * Creates AND publishes a raw-HTML landing page in one call — the combined
197
+ * equivalent of createRawLandingPage() + publishExistingLandingPage().
198
+ */
199
+ async publishRawLandingPage(params) {
200
+ const created = await this.createRawLandingPage({
201
+ name: params.name,
202
+ htmlContent: params.htmlContent,
203
+ acceptAup: params.acceptAup,
204
+ });
205
+ const templateId = created?.templateId;
206
+ if (!templateId) {
207
+ throw new Error(created?.error || "Raw landing page creation did not return a templateId.");
208
+ }
209
+ const published = await this.publishExistingLandingPage({
210
+ templateId,
211
+ domain: params.domain,
212
+ type: params.type,
213
+ });
214
+ return { ...created, ...published };
215
+ }
216
+ /**
217
+ * Replaces an existing RAW_UPLOAD page's HTML in place, under the same
218
+ * template id — the editable URL, live URL, and domain (if published) are
219
+ * all unchanged. Same endpoint replace-upload's REST multipart path uses,
220
+ * but with a JSON body.
221
+ */
222
+ async updateRawLandingPage(params) {
223
+ this.checkAuth();
224
+ const { templateId, ...body } = params;
225
+ const res = await fetch(`${this.baseUrl}/api/v1/templates/${encodeURIComponent(templateId)}/replace-upload`, {
226
+ method: "POST",
227
+ headers: this.getHeaders(),
228
+ body: JSON.stringify(body),
229
+ });
230
+ const data = (await res.json());
231
+ if (!res.ok) {
232
+ throw new Error(data?.error || `Raw landing page update failed with status ${res.status}`);
233
+ }
234
+ return data;
235
+ }
166
236
  /**
167
237
  * Returns every page belonging to the same multi-page site as templateId
168
238
  * — its home page plus all nested sub-pages. templateId can be the home
@@ -273,5 +343,112 @@ class PlexoClient {
273
343
  }
274
344
  return data;
275
345
  }
346
+ /** Fetches a single template's full details, including designJson — used by the blog
347
+ * layout tools to read back a layout template's current content (there's no other
348
+ * templateId-scoped GET in the public API; list endpoints only return metadata). */
349
+ async getTemplate(templateId) {
350
+ this.checkAuth();
351
+ const res = await fetch(`${this.baseUrl}/api/v1/templates/${encodeURIComponent(templateId)}`, {
352
+ method: "GET",
353
+ headers: this.getHeaders(),
354
+ });
355
+ const data = (await res.json());
356
+ if (!res.ok) {
357
+ throw new Error(data?.error || `Failed to fetch template (Status ${res.status})`);
358
+ }
359
+ return data;
360
+ }
361
+ /** Shared request helper for every /api/blog/{templateId}/... route below — these are
362
+ * the same admin endpoints the Plexo dashboard's own blog UI calls, and (like every
363
+ * other route in this client) accept the same Bearer/x-api-key auth as the rest of the
364
+ * public API (see resolveUser/resolveBlogAdminSite server-side). */
365
+ async blogFetch(method, templateId, path, body) {
366
+ this.checkAuth();
367
+ const res = await fetch(`${this.baseUrl}/api/blog/${encodeURIComponent(templateId)}${path}`, {
368
+ method,
369
+ headers: this.getHeaders(),
370
+ ...(body !== undefined ? { body: JSON.stringify(body) } : {}),
371
+ });
372
+ const data = (await res.json().catch(() => ({})));
373
+ if (!res.ok) {
374
+ throw new Error(data?.error || `Blog request failed (Status ${res.status})`);
375
+ }
376
+ return data;
377
+ }
378
+ /** Idempotent — returns the existing layout template id if one's already attached to
379
+ * this kind rather than creating a duplicate. Pair with updateTemplate() to set its
380
+ * designJson (see blogTools.ts's designBlogLayout). */
381
+ async ensureBlogLayout(templateId, kind) {
382
+ return this.blogFetch("POST", templateId, `/layout/${kind}`);
383
+ }
384
+ /** Detaches the layout (reverts to the default theme) without deleting the underlying Template row. */
385
+ async resetBlogLayout(templateId, kind) {
386
+ return this.blogFetch("DELETE", templateId, `/layout/${kind}`);
387
+ }
388
+ async getBlogSite(templateId) {
389
+ return this.blogFetch("GET", templateId, "/site");
390
+ }
391
+ async updateBlogSite(templateId, patch) {
392
+ return this.blogFetch("PATCH", templateId, "/site", patch);
393
+ }
394
+ async listBlogPosts(templateId, params = {}) {
395
+ const query = new URLSearchParams();
396
+ if (params.status)
397
+ query.set("status", params.status);
398
+ if (params.search)
399
+ query.set("search", params.search);
400
+ if (params.categoryId)
401
+ query.set("categoryId", params.categoryId);
402
+ const qs = query.toString();
403
+ return this.blogFetch("GET", templateId, `/posts${qs ? `?${qs}` : ""}`);
404
+ }
405
+ async getBlogPost(templateId, postId) {
406
+ return this.blogFetch("GET", templateId, `/posts/${encodeURIComponent(postId)}`);
407
+ }
408
+ async createBlogPost(templateId, payload) {
409
+ return this.blogFetch("POST", templateId, "/posts", payload);
410
+ }
411
+ async updateBlogPost(templateId, postId, payload) {
412
+ return this.blogFetch("PATCH", templateId, `/posts/${encodeURIComponent(postId)}`, payload);
413
+ }
414
+ async deleteBlogPost(templateId, postId) {
415
+ return this.blogFetch("DELETE", templateId, `/posts/${encodeURIComponent(postId)}`);
416
+ }
417
+ async listBlogCategories(templateId) {
418
+ return this.blogFetch("GET", templateId, "/categories");
419
+ }
420
+ async createBlogCategory(templateId, payload) {
421
+ return this.blogFetch("POST", templateId, "/categories", payload);
422
+ }
423
+ async deleteBlogCategory(templateId, categoryId) {
424
+ return this.blogFetch("DELETE", templateId, `/categories/${encodeURIComponent(categoryId)}`);
425
+ }
426
+ async listBlogTags(templateId) {
427
+ return this.blogFetch("GET", templateId, "/tags");
428
+ }
429
+ async createBlogTag(templateId, name) {
430
+ return this.blogFetch("POST", templateId, "/tags", { name });
431
+ }
432
+ async deleteBlogTag(templateId, tagId) {
433
+ return this.blogFetch("DELETE", templateId, `/tags/${encodeURIComponent(tagId)}`);
434
+ }
435
+ async listBlogAuthors(templateId) {
436
+ return this.blogFetch("GET", templateId, "/authors");
437
+ }
438
+ async createBlogAuthor(templateId, payload) {
439
+ return this.blogFetch("POST", templateId, "/authors", payload);
440
+ }
441
+ async deleteBlogAuthor(templateId, authorId) {
442
+ return this.blogFetch("DELETE", templateId, `/authors/${encodeURIComponent(authorId)}`);
443
+ }
444
+ async listBlogComments(templateId, status) {
445
+ return this.blogFetch("GET", templateId, `/comments${status ? `?status=${encodeURIComponent(status)}` : ""}`);
446
+ }
447
+ async moderateBlogComment(templateId, commentId, status) {
448
+ return this.blogFetch("PATCH", templateId, `/comments/${encodeURIComponent(commentId)}`, { status });
449
+ }
450
+ async deleteBlogComment(templateId, commentId) {
451
+ return this.blogFetch("DELETE", templateId, `/comments/${encodeURIComponent(commentId)}`);
452
+ }
276
453
  }
277
454
  exports.PlexoClient = PlexoClient;
package/dist/index.js CHANGED
@@ -5,6 +5,7 @@ const index_js_1 = require("@modelcontextprotocol/sdk/server/index.js");
5
5
  const stdio_js_1 = require("@modelcontextprotocol/sdk/server/stdio.js");
6
6
  const types_js_1 = require("@modelcontextprotocol/sdk/types.js");
7
7
  const plexoClient_js_1 = require("./client/plexoClient.js");
8
+ const blogTools_js_1 = require("./blogTools.js");
8
9
  const server = new index_js_1.Server({
9
10
  name: "plexo-mcp",
10
11
  version: "1.0.0",
@@ -129,7 +130,7 @@ EXAMPLE VALID designJson PAYLOAD (hero row, plus a 3-item product grid row):
129
130
  properties: {
130
131
  type: {
131
132
  type: "string",
132
- enum: ["heading", "paragraph", "text", "button", "card", "image", "menu", "social", "divider", "spacer", "form_container", "input", "textarea", "select", "carousel", "html", "icon", "table", "timer", "video"],
133
+ enum: ["heading", "paragraph", "text", "button", "card", "image", "menu", "social", "divider", "spacer", "form_container", "input", "textarea", "select", "carousel", "html", "icon", "table", "timer", "video", "accordion", "blog_title", "blog_content", "blog_featured_image", "blog_date", "blog_author", "blog_categories", "blog_comments", "blog_post_list"],
133
134
  },
134
135
  style: { type: "object" },
135
136
  attributes: { type: "object", description: "Component attributes (text, href, src, title, description, links, fields). For type 'html', raw markup goes under 'htmlContent' — NOT 'text'." },
@@ -221,7 +222,7 @@ Uses the SAME fully-hydrated layout schema as publish_landing_page — designJso
221
222
  properties: {
222
223
  type: {
223
224
  type: "string",
224
- enum: ["heading", "paragraph", "text", "button", "card", "image", "menu", "social", "divider", "spacer", "form_container", "input", "textarea", "select", "carousel", "html", "icon", "table", "timer", "video"],
225
+ enum: ["heading", "paragraph", "text", "button", "card", "image", "menu", "social", "divider", "spacer", "form_container", "input", "textarea", "select", "carousel", "html", "icon", "table", "timer", "video", "accordion", "blog_title", "blog_content", "blog_featured_image", "blog_date", "blog_author", "blog_categories", "blog_comments", "blog_post_list"],
225
226
  },
226
227
  style: { type: "object" },
227
228
  attributes: {
@@ -277,6 +278,8 @@ Map the returned tokens into designJson style fields: color-type tokens into bac
277
278
  name: "update_template",
278
279
  description: `Edits an existing landing page or email template in place, under the same template ID. Recompiles and re-saves the HTML from the new designJson — the editable URL stays the same, and for a published landing page the live URL and domain are unchanged too (this does not publish/unpublish or change the domain; call publish_landing_page again with a domain for that).
279
280
 
281
+ This is for drag-and-drop BUILDER pages only — it REJECTS a page created via create_raw_landing_page/publish_raw_landing_page/create_landing_page_subpage's htmlContent option. Use update_raw_landing_page for those instead. If unsure which kind an existing page is, check its sourceType via list_landing_pages/get_landing_page_pages first.
282
+
280
283
  Uses the SAME fully-hydrated layout schema as publish_landing_page/create_email_template — designJson MUST be { "body": { "style": {...}, "rows": [{ "id", "style", "columns": [{ "id", "width", "elements": [{ "id", "type", "style", "attributes" }] }] }] } }. There is no shorthand row format; rows without a 'columns' array are rejected, and this replaces the ENTIRE designJson — to edit one section, fetch the current template's designJson first (via list_landing_pages/list_email_templates, or the Plexo dashboard) and send back the full modified tree, not just the changed part. See publish_landing_page's description for a full worked example.`,
281
284
  inputSchema: {
282
285
  type: "object",
@@ -301,6 +304,30 @@ Uses the SAME fully-hydrated layout schema as publish_landing_page/create_email_
301
304
  required: ["templateId", "designJson"],
302
305
  },
303
306
  },
307
+ {
308
+ name: "update_raw_landing_page",
309
+ description: `Replaces an existing RAW_UPLOAD page's HTML in place, under the same template ID — the editable URL, live URL, and domain (if published) are all unchanged. This is for pages created via create_raw_landing_page/publish_raw_landing_page/create_landing_page_subpage's htmlContent option ONLY — it REJECTS a drag-and-drop BUILDER page (use update_template for those). If unsure which kind an existing page is, check its sourceType via list_landing_pages/get_landing_page_pages first.
310
+
311
+ This replaces the ENTIRE HTML document, not a patch — send back the full modified document. Same 1MB single-document scope as create_raw_landing_page.`,
312
+ inputSchema: {
313
+ type: "object",
314
+ properties: {
315
+ templateId: {
316
+ type: "string",
317
+ description: "ID of the raw-upload page to update — the templateId returned by create_raw_landing_page, publish_raw_landing_page, list_landing_pages, or get_landing_page_pages.",
318
+ },
319
+ htmlContent: {
320
+ type: "string",
321
+ description: "The FULL replacement raw HTML document (up to 1MB) — not a partial patch.",
322
+ },
323
+ name: {
324
+ type: "string",
325
+ description: "Optional new title for the page. Omit to keep the existing name.",
326
+ },
327
+ },
328
+ required: ["templateId", "htmlContent"],
329
+ },
330
+ },
304
331
  {
305
332
  name: "create_landing_page",
306
333
  description: `Creates and saves a landing page template WITHOUT publishing it to a domain — use this when the user wants to build a page (or start a multi-page site) first and go live later. Call publish_existing_landing_page afterward with the returned templateId to link a subdomain or custom domain whenever they're ready. To create a page AND publish it in one step, use publish_landing_page instead.
@@ -321,6 +348,63 @@ Uses the SAME fully-hydrated layout schema as publish_landing_page — see its d
321
348
  required: ["designJson"],
322
349
  },
323
350
  },
351
+ {
352
+ name: "create_raw_landing_page",
353
+ description: `Creates a landing page from a RAW HTML document you supply directly, WITHOUT publishing it to a domain — for when the user wants a page built from hand-written or externally-sourced HTML/CSS/JS instead of Plexo's drag-and-drop builder. The page is served byte-for-byte as given, completely unsanitized (no designJson, no compilation) — this is a DIFFERENT storage mode from create_landing_page/publish_landing_page/update_template, which are for the drag-and-drop BUILDER pages built from designJson. Do NOT use this tool for a page you want to build with designJson — use create_landing_page instead.
354
+
355
+ Scope: a single self-contained HTML document only (inline or CDN-linked CSS/JS), up to 1MB — no zip/multi-file sites with separate local asset files (that's a dashboard-only "import a website" feature with no MCP equivalent yet).
356
+
357
+ Because this serves unsanitized content, the account must accept the Acceptable Use Policy once — see the acceptAup argument. Call publish_existing_landing_page afterward with the returned templateId to link a subdomain or custom domain, or use publish_raw_landing_page to create and publish in one step. To edit this page's HTML later, use update_raw_landing_page (NOT update_template — that tool rejects raw-upload pages).`,
358
+ inputSchema: {
359
+ type: "object",
360
+ properties: {
361
+ name: {
362
+ type: "string",
363
+ description: "Title of the landing page (e.g. 'Kicks Store').",
364
+ },
365
+ htmlContent: {
366
+ type: "string",
367
+ description: "The full, self-contained raw HTML document to serve as-is (up to 1MB). Inline or CDN-linked CSS/JS only — no separate local asset files.",
368
+ },
369
+ acceptAup: {
370
+ type: "boolean",
371
+ description: "Pass true ONLY after explicitly telling the user this publishes unsanitized HTML/CSS/JS as-is and getting their confirmation of the Acceptable Use Policy (/legal/acceptable-use). Not needed once the account has accepted it once before.",
372
+ },
373
+ },
374
+ required: ["htmlContent"],
375
+ },
376
+ },
377
+ {
378
+ name: "publish_raw_landing_page",
379
+ description: `Creates, and publishes to a domain, a landing page from a RAW HTML document you supply directly — the combined create+publish equivalent of create_raw_landing_page. See create_raw_landing_page's description for the unsanitized-content, AUP, and scope caveats (single self-contained HTML document, up to 1MB, no zip/multi-file sites). For drag-and-drop BUILDER pages built from designJson, use publish_landing_page instead — this tool is a different storage mode.`,
380
+ inputSchema: {
381
+ type: "object",
382
+ properties: {
383
+ name: {
384
+ type: "string",
385
+ description: "Title of the landing page (e.g. 'Kicks Store').",
386
+ },
387
+ htmlContent: {
388
+ type: "string",
389
+ description: "The full, self-contained raw HTML document to serve as-is (up to 1MB). Inline or CDN-linked CSS/JS only — no separate local asset files.",
390
+ },
391
+ acceptAup: {
392
+ type: "boolean",
393
+ description: "Pass true ONLY after explicitly telling the user this publishes unsanitized HTML/CSS/JS as-is and getting their confirmation of the Acceptable Use Policy (/legal/acceptable-use). Not needed once the account has accepted it once before.",
394
+ },
395
+ domain: {
396
+ type: "string",
397
+ description: "Subdomain slug (e.g. 'kicks') or custom domain ('kicks.com').",
398
+ },
399
+ type: {
400
+ type: "string",
401
+ enum: ["SUBDOMAIN", "CUSTOM"],
402
+ description: "Domain routing type. Inferred from the domain string if omitted.",
403
+ },
404
+ },
405
+ required: ["htmlContent", "domain"],
406
+ },
407
+ },
324
408
  {
325
409
  name: "publish_existing_landing_page",
326
410
  description: `Links a subdomain or custom domain to an already-existing landing page template — for a template created via create_landing_page, or the home page of a multi-page site (see create_landing_page_subpage) once its sub-pages are ready. Unlike publish_landing_page, this does NOT create a new template — it publishes the one you already have. Every sub-page nested under templateId automatically becomes reachable at this domain too (e.g. domain.com/about) — no separate publish call is needed per sub-page.`,
@@ -346,9 +430,9 @@ Uses the SAME fully-hydrated layout schema as publish_landing_page — see its d
346
430
  },
347
431
  {
348
432
  name: "create_landing_page_subpage",
349
- description: `Adds a new page nested under an existing landing page, reachable at <site domain>/<slug> — or nested deeper (e.g. /blog/post-1) if parentTemplateId is itself a sub-page rather than the home page. This is how a single landing page becomes a multi-page site. No separate publish step is needed for sub-pages: they automatically become reachable once the site's home page has a domain linked (see publish_existing_landing_page). Requires an Ultra subscription plan — sub-pages are otherwise unlimited per site once enabled.
433
+ description: `Adds a new page nested under an existing landing page, reachable at <site domain>/<slug> — or nested deeper (e.g. /blog/post-1) if parentTemplateId is itself a sub-page rather than the home page. This is how a single landing page becomes a multi-page site (BUILDER and RAW_UPLOAD pages can be freely mixed within the same site — each page's own sourceType is independent of its siblings). No separate publish step is needed for sub-pages: they automatically become reachable once the site's home page has a domain linked (see publish_existing_landing_page). Requires an Ultra subscription plan — sub-pages are otherwise unlimited per site once enabled.
350
434
 
351
- The new page starts blank — use update_template with the returned templateId to add content.`,
435
+ Provide htmlContent for a raw-HTML sub-page (same unsanitized/AUP/1MB caveats as create_raw_landing_page). Omit it to create a blank BUILDER page — fill it in afterward with update_template using the returned templateId. Edit an existing sub-page's content afterward with update_template (BUILDER) or update_raw_landing_page (RAW_UPLOAD) depending on which mode it was created with.`,
352
436
  inputSchema: {
353
437
  type: "object",
354
438
  properties: {
@@ -364,6 +448,14 @@ The new page starts blank — use update_template with the returned templateId t
364
448
  type: "string",
365
449
  description: "Optional URL segment (e.g. 'about-us'). Auto-generated from name if omitted; auto-suffixed (about-us-2, ...) if it collides with a sibling page under the same parent.",
366
450
  },
451
+ htmlContent: {
452
+ type: "string",
453
+ description: "Optional. A full, self-contained raw HTML document (up to 1MB) to serve as-is. Creates a RAW_UPLOAD sub-page instead of a blank BUILDER one.",
454
+ },
455
+ acceptAup: {
456
+ type: "boolean",
457
+ description: "Only relevant when htmlContent is given. Pass true ONLY after explicitly telling the user this publishes unsanitized HTML/CSS/JS as-is and getting their confirmation of the Acceptable Use Policy (/legal/acceptable-use). Not needed once the account has accepted it once before.",
458
+ },
367
459
  },
368
460
  required: ["parentTemplateId", "name"],
369
461
  },
@@ -496,6 +588,7 @@ To edit a page's CONTENT (designJson), use update_template with the same templat
496
588
  },
497
589
  },
498
590
  },
591
+ ...blogTools_js_1.BLOG_TOOL_DEFS,
499
592
  ],
500
593
  };
501
594
  });
@@ -560,6 +653,39 @@ server.setRequestHandler(types_js_1.CallToolRequestSchema, async (request) => {
560
653
  ],
561
654
  };
562
655
  }
656
+ case "create_raw_landing_page": {
657
+ const result = await client.createRawLandingPage(args);
658
+ return {
659
+ content: [
660
+ {
661
+ type: "text",
662
+ text: JSON.stringify(result, null, 2),
663
+ },
664
+ ],
665
+ };
666
+ }
667
+ case "publish_raw_landing_page": {
668
+ const result = await client.publishRawLandingPage(args);
669
+ return {
670
+ content: [
671
+ {
672
+ type: "text",
673
+ text: JSON.stringify(result, null, 2),
674
+ },
675
+ ],
676
+ };
677
+ }
678
+ case "update_raw_landing_page": {
679
+ const result = await client.updateRawLandingPage(args);
680
+ return {
681
+ content: [
682
+ {
683
+ type: "text",
684
+ text: JSON.stringify(result, null, 2),
685
+ },
686
+ ],
687
+ };
688
+ }
563
689
  case "publish_existing_landing_page": {
564
690
  const result = await client.publishExistingLandingPage(args);
565
691
  return {
@@ -687,8 +813,20 @@ server.setRequestHandler(types_js_1.CallToolRequestSchema, async (request) => {
687
813
  ],
688
814
  };
689
815
  }
690
- default:
816
+ default: {
817
+ if (blogTools_js_1.BLOG_TOOL_NAMES.has(name)) {
818
+ const result = await (0, blogTools_js_1.handleBlogToolCall)(name, args || {}, client);
819
+ return {
820
+ content: [
821
+ {
822
+ type: "text",
823
+ text: JSON.stringify(result, null, 2),
824
+ },
825
+ ],
826
+ };
827
+ }
691
828
  throw new Error(`Unknown tool: ${name}`);
829
+ }
692
830
  }
693
831
  }
694
832
  catch (error) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@charisol/plexo-mcp",
3
- "version": "1.0.7",
3
+ "version": "1.0.9",
4
4
  "description": "Model Context Protocol (MCP) Server for Plexo - Landing page generation, email templates, publishing, and analytics.",
5
5
  "main": "dist/index.js",
6
6
  "bin": {