[Fleet Execution] [MCP Plan Generation Example]

[davideast]

Goal Reference

This issue was generated from .fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.

Objective

Create an example demonstrating how to build a custom MCP server that helps a coding agent create a highly detailed plan (with reference implementation, build/test commands, verification checks) which is then used as a prompt to create a new Jules session.

Code-Level Diagnosis

Code path: packages/core/examples/mcp-plan-generation/
Mechanism: The packages/core/examples/mcp-plan-generation/ directory and its corresponding examples are entirely missing.
Root cause: The SDK lacks a runnable, practical example of using MCP to generate plans for Jules sessions.

Current Implementation

// Missing example

Proposed Implementation

Files to modify: Create packages/core/examples/mcp-plan-generation/index.ts (or relevant files) and packages/core/examples/mcp-plan-generation/README.md. Update packages/core/README.md to link to the new example.

Integration (Before -> After)

--- a/packages/core/README.md
+++ b/packages/core/README.md
@@ -10,6 +10,7 @@
 Orchestrate complex, long-running coding tasks to an ephemeral cloud environment integrated with a GitHub repo.
 
 ## Examples
 
 - [Basic Session](./examples/basic-session/README.md)
+- [MCP Plan Generation](./examples/mcp-plan-generation/README.md)

Test Scenarios

1. Run bun run build and start the MCP server in the example directory -> The server runs successfully and responds to plan generation requests.
2. Follow the README.md instructions -> Instructions correctly guide a user to run the example.

Target Files

• packages/core/examples/mcp-plan-generation/index.ts
• packages/core/examples/mcp-plan-generation/README.md
• packages/core/examples/mcp-plan-generation/package.json
• packages/core/README.md

Boundary Rules

Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.

---

Fleet Context

• Source: jules:session:14750404909885933131
• Link: https://jules.google.com/session/14750404909885933131