update xmcp to v0.5.0 (#1221)

### Description
xmcp now features prompts on its latest release, would be great to bump
to v0.2 so it initializes with it by default

### Type of Change

- [ ] New Example
- [X] Example updates (Bug fixes, new features, etc.)
- [ ] Other (changes to the codebase, but not to examples)

Author: valebearzotti

framework-boilerplates/xmcp/.gitignore

@@ -3,4 +3,5 @@ node_modules/
 .vercel
 dist
 .xmcp
-xmcp-env.d.ts
+xmcp-env.d.ts
+.env

framework-boilerplates/xmcp/README.md

@@ -18,39 +18,90 @@ This will start the MCP server with the selected transport method.
 
 ## Project Structure
 
-This project uses the structured approach where tools are automatically discovered from the `src/tools` directory. Each tool is defined in its own file with the following structure:
+This project uses the structured approach where tools, prompts, and resources are automatically discovered from their respective directories:
+
+- `src/tools` - Tool definitions
+- `src/prompts` - Prompt templates
+- `src/resources` - Resource handlers
+
+### Tools
+
+Each tool is defined in its own file with the following structure:
 
 ```typescript
-import { z } from 'zod'
-import { type InferSchema } from 'xmcp'
+import { z } from "zod";
+import { type InferSchema, type ToolMetadata } from "xmcp";
 
-// Define the schema for tool parameters
 export const schema = {
-  a: z.number().describe('First number to add'),
-  b: z.number().describe('Second number to add'),
-}
+  name: z.string().describe("The name of the user to greet"),
+};
 
-// Define tool metadata
-export const metadata = {
-  name: 'add',
-  description: 'Add two numbers together',
+export const metadata: ToolMetadata = {
+  name: "greet",
+  description: "Greet the user",
   annotations: {
-    title: 'Add Two Numbers',
+    title: "Greet the user",
     readOnlyHint: true,
     destructiveHint: false,
     idempotentHint: true,
   },
+};
+
+export default function greet({ name }: InferSchema<typeof schema>) {
+  return `Hello, ${name}!`;
+}
+```
+
+### Prompts
+
+Prompts are template definitions for AI interactions:
+
+```typescript
+import { z } from "zod";
+import { type InferSchema, type PromptMetadata } from "xmcp";
+
+export const schema = {
+  code: z.string().describe("The code to review"),
+};
+
+export const metadata: PromptMetadata = {
+  name: "review-code",
+  title: "Review Code",
+  description: "Review code for best practices and potential issues",
+  role: "user",
+};
+
+export default function reviewCode({ code }: InferSchema<typeof schema>) {
+  return `Please review this code: ${code}`;
 }
+```
+
+### Resources
+
+Resources provide data or content with URI-based access:
+
+```typescript
+import { z } from "zod";
+import { type ResourceMetadata, type InferSchema } from "xmcp";
 
-// Tool implementation
-export default async function add({ a, b }: InferSchema<typeof schema>) {
-  return {
-    content: [{ type: 'text', text: String(a + b) }],
-  }
+export const schema = {
+  userId: z.string().describe("The ID of the user"),
+};
+
+export const metadata: ResourceMetadata = {
+  name: "user-profile",
+  title: "User Profile",
+  description: "User profile information",
+};
+
+export default function handler({ userId }: InferSchema<typeof schema>) {
+  return `Profile data for user ${userId}`;
 }
 ```
 
-## Adding New Tools
+## Adding New Components
+
+### Adding New Tools
 
 To add a new tool:
 
@@ -59,6 +110,25 @@ To add a new tool:
 3. Export a `metadata` object with tool information
 4. Export a default function that implements the tool logic
 
+### Adding New Prompts
+
+To add a new prompt:
+
+1. Create a new `.ts` file in the `src/prompts` directory
+2. Export a `schema` object defining the prompt parameters using Zod
+3. Export a `metadata` object with prompt information and role
+4. Export a default function that returns the prompt text
+
+### Adding New Resources
+
+To add a new resource:
+
+1. Create a new `.ts` file in the `src/resources` directory
+2. Use folder structure to define the URI (e.g., `(users)/[userId]/profile.ts` → `users://{userId}/profile`)
+3. Export a `schema` object for dynamic parameters (optional for static resources)
+4. Export a `metadata` object with resource information
+5. Export a default function that returns the resource content
+
 ## Building for Production
 
 To build your project for production:
@@ -80,17 +150,27 @@ You can run the server for the transport built with:
 - HTTP: `node dist/http.js`
 - STDIO: `node dist/stdio.js`
 
-Alternatively, you can use the script which will automatically start the appropriate transport based on your project configuration:
+Given the selected transport method, you will have a custom start script added to the `package.json` file.
 
-```
-npm run start
+For HTTP:
+
+```bash
+npm run start-http
 # or
-yarn start
+yarn start-http
 # or
-pnpm start
+pnpm start-http
 ```
 
-The start script will automatically run either the HTTP or STDIO transport depending on which transport method was selected when you initialized the project.
+For STDIO:
+
+```bash
+npm run start-stdio
+# or
+yarn start-stdio
+# or
+pnpm start-stdio
+```
 
 ## Learn More
 

framework-boilerplates/xmcp/package.json

@@ -1,7 +1,7 @@
 {
   "name": "xmcp-demo",
   "version": "0.1.0",
-  "description": "An xmcp application with tool syntax",
+  "description": "An xmcp demo server with tool syntax",
   "engines": {
     "node": "22.x"
   },
@@ -11,10 +11,7 @@
     "start": "node dist/http.js"
   },
   "dependencies": {
-    "xmcp": "^0.1.11",
+    "xmcp": "^0.5.0",
     "zod": "3.24.4"
-  },
-  "devDependencies": {
-    "swc-loader": "^0.2.6"
   }
 }