Skip to content

Latest commit

 

History

History
38 lines (31 loc) · 1.24 KB

File metadata and controls

38 lines (31 loc) · 1.24 KB

node-starter

This template is the handoff point from blueprint to implementation. Copy it into a fresh repository, rename the placeholder package, and replace the sample provider and tools with your real integration logic.

Included Structure

node-starter/
├── .env.example
├── package.json
├── src/
│   ├── config.mjs
│   ├── index.mjs
│   ├── manifest.mjs
│   ├── providers/
│   │   └── example-api.mjs
│   └── tools/
│       ├── customers.lookup.mjs
│       └── health.mjs
└── tests/
    └── starter.test.mjs

Why This Shape

  • config.mjs centralizes env access and safe defaults.
  • manifest.mjs makes service identity and ownership visible.
  • providers/ holds upstream API wiring so tools stay thin.
  • tools/ holds MCP-facing contracts and business actions.
  • tests/ keeps starter invariants executable with zero dependencies.

Expected Next Edits

  1. Rename the package and service metadata.
  2. Replace example-api.mjs with your real provider adapter.
  3. Swap placeholder tool schemas for your actual actions.
  4. Add transport bootstrapping with your MCP SDK of choice.
  5. Keep the smoke tests and expand them as real behavior appears.