@stackonward/cli 0.0.1 → 1.0.1

package/dist/resources/templates/mcp-server/.claude/docs/stack.md

@@ -0,0 +1,338 @@
+# MCP Server Application Coding Standard
+
+> **Stack**: Node.js >=20, TypeScript 5, ESM, MCP SDK (`@modelcontextprotocol/sdk` 1.x), Zod 3, tsup 8, Vitest 2, ESLint 9 and Prettier 3.
+> **Transport**: compiled stdio server. Tool and resource registrations are application-owned.
+> `package.json` and the lockfile are the dependency/version authority.
+
+## I. Project Purpose and Runtime
+
+The application exposes typed MCP tools and resources through the installed SDK. `src/index.ts` creates the server, registers tools/resources and connects `StdioServerTransport`. External application services belong in `src/services/`; tool registration is not an authorization or persistence layer.
+
+The current template provides `hello`, `get_info` and a help resource. It does not include remote credentials, a database, OAuth middleware, an HTTP transport, a hosted API gateway or a background worker. Do not describe such capabilities as installed merely because the architecture can support an adapter.
+
+### Commands
+
+| Command                            | Actual script behavior                                           |
+| ---------------------------------- | ---------------------------------------------------------------- |
+| `pnpm dev`                         | `tsup --watch`; rebuilds, does not itself start a client session |
+| `pnpm build`                       | Build compiled output with tsup                                  |
+| `pnpm start`                       | Run `dist/index.js`                                              |
+| `pnpm start:stdio`                 | Run the compiled entry with `--stdio`                            |
+| `pnpm typecheck`                   | `tsc --noEmit`                                                   |
+| `pnpm lint`, `pnpm lint:fix`       | ESLint over `src/`                                               |
+| `pnpm format`, `pnpm format:check` | Prettier over TypeScript source                                  |
+| `pnpm test`, `pnpm test:watch`     | Vitest run/watch                                                 |
+| `pnpm test:coverage`               | Vitest with V8 coverage                                          |
+| `pnpm inspect`                     | Launch the MCP Inspector command                                 |
+| `pnpm mcp-test`                    | Start stdio process; not an assertion-based protocol test        |
+| `pnpm publish:local`               | Build and pack the npm artifact                                  |
+| `pnpm prepublishOnly`              | Typecheck, lint, test and build                                  |
+| `pnpm pub:release`                 | Build and publish; requires publication authorization            |
+| `pnpm prepare`                     | Existing Husky setup script                                      |
+
+A successful executable launch is not proof of a valid initialize/list/call/read exchange. Build before inspecting the compiled entry. Declared test scripts do not imply business or external-service acceptance coverage exists.
+
+### Environment
+
+`.env.example` currently documents `DEBUG=false` and credential examples. The entrypoint does not load dotenv or read `DEBUG`; creating `.env` does not automatically activate configuration. Configure actual process environment through the launcher and document each real consumer when adding a variable.
+
+**FORBIDDEN**: private credentials in tool descriptions, help resources, source, package metadata, command arguments logged by the launcher or protocol output. Validate required configuration before registering an operational capability that depends on it.
+
+## II. Structure and Import Rules
+
+| Owner                                 | Key responsibility                                       |
+| ------------------------------------- | -------------------------------------------------------- |
+| `src/index.ts`                        | Server identity, registration and transport startup      |
+| `src/tools.ts::registerTools`         | Tool names, descriptions, argument schemas and dispatch  |
+| `src/resources.ts::registerResources` | Resource identity, URI, MIME type and read result        |
+| `src/services/`                       | External service implementation and protocol translation |
+| `src/types/index.ts`                  | Existing application type declarations                   |
+| `src/utils/index.ts`                  | `safeJsonParse`, `delay`, `formatError` value helpers    |
+| `tsup.config.ts`                      | Compiled entry and build output                          |
+| `tsconfig.json`                       | TypeScript module/resolution contract                    |
+| `vitest.config.ts`                    | Test discovery and execution configuration               |
+
+Use type-only imports for types. Runtime relative imports retain `.js` suffixes as required by the ESM source/build convention. Public SDK imports follow the actual installed exports, not guessed internal paths.
+
+Import order: types → SDK/framework → installed libraries → application owners. Do not add undeclared dependencies or import a package's private source directory.
+
+## III. Read and Placement Gate (CRITICAL)
+
+Before adding a tool/resource, read existing registrations, SDK version and public API, input/output types, service adapter and runtime consumer. Search names and URIs with `rg`; registrations must remain unique and describe the owning action.
+
+| Responsibility                      | Owner                                  |
+| ----------------------------------- | -------------------------------------- |
+| MCP argument schema                 | Tool registration                      |
+| Use case and business invariant     | Application service                    |
+| Provider HTTP payload/error mapping | Service adapter                        |
+| Shared pure parsing/formatting      | Existing utility when contract matches |
+| Process connection/lifetime         | Entrypoint and transport composition   |
+| Permission and resource scope       | Authoritative service contract         |
+
+A tool callback may parse and dispatch; it must not become a second provider implementation. A provider adapter must not register protocol handlers, choose UI copy or write transport frames.
+
+✅ Correct: tool validates arguments, calls a typed service and converts its result to MCP content.
+
+❌ Wrong: every tool builds its own client, reads credentials, implements retries and catches all errors as success.
+
+## IV. Tool Contract Standards
+
+Names describe one independently callable action. Descriptions state its purpose, input meaning and observable effect without hidden prerequisites. A tool with effects must identify the scope and permission boundary; model instructions cannot grant authority.
+
+Zod schemas validate string length, numeric range, enum choices and required fields as appropriate. Validate at the boundary before effects; internal code consumes typed values. Do not repeatedly parse trusted framework-provided fields.
+
+```typescript
+import { z } from "zod";
+
+const inputShape = {
+  name: z.string().trim().min(1).max(120).describe("Name to greet"),
+};
+```
+
+This is a schema pattern, not a claim that the current `hello` schema already enforces those limits. Production tool changes must align descriptions, accepted arguments and implementation.
+
+### Result Semantics
+
+| Outcome                     | Required result                                                      |
+| --------------------------- | -------------------------------------------------------------------- |
+| Completed read/action       | Content describes the actual result                                  |
+| Accepted asynchronous work  | Return operation identity and accepted/running state                 |
+| Validation/protocol failure | Use SDK protocol failure semantics                                   |
+| Execution failure           | Error result appropriate to SDK/tool contract; do not report success |
+| Partial completion          | Preserve completed results and identify failed parts                 |
+| Unsupported operation       | Explicit typed failure; no empty success                             |
+
+Do not use one `success` boolean for accepted, completed and partially failed work. Counts and progress come from authoritative service data, not elapsed time or fabricated samples.
+
+## V. Resource Standards
+
+Resources represent readable content with stable URI identity and explicit MIME type. Return contents whose URI agrees with the requested/registered resource. Scope dynamic resources to the authorized service data; guessed URIs do not bypass authorization.
+
+Resource reads must not perform unrelated mutations. Expensive or paginated data must use a bounded contract; do not dump unlimited records into a single text response. Help resources list real available capabilities and current input meaning.
+
+✅ Correct: a help resource documents registered tool names and URI identity.
+
+❌ Wrong: static help claims a remote account action exists while registration/service support is absent.
+
+## VI. Type Definitions and Validation
+
+Co-locate tool-specific input/result types with their owner. Shared types require actual multiple consumers. Use SDK result types where appropriate rather than creating a broader incompatible protocol union.
+
+`ServerConfig` is an application declaration, not proof of a runtime configuration loader. `ToolResult` is a local type and must not override the SDK wire schema.
+
+`safeJsonParse<T>` checks JSON syntax only. The generic assertion does not verify fields; validate external data with a real schema after parsing. `formatError` converts an unknown error to text; callers must ensure that text is safe before exposing it to users.
+
+**FORBIDDEN**: treating `as SomeResponse`, `unknown as SomeResponse` or an optional field bag as proof that an external response is valid. Keep error, absent and partial data states explicit.
+
+## VII. Services and Extension Points (CRITICAL)
+
+External calls and replaceable providers start with a consumer-owned interface, then configuration, concrete adapter and dependency composition. Tool contracts must not embed provider model names or credential format.
+
+```typescript
+interface LookupService {
+  lookup(query: string, signal: AbortSignal): Promise<readonly string[]>;
+}
+```
+
+A second adapter should change the adapter and composition/configuration entry, not every tool. Keep service errors stable while preserving provider diagnostics behind a safe boundary.
+
+Do not add a universal `execute(name, args: any)` service to hide incompatible operations. Each tool/service operation needs precise arguments, effect semantics, idempotency and errors.
+
+## VIII. Security and Authorization
+
+A local stdio connection is a transport context, not permission to access every resource or provider account. Enforce scope through the configured service identity and actual backend contract. User-supplied IDs, file paths, URLs and model-generated arguments remain untrusted.
+
+Outbound adapters restrict protocol and destination. File adapters resolve paths against configured roots and reject traversal. A tool description saying “safe” does not constrain runtime behavior.
+
+Never expose secrets in one-time credentials except through the deliberate, authorized result contract. Logs and subsequent reads must redact them. Do not add fictional OAuth/IAM behavior to documentation for an unimplemented transport.
+
+## IX. Transport and Lifecycle
+
+stdout belongs exclusively to MCP framing. Diagnostics use stderr and exclude secret values. `console.log` in a tool or provider corrupts stdio even when the business function is otherwise correct.
+
+The process entry owns connection startup and shutdown. Every subscription, timer, request and stream has a disposal owner. A disconnected client or cancelled request cannot continue writing results into another session's state.
+
+The existing `delay` utility is an uncancellable timer. Do not treat it as a cancellation-aware retry primitive. Use an operation-owned abort contract for cancellable remote work.
+
+Transport disconnect only proves local disconnection. It does not prove remote rollback, job cancellation or refund. Report the actual acknowledged service state.
+
+## X. Retry, Concurrency and Idempotency
+
+Read retries are bounded by attempt and total-time budgets. Honor cancellation and provider retry hints. Mutation retries require explicit idempotency or acceptance-status lookup; ambiguous timeouts must not trigger blind duplicate effects.
+
+Idempotency keys, internal resource IDs, external IDs and display labels have separate meanings. The authoritative backend owns durable uniqueness and replay. A process-local Set cannot provide cross-process exactly-once execution.
+
+Concurrent tool calls must not overwrite shared mutable state or reuse one caller's identity. Scope caches and clients according to the credential/resource boundary. Do not share sensitive results through unscoped module globals.
+
+## XI. Error and Diagnostic Contract
+
+| Failure               | Handling                                                 |
+| --------------------- | -------------------------------------------------------- |
+| Invalid arguments     | Reject before provider call with safe field guidance     |
+| Missing configuration | Explicit startup/capability failure; no simulated result |
+| Permission denied     | Preserve denial; do not retry with another identity      |
+| Rate limit            | Bounded retry or explicit retryable result               |
+| Provider unavailable  | Safe code and preserved correlation                      |
+| Internal failure      | Safe tool/protocol error and controlled diagnostics      |
+
+Catch errors only at a boundary that can translate, recover or terminate correctly. Empty catch blocks and fallback successful content are forbidden. A valid JSON response containing false claims is still a failed contract.
+
+## XII. Forbidden Patterns
+
+| ID     | Forbidden                                            | Required behavior                       |
+| ------ | ---------------------------------------------------- | --------------------------------------- |
+| MCP-01 | Unvalidated tool arguments                           | Declared schema before effects          |
+| MCP-02 | Credentials/protocol conversion in tool descriptions | Configuration and service adapters      |
+| MCP-03 | Failed operation returned as success                 | Explicit semantic error                 |
+| MCP-04 | Diagnostic stdout writes                             | Protocol-only stdout, safe stderr       |
+| MCP-05 | Hidden resource lifetime                             | Explicit owner and disposal             |
+| MCP-06 | Unbounded effectful retry                            | Contract-backed bounded retry           |
+| MCP-07 | Provider-specific model in shared interface          | Configured provider adapter             |
+| MCP-08 | Type assertions as validation                        | Parse unknown data                      |
+| MCP-09 | Unrestricted URL or filesystem access                | Configured destination/root scope       |
+| MCP-10 | Duplicate tool/resource identity                     | Unique registry entry and matching docs |
+| MCP-11 | Help resources describe absent behavior              | Real registered capabilities            |
+| MCP-12 | Startup success claimed as protocol acceptance       | Initialize/list/call/read evidence      |
+| MCP-13 | Test fixtures in production results                  | Real service response                   |
+| MCP-14 | Unshipped source imports in package                  | Packed artifact consumer checks         |
+| MCP-15 | Tool input grants resource authority                 | Backend/service authorization           |
+| MCP-16 | Error serializer leaks request credentials           | Safe code/message boundary              |
+
+## XIII. Testing and Distribution
+
+Use Vitest for schema, service and result behavior. Fakes are test-only and preserve the actual success/error shape. Assert observable guarantees, including rejection before effects, timeout ambiguity, partial completion and disposal.
+
+For transport changes, build and verify initialization, tools/list, tools/call, resources/list, resources/read and close through a real protocol client. Include invalid/unknown operations. Inspect stdout purity and stderr safety.
+
+For package changes, inspect `npm pack` output and run the compiled binary outside the source workspace. `files` currently publishes `dist` and README; source checkout files cannot be required at runtime. Do not publish without authorization.
+
+### Complete Registration and Protocol Error Example
+
+This complete Vitest example exercises the installed SDK with linked transports. It registers a deterministic text-normalization tool, calls it through `Client`, verifies content and verifies an explicit execution-error result. The example has no provider credentials, HTTP endpoints or product policy. In an application, the registration function belongs to the tool owner and is called by `src/index.ts`; the test belongs in test source.
+
+```typescript
+import { afterEach, expect, test } from "vitest";
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { Client } from "@modelcontextprotocol/sdk/client/index.js";
+import { InMemoryTransport } from "@modelcontextprotocol/sdk/inMemory.js";
+import { z } from "zod";
+
+function registerNormalizationTool(server: McpServer): void {
+  server.tool(
+    "normalize_text",
+    "Normalize whitespace within a declared output limit.",
+    {
+      text: z.string().min(1).max(10_000),
+      maxLength: z.number().int().min(1).max(10_000),
+    },
+    async ({ text, maxLength }) => {
+      const normalized = text.trim().replace(/\s+/gu, " ");
+      if (normalized.length > maxLength) {
+        return {
+          isError: true,
+          content: [{ type: "text" as const, text: "Normalized text exceeds the output limit." }],
+        };
+      }
+      return { content: [{ type: "text" as const, text: normalized }] };
+    },
+  );
+}
+
+const client = new Client({ name: "protocol-check", version: "1.0.0" });
+const server = new McpServer({ name: "normalization-example", version: "1.0.0" });
+afterEach(async () => {
+  await client.close();
+  await server.close();
+});
+
+test("registration, successful call and execution error preserve protocol semantics", async () => {
+  registerNormalizationTool(server);
+  const [clientTransport, serverTransport] = InMemoryTransport.createLinkedPair();
+  await server.connect(serverTransport);
+  await client.connect(clientTransport);
+
+  const listing = await client.listTools();
+  expect(listing.tools.map((tool) => tool.name)).toContain("normalize_text");
+
+  const result = await client.callTool({
+    name: "normalize_text",
+    arguments: { text: "  alpha   beta  ", maxLength: 20 },
+  });
+  expect(result.isError).not.toBe(true);
+  expect(result.content).toEqual([{ type: "text", text: "alpha beta" }]);
+
+  const failure = await client.callTool({
+    name: "normalize_text",
+    arguments: { text: "alpha beta", maxLength: 3 },
+  });
+  expect(failure.isError).toBe(true);
+  expect(failure.content).toEqual([
+    { type: "text", text: "Normalized text exceeds the output limit." },
+  ]);
+});
+```
+
+✅ An execution limit returns `isError: true`, not a successful empty string. SDK schemas still reject malformed types before the callback; boundary tests must also cover those schema constraints when changing them.
+
+❌ Do not call a tool callback directly and label that a protocol test. Do not catch every provider exception into `{ content: [] }`, and do not write diagnostic messages to stdout.
+
+### Complete Compiled Stdio Acceptance Example
+
+The following JavaScript script runs against the **existing generated** `hello`, `get_info` and help resource. Save it as `scripts/check-stdio.mjs` in a generated application that needs this check, build, then run `node scripts/check-stdio.mjs`. This is an executable example, not a claim that the template already ships this script or a corresponding package command.
+
+```javascript
+import assert from "node:assert/strict";
+import { resolve } from "node:path";
+import { Client } from "@modelcontextprotocol/sdk/client/index.js";
+import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
+
+const client = new Client({ name: "stdio-check", version: "1.0.0" });
+const transport = new StdioClientTransport({
+  command: process.execPath,
+  args: [resolve("dist/index.js"), "--stdio"],
+  stderr: "inherit",
+});
+
+try {
+  await client.connect(transport);
+  const listing = await client.listTools();
+  assert.ok(listing.tools.some((tool) => tool.name === "hello"));
+  assert.ok(listing.tools.some((tool) => tool.name === "get_info"));
+  const greeting = await client.callTool({ name: "hello", arguments: { name: "Ada" } });
+  assert.notEqual(greeting.isError, true);
+  assert.ok(
+    greeting.content.some((block) => block.type === "text" && block.text.includes("Hello, Ada!")),
+  );
+  const resources = await client.listResources();
+  const help = resources.resources.find((resource) => resource.name === "help");
+  assert.ok(help, "Help resource must be registered");
+  const result = await client.readResource({ uri: help.uri });
+  assert.ok(
+    result.contents.some((entry) => entry.uri === help.uri && entry.mimeType === "text/markdown"),
+  );
+} finally {
+  await client.close();
+  await transport.close();
+}
+```
+
+The SDK client performs initialization and owns request framing; the compiled child process proves distribution/startup behavior. In-memory protocol tests and stdio acceptance prove different boundaries. Neither proves an external provider account is authorized. Assertions, connection shutdown and error propagation are part of the example; do not replace them with a process-start message.
+
+## XIV. Documentation and Delivery
+
+Comments explain why in Chinese. Exported services and utilities document input, errors, ownership and disposal where not self-evident. Keep tool descriptions, help resources and actual registration synchronized.
+
+Read [Architecture](architecture.md), [Security and Lifecycle](security-lifecycle.md), [Verification](verification.md) and the full [Design Template](architecture-template.md).
+
+### Pre-commit Checklist
+
+- [ ] Tool/resource names and URIs are unique and documented accurately.
+- [ ] Schemas validate input before effects and types match SDK contracts.
+- [ ] Provider configuration, business policy and protocol registration have separate owners.
+- [ ] Scope, safe errors, cancellation and idempotency are explicit.
+- [ ] stdout is protocol-clean; stderr contains no credentials or personal payloads.
+- [ ] `pnpm typecheck`, `pnpm lint`, `pnpm test` and `pnpm build` pass for code changes.
+- [ ] Actual compiled transport behavior is verified when touched.
+- [ ] Packed artifact runs independently of the company checkout.
+- [ ] External-service acceptance is not inferred from fakes or process launch.
+- [ ] No deferred production action or invented command is delivered.

package/dist/resources/templates/mcp-server/.editorconfig

@@ -0,0 +1,13 @@
+# EditorConfig - https://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false

package/dist/resources/templates/mcp-server/.env.example

@@ -0,0 +1,8 @@
+# Environment variables for {{projectName}}
+# Copy this file to .env and fill in the values
+
+# Debug mode
+DEBUG=false
+
+# Add your environment variables here
+# API_KEY=your_api_key_here

package/dist/resources/templates/mcp-server/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,104 @@
+name: Bug Report
+description: Report a bug or unexpected behavior
+labels: ["bug", "triage"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug! Please fill out the form below.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of what the bug is.
+      placeholder: Describe the bug...
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. Configure MCP server with...
+        2. Run command...
+        3. See error...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+      placeholder: Describe what you expected...
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+      placeholder: Describe what actually happened...
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Package Version
+      description: What version of {{projectName}} are you using?
+      placeholder: "0.1.0"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: client
+    attributes:
+      label: MCP Client
+      description: Which MCP client are you using?
+      options:
+        - Cursor
+        - Windsurf
+        - Cline
+        - Claude Desktop
+        - Other
+    validations:
+      required: true
+
+  - type: input
+    id: node-version
+    attributes:
+      label: Node.js Version
+      description: What version of Node.js are you using? (run `node -v`)
+      placeholder: "v20.0.0"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating System
+      options:
+        - macOS
+        - Windows
+        - Linux
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Error Logs
+      description: If applicable, paste any error logs here.
+      render: shell
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Any other context about the problem.

package/dist/resources/templates/mcp-server/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,54 @@
+name: Feature Request
+description: Suggest a new feature or improvement
+labels: ["enhancement"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a feature! Please fill out the form below.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: Is your feature request related to a problem? Please describe.
+      placeholder: "I'm always frustrated when..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the solution you'd like to see.
+      placeholder: "I would like to be able to..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Describe any alternative solutions or features you've considered.
+      placeholder: "I've also thought about..."
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How important is this feature to you?
+      options:
+        - Nice to have
+        - Important
+        - Critical
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      description: Are you willing to contribute to this feature?
+      options:
+        - label: I'm willing to submit a PR for this feature

package/dist/resources/templates/mcp-server/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,36 @@
+## Description
+
+<!-- Describe your changes in detail -->
+
+## Related Issue
+
+<!-- Link to the issue this PR addresses (if applicable) -->
+<!-- Fixes #123 -->
+
+## Type of Change
+
+<!-- Mark the relevant option with an "x" -->
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Refactoring (no functional changes)
+
+## Checklist
+
+- [ ] My code follows the project's style guidelines
+- [ ] I have performed a self-review of my code
+- [ ] I have added/updated comments for hard-to-understand areas
+- [ ] I have updated the documentation (if applicable)
+- [ ] My changes generate no new warnings
+- [ ] I have run `pnpm lint` and `pnpm build` successfully
+- [ ] I have tested my changes locally
+
+## Screenshots (if applicable)
+
+<!-- Add screenshots to help explain your changes -->
+
+## Additional Notes
+
+<!-- Any additional information that reviewers should know -->

package/dist/resources/templates/mcp-server/.github/workflows/ci.yml

@@ -0,0 +1,78 @@
+name: CI
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x, 22.x]
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: "pnpm"
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Type check
+        run: pnpm typecheck
+
+      - name: Lint
+        run: pnpm lint
+
+      - name: Test
+        run: pnpm test
+
+      - name: Build
+        run: pnpm build
+
+  release:
+    needs: build
+    runs-on: ubuntu-latest
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+          cache: "pnpm"
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Build
+        run: pnpm build
+
+      # Uncomment to enable auto-publish on main branch
+      # - name: Publish to npm
+      #   run: npm publish --access public
+      #   env:
+      #     NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package/dist/resources/templates/mcp-server/.husky/commit-msg

@@ -0,0 +1 @@
+npx --no -- commitlint --edit $1

package/dist/resources/templates/mcp-server/.husky/pre-commit

@@ -0,0 +1 @@
+npx lint-staged

package/dist/resources/templates/mcp-server/.lintstagedrc.json

@@ -0,0 +1,4 @@
+{
+  "src/**/*.{ts,tsx}": ["eslint --fix", "prettier --write"],
+  "*.{json,md,yml,yaml}": ["prettier --write"]
+}

package/dist/resources/templates/mcp-server/.nvmrc

@@ -0,0 +1 @@
+20

package/dist/resources/templates/mcp-server/.prettierrc

@@ -0,0 +1,8 @@
+{
+  "semi": true,
+  "trailingComma": "all",
+  "singleQuote": false,
+  "printWidth": 100,
+  "tabWidth": 2,
+  "useTabs": false
+}