Servers must declare logging capability
Servers that emit log message notifications MUST declare the logging capability in their capabilities object with the key "logging" set to an empty object.
MCP · Building servers and clients · all subjects
server building
5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
Server implementation guidelines for pagination
Servers should provide stable cursors and handle invalid cursors gracefully.
MCP repository structure: documentation and schema
The MCP repository is organized as follows: docs/ contains a Mintlify site with docs/docs/ for guides and tutorials versioned as draft/ or [YYYY-MM-DD]/, and docs/specification/ for the formal specification versioned the same way. blog/ contains a Hugo blog. TypeScript files in schema/[version]/schema.ts are the source of truth for the protocol schema. The npm run generate:schema command generates both schema/[version]/schema.json and the Schema Reference document in docs/specification/[version]/schema.mdx. JSON examples live in schema/[version]/examples/[TypeName]/ where the directory name matches the schema type (e.g., Tool/, Resource/).
Documentation and schema generation commands
Key npm commands for MCP development: npm run serve:docs starts local Mintlify docs server, npm run serve:blog starts local Hugo blog server. npm run generate:schema generates JSON schemas and MDX from TypeScript after editing schema/[version]/schema.ts. npm run prep runs full preparation before committing: check, generate, and format. npm run check:schema checks schema (TS, JSON, examples, MDX). npm run format:schema formats schema TypeScript files.
Schema examples validation
JSON examples in schema/[version]/examples/[TypeName]/ are validated against their directory's schema type. For example, a file named Tool/example-name.json is validated against the Tool schema. These examples are referenced in schema.ts via @includeCode JSDoc tags.