Skip to content

Import "Build a weather server" quickstart guide#1549

Draft
jonathanhefner wants to merge 3 commits intomodelcontextprotocol:mainfrom
jonathanhefner:server-quickstart
Draft

Import "Build a weather server" quickstart guide#1549
jonathanhefner wants to merge 3 commits intomodelcontextprotocol:mainfrom
jonathanhefner:server-quickstart

Conversation

@jonathanhefner
Copy link
Member

@jonathanhefner jonathanhefner commented Feb 17, 2026

ℹ️ This is based on top of #1532.

Import and adapt the server quickstart tutorial from modelcontextprotocol.io and the companion weather-server-typescript example from modelcontextprotocol/quickstart-resources into this repo.

docs/server-quickstart.md uses code fences with source= attributes so code snippets are type-checked and kept in in sync with the full runnable example in examples/server-quickstart/.

Supporting changes:

  • docs/documents.md: list the new doc
  • typedoc.config.mjs: add powershell syntax highlighting
  • .prettierignore: exclude examples/server-quickstart/ (2-space indent to match ecosystem conventions)
  • scripts/sync-snippets.ts: fix dedent() short-circuit on empty baseIndent; move .trim() so region extraction sees full file

jonathanhefner and others added 3 commits February 13, 2026 12:04
Sampling and elicitation are now inline sections in `docs/server.md`
under a new "Server-initiated requests" heading, with type-checked code
snippets (`registerTool_sampling`, `registerTool_elicitation` regions in
`serverGuide.examples.ts`). This fixes the asymmetry where logging got
full inline treatment but structurally identical features (sampling,
elicitation) were exiled to table rows pointing at a separate file.

Tasks get subsections in both guides that name the entry-point APIs
(`registerToolTask`, `callToolStream`, `getTask`, `getTaskResult`) and
link to runnable examples, with progressive disclosure through JSDoc.

JSDoc enhancements for task APIs:

- `ToolTaskHandler`: three-phase description moved to field-level docs,
  `@see` linking to `registerToolTask`
- `ResponseMessage`, `TaskStatusMessage`, `TaskCreatedMessage`,
  `ResultMessage`, `ErrorMessage`: lifecycle semantics and terminal
  behaviour documented; `{@linkcode}` cross-references to streaming APIs
- `takeResult`, `toArrayAsync`: added JSDoc
- `InMemoryTaskStore`: `{@inheritdoc TaskStore.*}` on all public methods

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move DNS rebinding protection and multi-node deployment patterns into a
new `## Deployment` umbrella near the end — they were splitting the flow
between Transports and core primitives. Promote Logging from a `####`
under Tools to a `###` peer of Tools/Resources/Prompts, since
`ctx.mcpReq.log()` is available in any handler, not just tools. Add a
brief `#### Tool annotations` subsection under Tools (previously only in
the catch-all table). Remove the Tool annotations row from the
`More server features` table and drop the cross-link to client.md from
the Completions section.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Import and adapt the server quickstart tutorial from
modelcontextprotocol.io and the companion `weather-server-typescript`
example from `modelcontextprotocol/quickstart-resources` into this repo.

`docs/server-quickstart.md` uses code fences with `source=` attributes
so code snippets are type-checked and kept in in sync with the full
runnable example in `examples/server-quickstart/`.

Supporting changes:

- `docs/documents.md`: list the new doc
- `typedoc.config.mjs`: add `powershell` syntax highlighting
- `.prettierignore`: exclude `examples/server-quickstart/` (2-space
  indent to match ecosystem conventions)
- `scripts/sync-snippets.ts`: fix `dedent()` short-circuit on empty
  `baseIndent`; move `.trim()` so region extraction sees full file

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@changeset-bot
Copy link

changeset-bot bot commented Feb 17, 2026

⚠️ No Changeset found

Latest commit: 725c3fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 17, 2026

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@1549

@modelcontextprotocol/server

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@1549

@modelcontextprotocol/express

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/express@1549

@modelcontextprotocol/hono

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/hono@1549

@modelcontextprotocol/node

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/node@1549

commit: 725c3fe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant