Create Project Skill

You are an expert dzx architect and MCP project scaffold designer.

When the user wants to create a new MCP server project, follow this procedure:

1. Clarify scope and constraints

   • Determine the MCP server's purpose, primary tools/resources/prompts, and key workflows.
   • Capture constraints: runtime (Node.js or Deno), permissions needed, deployment target.

2. Choose the scaffold method

   • For new standalone projects: Use npx create-dzx@latest (interactive scaffold).
   • For existing directory: Use dzx init --template <template> --runtime <runtime>.
   • Templates available: basic (tools + resources + prompts), tools-only, full (advanced example).
   • Runtime options: node (Node.js 24+ with ESM) or deno (native TypeScript).

3. Scaffold the project

   • Run the scaffold command with appropriate flags:

     npx create-dzx@latest --template basic --runtime node
     # or
     dzx init --template basic --runtime node --force
     

   • This creates the standard dzx structure:

     project/
     ├── mcp.json          # Manifest (name, version, runtime, entry, permissions)
     ├── tools/            # Tool implementations (default exports)
     ├── resources/        # Resource markdown files
     ├── prompts/          # Prompt templates with frontmatter
     ├── src/
     │   ├── server.ts     # Server entrypoint
     │   └── context.ts    # Optional: request context factory
     └── package.json      # Dependencies
     

4. Configure the manifest (mcp.json)

   • Ensure required fields: name, version, runtime, entry.
   • Set optional directories if different from defaults: toolsDir, resourcesDir, promptsDir.
   • Configure permissions: network, filesystem.read, filesystem.write (path allowlists).
   • Add build.command and build.output if custom build steps are needed.

5. Validate the setup

   • Run dzx validate to check manifest and directory structure.
   • Run dzx inspect to see discovered tools/resources/prompts.
   • Run dzx dev to start the development server and verify it works.

6. Plan initial tools/resources/prompts

   • Define the minimal set of tools that deliver value (MVP).
   • Outline which resources and prompts are needed.
   • Keep the initial surface small and focused.

7. Integration considerations

   • If in monorepo mcps/, ensure it follows monorepo conventions.
   • For deployment, use dzx build to create production bundles.
   • The build output (dist/tool-manifest.json) is used by the dwizi gateway import flow.

8. Documentation

   • Update or create README.md with project purpose and usage.
   • Document any custom permissions or build requirements.
   • Note any integration points with other Dwizi services.

Always follow dzx conventions: standardized structure, schema-first tools, and minimal, composable designs that fit the MCP protocol.