@charisol/plexo-mcp 1.0.6 → 1.0.7

package/dist/client/plexoClient.js

@@ -115,6 +115,119 @@ class PlexoClient {
         }
         return data;
     }
+    /**
+     * Creates a landing page template WITHOUT publishing it — a thin wrapper
+     * around the same /api/v1/publish endpoint publishLandingPage() uses,
+     * just never forwarding a domain/type even if the caller passed one, so
+     * this tool's contract ("never publishes") holds regardless of input.
+     */
+    async createLandingPage(params) {
+        return this.publishLandingPage({ name: params.name, designJson: params.designJson });
+    }
+    /**
+     * Links a subdomain or custom domain to an already-existing landing page
+     * template (unlike publishLandingPage, which always creates a new one).
+     * Used both for a plain create_landing_page template and for the home
+     * page of a multi-page site once its sub-pages are ready.
+     */
+    async publishExistingLandingPage(params) {
+        this.checkAuth();
+        const type = params.type || (params.domain.includes(".") ? "CUSTOM" : "SUBDOMAIN");
+        const res = await fetch(`${this.baseUrl}/api/v1/domains`, {
+            method: "POST",
+            headers: this.getHeaders(),
+            body: JSON.stringify({ templateId: params.templateId, domain: params.domain, type }),
+        });
+        const data = (await res.json());
+        if (!res.ok) {
+            throw new Error(data?.error || `Publishing failed with status ${res.status}`);
+        }
+        return data;
+    }
+    /**
+     * Creates a new page nested under an existing landing page (its home page
+     * for a top-level page, or another sub-page's id to nest deeper) — how a
+     * single landing page becomes a multi-page site. Starts blank; use
+     * updateTemplate() with the returned templateId to add content.
+     */
+    async createLandingPageSubpage(params) {
+        this.checkAuth();
+        const res = await fetch(`${this.baseUrl}/api/templates`, {
+            method: "POST",
+            headers: this.getHeaders(),
+            body: JSON.stringify({ name: params.name, parentId: params.parentTemplateId, slug: params.slug }),
+        });
+        const data = (await res.json());
+        if (!res.ok) {
+            throw new Error(data?.error || `Sub-page creation failed with status ${res.status}`);
+        }
+        return data;
+    }
+    /**
+     * Returns every page belonging to the same multi-page site as templateId
+     * — its home page plus all nested sub-pages. templateId can be the home
+     * page or any sub-page; either way the whole tree comes back.
+     */
+    async getLandingPagePages(templateId) {
+        this.checkAuth();
+        const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}/pages`, {
+            method: "GET",
+            headers: this.getHeaders(),
+        });
+        const data = (await res.json());
+        if (!res.ok) {
+            throw new Error(data?.error || `Failed to fetch page tree (Status ${res.status})`);
+        }
+        return data;
+    }
+    /**
+     * Renames a page, changes its URL segment, moves it under a different
+     * parent, or reorders it among siblings. Does not touch page content —
+     * use updateTemplate() for that.
+     */
+    async updateLandingPagePage(params) {
+        this.checkAuth();
+        const { templateId, parentTemplateId, ...rest } = params;
+        const body = { ...rest };
+        if (parentTemplateId !== undefined)
+            body.parentId = parentTemplateId;
+        const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}`, {
+            method: "PATCH",
+            headers: this.getHeaders(),
+            body: JSON.stringify(body),
+        });
+        const data = (await res.json());
+        if (!res.ok) {
+            throw new Error(data?.error || `Page update failed with status ${res.status}`);
+        }
+        return data;
+    }
+    /** Deletes a page. Sub-pages nested under it are cascade-deleted too. */
+    async deleteLandingPagePage(templateId) {
+        this.checkAuth();
+        const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}`, {
+            method: "DELETE",
+            headers: this.getHeaders(),
+        });
+        const data = (await res.json());
+        if (!res.ok) {
+            throw new Error(data?.error || `Page deletion failed with status ${res.status}`);
+        }
+        return data;
+    }
+    /** Clones a sub-page's content into a new sibling page under the same parent. */
+    async duplicateLandingPagePage(templateId) {
+        this.checkAuth();
+        const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}/duplicate`, {
+            method: "POST",
+            headers: this.getHeaders(),
+        });
+        const data = (await res.json());
+        if (!res.ok) {
+            throw new Error(data?.error || `Page duplication failed with status ${res.status}`);
+        }
+        return data;
+    }
     async listTemplates() {
         this.checkAuth();
         const res = await fetch(`${this.baseUrl}/api/templates`, {

package/dist/index.js

@@ -301,6 +301,147 @@ Uses the SAME fully-hydrated layout schema as publish_landing_page/create_email_
                     required: ["templateId", "designJson"],
                 },
             },
+            {
+                name: "create_landing_page",
+                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.
+
+Uses the SAME fully-hydrated layout schema as publish_landing_page — see its description for a full worked example.`,
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        name: {
+                            type: "string",
+                            description: "Title of the landing page (e.g. 'Kicks Store').",
+                        },
+                        designJson: {
+                            type: "object",
+                            description: "Plexo layout schema object — same shape as publish_landing_page's designJson.",
+                        },
+                    },
+                    required: ["designJson"],
+                },
+            },
+            {
+                name: "publish_existing_landing_page",
+                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.`,
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        templateId: {
+                            type: "string",
+                            description: "ID of an existing landing page template to publish — must be a home page (no parent), not a sub-page.",
+                        },
+                        domain: {
+                            type: "string",
+                            description: "Subdomain slug (e.g. 'kicks') or custom domain ('kicks.com').",
+                        },
+                        type: {
+                            type: "string",
+                            enum: ["SUBDOMAIN", "CUSTOM"],
+                            description: "Domain routing type. Inferred from the domain string if omitted.",
+                        },
+                    },
+                    required: ["templateId", "domain"],
+                },
+            },
+            {
+                name: "create_landing_page_subpage",
+                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.
+
+The new page starts blank — use update_template with the returned templateId to add content.`,
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        parentTemplateId: {
+                            type: "string",
+                            description: "ID of the page this new page should be nested under — the site's home page for a top-level page (e.g. /about), or another sub-page's ID to nest deeper (e.g. a 'Blog' page's ID to create /blog/post-1).",
+                        },
+                        name: {
+                            type: "string",
+                            description: "Friendly name of the page (e.g. 'About Us').",
+                        },
+                        slug: {
+                            type: "string",
+                            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.",
+                        },
+                    },
+                    required: ["parentTemplateId", "name"],
+                },
+            },
+            {
+                name: "get_landing_page_pages",
+                description: "Returns every page belonging to the same multi-page site as the given template — its home page plus all nested sub-pages, each with its name, URL segment (slug), parent, and full resolved path (e.g. '/blog/post-1'). Pass the home page's ID or any sub-page's ID — either way you get the whole tree back. Use this before create_landing_page_subpage/update_landing_page_page when you need to know what pages already exist or what a page's current slug/parent is.",
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        templateId: {
+                            type: "string",
+                            description: "ID of the site's home page, or any sub-page within it.",
+                        },
+                    },
+                    required: ["templateId"],
+                },
+            },
+            {
+                name: "update_landing_page_page",
+                description: `Renames a page, changes its URL segment (slug), moves it under a different parent page, or reorders it among its siblings. The home page of a site (no parent) can be renamed but has no slug of its own and can't be re-parented — use publish_existing_landing_page to manage its domain instead.
+
+To edit a page's CONTENT (designJson), use update_template with the same templateId instead — this tool only manages the page's place in the site's structure, not what's on it.`,
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        templateId: {
+                            type: "string",
+                            description: "ID of the page to update.",
+                        },
+                        name: {
+                            type: "string",
+                            description: "Optional new name.",
+                        },
+                        slug: {
+                            type: "string",
+                            description: "Optional new URL segment. Not allowed for the home page.",
+                        },
+                        parentTemplateId: {
+                            type: "string",
+                            description: "Optional new parent page ID, to move this page elsewhere in the site's tree. Rejected if it would create a cycle (e.g. moving a page underneath its own sub-page).",
+                        },
+                        order: {
+                            type: "number",
+                            description: "Optional sort position among sibling pages under the same parent (lower = earlier).",
+                        },
+                    },
+                    required: ["templateId"],
+                },
+            },
+            {
+                name: "delete_landing_page_page",
+                description: "Deletes a page. If it has sub-pages nested under it, they're deleted too (cascade) — the response reports how many. Deleting a site's home page deletes the whole site, including every page nested under it and its published domain link — this can't be undone, confirm with the user first.",
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        templateId: {
+                            type: "string",
+                            description: "ID of the page to delete.",
+                        },
+                    },
+                    required: ["templateId"],
+                },
+            },
+            {
+                name: "duplicate_landing_page_page",
+                description: "Clones a sub-page's content into a new sibling page under the same parent — handy for building several similar pages (e.g. multiple product pages) without starting blank. Not available for a site's home page. Requires an Ultra subscription plan.",
+                inputSchema: {
+                    type: "object",
+                    properties: {
+                        templateId: {
+                            type: "string",
+                            description: "ID of the sub-page to duplicate — must not be a home page.",
+                        },
+                    },
+                    required: ["templateId"],
+                },
+            },
             {
                 name: "list_landing_pages",
                 description: "Lists all saved landing page templates and published domain URLs in the user's Plexo account.",
@@ -408,6 +549,83 @@ server.setRequestHandler(types_js_1.CallToolRequestSchema, async (request) => {
                     ],
                 };
             }
+            case "create_landing_page": {
+                const result = await client.createLandingPage(args);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
+            case "publish_existing_landing_page": {
+                const result = await client.publishExistingLandingPage(args);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
+            case "create_landing_page_subpage": {
+                const result = await client.createLandingPageSubpage(args);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
+            case "get_landing_page_pages": {
+                const result = await client.getLandingPagePages(args?.templateId);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
+            case "update_landing_page_page": {
+                const result = await client.updateLandingPagePage(args);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
+            case "delete_landing_page_page": {
+                const result = await client.deleteLandingPagePage(args?.templateId);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
+            case "duplicate_landing_page_page": {
+                const result = await client.duplicateLandingPagePage(args?.templateId);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: JSON.stringify(result, null, 2),
+                        },
+                    ],
+                };
+            }
             case "list_landing_pages": {
                 const data = await client.listTemplates();
                 const landingPages = (data.templates || []).filter((t) => t.kind === "LANDING_PAGE");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@charisol/plexo-mcp",
-  "version": "1.0.6",
+  "version": "1.0.7",
   "description": "Model Context Protocol (MCP) Server for Plexo - Landing page generation, email templates, publishing, and analytics.",
   "main": "dist/index.js",
   "bin": {

package/src/client/plexoClient.ts

@@ -156,6 +156,152 @@ export class PlexoClient {
     return data;
   }
 
+  /**
+   * Creates a landing page template WITHOUT publishing it — a thin wrapper
+   * around the same /api/v1/publish endpoint publishLandingPage() uses,
+   * just never forwarding a domain/type even if the caller passed one, so
+   * this tool's contract ("never publishes") holds regardless of input.
+   */
+  async createLandingPage(params: { name?: string; designJson: Record<string, any> }): Promise<any> {
+    return this.publishLandingPage({ name: params.name, designJson: params.designJson });
+  }
+
+  /**
+   * Links a subdomain or custom domain to an already-existing landing page
+   * template (unlike publishLandingPage, which always creates a new one).
+   * Used both for a plain create_landing_page template and for the home
+   * page of a multi-page site once its sub-pages are ready.
+   */
+  async publishExistingLandingPage(params: {
+    templateId: string;
+    domain: string;
+    type?: "SUBDOMAIN" | "CUSTOM";
+  }): Promise<any> {
+    this.checkAuth();
+    const type = params.type || (params.domain.includes(".") ? "CUSTOM" : "SUBDOMAIN");
+    const res = await fetch(`${this.baseUrl}/api/v1/domains`, {
+      method: "POST",
+      headers: this.getHeaders(),
+      body: JSON.stringify({ templateId: params.templateId, domain: params.domain, type }),
+    });
+
+    const data = (await res.json()) as any;
+    if (!res.ok) {
+      throw new Error(data?.error || `Publishing failed with status ${res.status}`);
+    }
+
+    return data;
+  }
+
+  /**
+   * Creates a new page nested under an existing landing page (its home page
+   * for a top-level page, or another sub-page's id to nest deeper) — how a
+   * single landing page becomes a multi-page site. Starts blank; use
+   * updateTemplate() with the returned templateId to add content.
+   */
+  async createLandingPageSubpage(params: {
+    parentTemplateId: string;
+    name: string;
+    slug?: string;
+  }): Promise<any> {
+    this.checkAuth();
+    const res = await fetch(`${this.baseUrl}/api/templates`, {
+      method: "POST",
+      headers: this.getHeaders(),
+      body: JSON.stringify({ name: params.name, parentId: params.parentTemplateId, slug: params.slug }),
+    });
+
+    const data = (await res.json()) as any;
+    if (!res.ok) {
+      throw new Error(data?.error || `Sub-page creation failed with status ${res.status}`);
+    }
+
+    return data;
+  }
+
+  /**
+   * Returns every page belonging to the same multi-page site as templateId
+   * — its home page plus all nested sub-pages. templateId can be the home
+   * page or any sub-page; either way the whole tree comes back.
+   */
+  async getLandingPagePages(templateId: string): Promise<any> {
+    this.checkAuth();
+    const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}/pages`, {
+      method: "GET",
+      headers: this.getHeaders(),
+    });
+
+    const data = (await res.json()) as any;
+    if (!res.ok) {
+      throw new Error(data?.error || `Failed to fetch page tree (Status ${res.status})`);
+    }
+
+    return data;
+  }
+
+  /**
+   * Renames a page, changes its URL segment, moves it under a different
+   * parent, or reorders it among siblings. Does not touch page content —
+   * use updateTemplate() for that.
+   */
+  async updateLandingPagePage(params: {
+    templateId: string;
+    name?: string;
+    slug?: string;
+    parentTemplateId?: string;
+    order?: number;
+  }): Promise<any> {
+    this.checkAuth();
+    const { templateId, parentTemplateId, ...rest } = params;
+    const body: Record<string, any> = { ...rest };
+    if (parentTemplateId !== undefined) body.parentId = parentTemplateId;
+
+    const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}`, {
+      method: "PATCH",
+      headers: this.getHeaders(),
+      body: JSON.stringify(body),
+    });
+
+    const data = (await res.json()) as any;
+    if (!res.ok) {
+      throw new Error(data?.error || `Page update failed with status ${res.status}`);
+    }
+
+    return data;
+  }
+
+  /** Deletes a page. Sub-pages nested under it are cascade-deleted too. */
+  async deleteLandingPagePage(templateId: string): Promise<any> {
+    this.checkAuth();
+    const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}`, {
+      method: "DELETE",
+      headers: this.getHeaders(),
+    });
+
+    const data = (await res.json()) as any;
+    if (!res.ok) {
+      throw new Error(data?.error || `Page deletion failed with status ${res.status}`);
+    }
+
+    return data;
+  }
+
+  /** Clones a sub-page's content into a new sibling page under the same parent. */
+  async duplicateLandingPagePage(templateId: string): Promise<any> {
+    this.checkAuth();
+    const res = await fetch(`${this.baseUrl}/api/templates/${encodeURIComponent(templateId)}/duplicate`, {
+      method: "POST",
+      headers: this.getHeaders(),
+    });
+
+    const data = (await res.json()) as any;
+    if (!res.ok) {
+      throw new Error(data?.error || `Page duplication failed with status ${res.status}`);
+    }
+
+    return data;
+  }
+
   async listTemplates(): Promise<any> {
     this.checkAuth();
     const res = await fetch(`${this.baseUrl}/api/templates`, {

package/src/index.ts

@@ -308,6 +308,147 @@ Uses the SAME fully-hydrated layout schema as publish_landing_page/create_email_
           required: ["templateId", "designJson"],
         },
       },
+      {
+        name: "create_landing_page",
+        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.
+
+Uses the SAME fully-hydrated layout schema as publish_landing_page — see its description for a full worked example.`,
+        inputSchema: {
+          type: "object",
+          properties: {
+            name: {
+              type: "string",
+              description: "Title of the landing page (e.g. 'Kicks Store').",
+            },
+            designJson: {
+              type: "object",
+              description: "Plexo layout schema object — same shape as publish_landing_page's designJson.",
+            },
+          },
+          required: ["designJson"],
+        },
+      },
+      {
+        name: "publish_existing_landing_page",
+        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.`,
+        inputSchema: {
+          type: "object",
+          properties: {
+            templateId: {
+              type: "string",
+              description: "ID of an existing landing page template to publish — must be a home page (no parent), not a sub-page.",
+            },
+            domain: {
+              type: "string",
+              description: "Subdomain slug (e.g. 'kicks') or custom domain ('kicks.com').",
+            },
+            type: {
+              type: "string",
+              enum: ["SUBDOMAIN", "CUSTOM"],
+              description: "Domain routing type. Inferred from the domain string if omitted.",
+            },
+          },
+          required: ["templateId", "domain"],
+        },
+      },
+      {
+        name: "create_landing_page_subpage",
+        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.
+
+The new page starts blank — use update_template with the returned templateId to add content.`,
+        inputSchema: {
+          type: "object",
+          properties: {
+            parentTemplateId: {
+              type: "string",
+              description: "ID of the page this new page should be nested under — the site's home page for a top-level page (e.g. /about), or another sub-page's ID to nest deeper (e.g. a 'Blog' page's ID to create /blog/post-1).",
+            },
+            name: {
+              type: "string",
+              description: "Friendly name of the page (e.g. 'About Us').",
+            },
+            slug: {
+              type: "string",
+              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.",
+            },
+          },
+          required: ["parentTemplateId", "name"],
+        },
+      },
+      {
+        name: "get_landing_page_pages",
+        description: "Returns every page belonging to the same multi-page site as the given template — its home page plus all nested sub-pages, each with its name, URL segment (slug), parent, and full resolved path (e.g. '/blog/post-1'). Pass the home page's ID or any sub-page's ID — either way you get the whole tree back. Use this before create_landing_page_subpage/update_landing_page_page when you need to know what pages already exist or what a page's current slug/parent is.",
+        inputSchema: {
+          type: "object",
+          properties: {
+            templateId: {
+              type: "string",
+              description: "ID of the site's home page, or any sub-page within it.",
+            },
+          },
+          required: ["templateId"],
+        },
+      },
+      {
+        name: "update_landing_page_page",
+        description: `Renames a page, changes its URL segment (slug), moves it under a different parent page, or reorders it among its siblings. The home page of a site (no parent) can be renamed but has no slug of its own and can't be re-parented — use publish_existing_landing_page to manage its domain instead.
+
+To edit a page's CONTENT (designJson), use update_template with the same templateId instead — this tool only manages the page's place in the site's structure, not what's on it.`,
+        inputSchema: {
+          type: "object",
+          properties: {
+            templateId: {
+              type: "string",
+              description: "ID of the page to update.",
+            },
+            name: {
+              type: "string",
+              description: "Optional new name.",
+            },
+            slug: {
+              type: "string",
+              description: "Optional new URL segment. Not allowed for the home page.",
+            },
+            parentTemplateId: {
+              type: "string",
+              description: "Optional new parent page ID, to move this page elsewhere in the site's tree. Rejected if it would create a cycle (e.g. moving a page underneath its own sub-page).",
+            },
+            order: {
+              type: "number",
+              description: "Optional sort position among sibling pages under the same parent (lower = earlier).",
+            },
+          },
+          required: ["templateId"],
+        },
+      },
+      {
+        name: "delete_landing_page_page",
+        description: "Deletes a page. If it has sub-pages nested under it, they're deleted too (cascade) — the response reports how many. Deleting a site's home page deletes the whole site, including every page nested under it and its published domain link — this can't be undone, confirm with the user first.",
+        inputSchema: {
+          type: "object",
+          properties: {
+            templateId: {
+              type: "string",
+              description: "ID of the page to delete.",
+            },
+          },
+          required: ["templateId"],
+        },
+      },
+      {
+        name: "duplicate_landing_page_page",
+        description: "Clones a sub-page's content into a new sibling page under the same parent — handy for building several similar pages (e.g. multiple product pages) without starting blank. Not available for a site's home page. Requires an Ultra subscription plan.",
+        inputSchema: {
+          type: "object",
+          properties: {
+            templateId: {
+              type: "string",
+              description: "ID of the sub-page to duplicate — must not be a home page.",
+            },
+          },
+          required: ["templateId"],
+        },
+      },
       {
         name: "list_landing_pages",
         description: "Lists all saved landing page templates and published domain URLs in the user's Plexo account.",
@@ -421,6 +562,90 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
         };
       }
 
+      case "create_landing_page": {
+        const result = await client.createLandingPage(args as any);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
+      case "publish_existing_landing_page": {
+        const result = await client.publishExistingLandingPage(args as any);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
+      case "create_landing_page_subpage": {
+        const result = await client.createLandingPageSubpage(args as any);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
+      case "get_landing_page_pages": {
+        const result = await client.getLandingPagePages((args as any)?.templateId);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
+      case "update_landing_page_page": {
+        const result = await client.updateLandingPagePage(args as any);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
+      case "delete_landing_page_page": {
+        const result = await client.deleteLandingPagePage((args as any)?.templateId);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
+      case "duplicate_landing_page_page": {
+        const result = await client.duplicateLandingPagePage((args as any)?.templateId);
+        return {
+          content: [
+            {
+              type: "text",
+              text: JSON.stringify(result, null, 2),
+            },
+          ],
+        };
+      }
+
       case "list_landing_pages": {
         const data = await client.listTemplates();
         const landingPages = (data.templates || []).filter(