@content-island/mcp 0.1.0 → 0.1.2

package/dist/index.js

@@ -1,31 +1,31 @@
-import { z as n } from "zod";
-import { McpServer as c } from "@modelcontextprotocol/sdk/server/mcp.js";
-import { createClient as d } from "@content-island/api-client";
-import { StdioServerTransport as p } from "@modelcontextprotocol/sdk/server/stdio.js";
-const i = {
+import { z as o } from "zod";
+import { McpServer as l } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { createClient as p } from "@content-island/api-client";
+import { StdioServerTransport as d } from "@modelcontextprotocol/sdk/server/stdio.js";
+const r = {
   CONTENT_ISLAND_ACCESS_TOKEN: process.env.CONTENT_ISLAND_ACCESS_TOKEN,
-  CONTENT_ISLAND_DOMAIN: process.env.CONTENT_ISLAND_DOMAIN || void 0,
+  CONTENT_ISLAND_DOMAIN: process.env.CONTENT_ISLAND_DOMAIN,
   CONTENT_ISLAND_SECURE_PROTOCOL: process.env.CONTENT_ISLAND_SECURE_PROTOCOL !== "false",
-  CONTENT_ISLAND_API_VERSION: process.env.CONTENT_ISLAND_API_VERSION || void 0
-}, g = "0.1.0", u = {
-  version: g
-}, r = new c({
+  CONTENT_ISLAND_API_VERSION: process.env.CONTENT_ISLAND_API_VERSION
+}, u = "0.1.2", g = {
+  version: u
+}, s = new l({
   name: "Content Island",
-  version: u.version
+  version: g.version
 }), m = () => {
-  r.prompt(
+  s.prompt(
     "create-content-island-project",
     "Professional MCP Server prompt for creating modern frontend projects integrated with Content Island CMS",
     {
-      framework: n.string().describe("Framework choice (Next.js, Astro, Nuxt, etc.)"),
-      pages: n.string().describe("Pages needed (Homepage, Blog, Contact, etc.)"),
-      location: n.string().describe("Project location (root directory or subfolder name)"),
-      styling: n.string().describe("Styling preference (Tailwind CSS or custom)"),
-      design: n.string().describe("Design assets (mockups, wireframes, or none)")
+      framework: o.string().describe("Framework choice (Next.js, Astro, Nuxt, etc.)"),
+      pages: o.string().describe("Pages needed (Homepage, Blog, Contact, etc.)"),
+      location: o.string().describe("Project location (root directory or subfolder name)"),
+      styling: o.string().describe("Styling preference (Tailwind CSS or custom)"),
+      design: o.string().describe("Design assets (mockups, wireframes, or none)")
     },
-    async (l) => {
-      const { framework: e, pages: o, location: s, styling: t, design: a } = l;
-      return e && o && s && t && a ? {
+    async (c) => {
+      const { framework: e, pages: i, location: t, styling: n, design: a } = c;
+      return e && i && t && n && a ? {
         description: "Content Island project generator",
         messages: [
           {
@@ -38,9 +38,9 @@ I'll create a professional ${e} application integrated with your Content Island
 
 **Configuration:**
 - Framework: **${e}**
-- Pages: ${o}
-- Location: ${s}
-- Styling: ${t}
+- Pages: ${i}
+- Location: ${t}
+- Styling: ${n}
 - Design: ${a}
 
 # CRITICAL IMPLEMENTATION INSTRUCTIONS - FOLLOW EXACTLY
@@ -49,13 +49,20 @@ You are a specialized web development assistant creating a ${e} application inte
 
 ## MANDATORY EXECUTION SEQUENCE - NO EXCEPTIONS
 
-### STEP 1: DATA RETRIEVAL (REQUIRED FIRST ACTION)
-- You MUST call the 'get-content-island-project' tool as your FIRST action
+### STEP 1: FRAMEWORK PROJECT INITIALIZATION (REQUIRED FIRST ACTION)
+- FIRST execute the appropriate framework CLI command to create the base project:
+${e === "Next.js" ? `  * Run: npx create-next-app@latest ${t !== "root directory" ? t : "."} --typescript --tailwind --eslint --app --src-dir --import-alias "@/*"` : e === "Nuxt" ? `  * Run: npx nuxi@latest init ${t !== "root directory" ? t : "."}` : e === "Astro" ? `  * Run: npm create astro@latest ${t !== "root directory" ? t : "."}` : e === "SvelteKit" ? `  * Run: npm create svelte@latest ${t !== "root directory" ? t : "."}` : e === "Vite" ? `  * Run: npm create vite@latest ${t !== "root directory" ? t : "."} -- --template react-ts` : `  * Run the appropriate CLI command for ${e} to create a new project in ${t !== "root directory" ? t : "current directory"}`}
+- Navigate to the project directory if created in a subfolder
+- Wait for the framework setup to complete before proceeding
+- DO NOT skip this step - the framework base is required for all subsequent steps
+
+### STEP 2: DATA RETRIEVAL (REQUIRED SECOND ACTION)
+- You MUST call the 'get-content-island-project' tool as your SECOND action
 - DO NOT proceed with ANY code generation until you have the project structure
 - Parse the returned JSON to extract: project languages, content types, and field definitions
 - If the tool fails, STOP and ask user to check their Content Island configuration
 
-### STEP 2: PACKAGE INSTALLATION (MANDATORY BEFORE CODE GENERATION)
+### STEP 3: PACKAGE INSTALLATION (MANDATORY BEFORE CODE GENERATION)
 ${e === "Nuxt" ? `
 - FIRST install the official Content Island packages:
   * npm install @content-island/nuxt@latest
@@ -70,7 +77,7 @@ ${e === "Nuxt" ? `
 - NEVER create custom API implementations
 - NEVER invent API methods that don't exist
 
-### STEP 3: TYPESCRIPT INTERFACE GENERATION (EXACT MAPPING REQUIRED)
+### STEP 4: TYPESCRIPT INTERFACE GENERATION (EXACT MAPPING REQUIRED)
 - Import Media type from '@content-island/api-client' if needed: import type { Media } from '@content-island/api-client'
 - Generate TypeScript interfaces using EXACTLY the structure returned by the tool
 - For EACH content type in the project data, create ONE interface
@@ -89,7 +96,7 @@ ${e === "Nuxt" ? `
   Field: {"name": "title", "type": "short-text", "tsType": "string", "isArray": false, "isRequired": true}
   Result: title: string;
 
-### STEP 4: API CLIENT IMPLEMENTATION (DOCUMENTED METHODS ONLY)
+### STEP 5: API CLIENT IMPLEMENTATION (DOCUMENTED METHODS ONLY)
 ${e === "Nuxt" ? `
 - Use Nuxt Content Island composables from '@content-island/nuxt'
 - Configure the module in nuxt.config.ts with your project settings
@@ -124,11 +131,11 @@ ${e === "Nuxt" ? `
 - Always include language parameter support for multi-language projects
 
 
-### STEP 5: PROJECT STRUCTURE GENERATION (FRAMEWORK-SPECIFIC)
+### STEP 6: PROJECT STRUCTURE GENERATION (FRAMEWORK-SPECIFIC)
 - Framework: ${e}
-- Location: ${s}
-- Pages requested: ${o}
-- Styling: ${t}
+- Location: ${t}
+- Pages requested: ${i}
+- Styling: ${n}
 - Design approach: ${a}
 
 #### FRAMEWORK-SPECIFIC REQUIREMENTS:
@@ -154,7 +161,7 @@ ${e === "Nuxt" ? `
 - Implement proper SEO with useHead
 ` : ""}
 
-### STEP 6: ENVIRONMENT CONFIGURATION (MANDATORY FILES)
+### STEP 7: ENVIRONMENT CONFIGURATION (MANDATORY FILES)
 ${e === "Nuxt" ? `
 - Configure Content Island in nuxt.config.ts:
   runtimeConfig: {
@@ -169,21 +176,21 @@ ${e === "Nuxt" ? `
 - Add .env to .gitignore if not present
 - Document environment setup in README.md
 
-### STEP 7: STYLING IMPLEMENTATION
-${t.toLowerCase().includes("tailwind") ? `
+### STEP 8: STYLING IMPLEMENTATION
+${n.toLowerCase().includes("tailwind") ? `
 - Install and configure Tailwind CSS according to ${e} official documentation
 - Create tailwind.config.js with proper content paths
 - Add Tailwind directives to main CSS file
 - Implement responsive design classes (sm:, md:, lg:, xl:)
 - Use Tailwind accessibility classes for WCAG compliance
 ` : `
-- Implement ${t} according to ${e} best practices
+- Implement ${n} according to ${e} best practices
 - Create modular CSS structure
 - Implement responsive design with media queries
 - Ensure accessibility with proper contrast and focus states
 `}
 
-### STEP 8: ERROR HANDLING & UX (NON-NEGOTIABLE REQUIREMENTS)
+### STEP 9: ERROR HANDLING & UX (NON-NEGOTIABLE REQUIREMENTS)
 - Implement loading states for ALL data fetching operations
 - Create error boundaries/components for content display failures
 - Add try-catch blocks around ALL API calls
@@ -192,14 +199,14 @@ ${t.toLowerCase().includes("tailwind") ? `
 - Show user-friendly error messages (no technical details to users)
 - Implement 404 pages for missing content
 
-### STEP 9: PERFORMANCE OPTIMIZATION (MANDATORY)
+### STEP 10: PERFORMANCE OPTIMIZATION (MANDATORY)
 - Implement lazy loading for images using framework-specific solutions
 - Use proper code splitting for JavaScript bundles
 - Optimize bundle sizes with tree shaking
 - Implement appropriate caching strategies for API responses
 - Use efficient data fetching patterns (avoid unnecessary re-renders)
 
-### STEP 10: ACCESSIBILITY & SEO (WCAG COMPLIANCE REQUIRED)
+### STEP 11: ACCESSIBILITY & SEO (WCAG COMPLIANCE REQUIRED)
 - Use semantic HTML elements (header, nav, main, section, article, footer)
 - Implement proper heading hierarchy (h1, h2, h3...)
 - Add alt attributes to ALL images
@@ -209,7 +216,7 @@ ${t.toLowerCase().includes("tailwind") ? `
 - Generate proper meta tags for SEO (title, description, og tags)
 - Implement structured data where appropriate
 
-### STEP 11: INTERNATIONALIZATION (IF APPLICABLE)
+### STEP 12: INTERNATIONALIZATION (IF APPLICABLE)
 - If project.languages contains multiple languages:
   * Implement language detection based on URL or user preference
   * Create language switching functionality
@@ -217,7 +224,7 @@ ${t.toLowerCase().includes("tailwind") ? `
   * Add fallbacks for unavailable translations
   * Show appropriate messages when content not available in selected language
 
-### STEP 12: DOCUMENTATION GENERATION (COMPREHENSIVE REQUIRED)
+### STEP 13: DOCUMENTATION GENERATION (COMPREHENSIVE REQUIRED)
 - Create README.md with:
   * Project title and description
   * Prerequisites (Node.js version, package manager)
@@ -234,18 +241,19 @@ ${t.toLowerCase().includes("tailwind") ? `
 
 1. NEVER invent Content Island API methods not documented
 2. NEVER create example/dummy interfaces - use ONLY project structure data
-3. NEVER proceed without calling get-content-island-project tool first
+3. NEVER proceed without executing framework CLI first and calling get-content-island-project tool second
 4. NEVER skip installing the correct Content Island packages (${e === "Nuxt" ? "@content-island/nuxt@latest and @content-island/api-client@latest" : "@content-island/api-client@latest"})
 5. NEVER skip error handling implementation
 6. NEVER ignore accessibility requirements
 7. NEVER use deprecated framework patterns
 8. NEVER hardcode content - fetch from Content Island API
 9. NEVER create TypeScript interfaces that don't match exact project structure
-10. NEVER skip any of the 12 implementation steps
+10. NEVER skip any of the 13 implementation steps
 11. NEVER assume functionality exists without documentation
 12. NEVER create custom API clients when official one exists
 
 ## VALIDATION CHECKLIST - VERIFY BEFORE COMPLETION:
+□ Framework CLI executed to create base project structure
 □ get-content-island-project tool called and data parsed
 ${e === "Nuxt" ? `
 □ @content-island/nuxt@latest and @content-island/api-client@latest installed
@@ -258,7 +266,7 @@ ${e === "Nuxt" ? `
 □ All content types have corresponding API functions using official client
 `}
 □ TypeScript interfaces exactly match project structure
-□ All requested pages (${o}) are implemented
+□ All requested pages (${i}) are implemented
 □ Error handling implemented for all API calls
 □ Loading states implemented for all data fetching
 □ Responsive design implemented
@@ -270,7 +278,7 @@ ${e === "Nuxt" ? `
 
 FAILURE TO FOLLOW ANY OF THESE INSTRUCTIONS IS UNACCEPTABLE. DOUBLE-CHECK EVERY REQUIREMENT.
 
-Let me start by getting your Content Island project details...`
+Let me start by creating the framework project and then getting your Content Island project details...`
             }
           }
         ]
@@ -307,12 +315,12 @@ Please provide all this information so I can create your project.`
 }, E = () => {
   m();
 }, f = () => {
-  r.tool("get-content-island-project", "Get the user's Content Island project details", async () => {
-    const e = await d({
-      accessToken: i.CONTENT_ISLAND_ACCESS_TOKEN,
-      domain: i.CONTENT_ISLAND_DOMAIN,
-      secureProtocol: i.CONTENT_ISLAND_SECURE_PROTOCOL,
-      apiVersion: i.CONTENT_ISLAND_API_VERSION
+  s.tool("get-content-island-project", "Get the user's Content Island project details", async () => {
+    const e = await p({
+      accessToken: r.CONTENT_ISLAND_ACCESS_TOKEN,
+      domain: r.CONTENT_ISLAND_DOMAIN,
+      secureProtocol: r.CONTENT_ISLAND_SECURE_PROTOCOL,
+      apiVersion: r.CONTENT_ISLAND_API_VERSION
     }).getProject();
     return {
       content: [{ type: "text", text: JSON.stringify(e, null, 2) }]
@@ -323,5 +331,5 @@ Please provide all this information so I can create your project.`
 };
 E();
 I();
-const N = new p();
-await r.connect(N);
+const N = new d();
+await s.connect(N);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@content-island/mcp",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Content Island - MCP (Model Context Protocol) server",
   "private": false,
   "sideEffects": false,