- Build:
npm run build- Compiles TypeScript to JavaScript - Watch mode:
npm run watch- Watches for changes and rebuilds automatically - Run STDIO server:
npm run start:stdio- Starts the MCP server using stdio transport - Run SSE server:
npm run start:sse- Starts the MCP server with SSE transport - Run StreamableHttp server:
npm run start:streamableHttp- Starts the MCP server with StreamableHttp transport - Prepare release:
npm run prepare- Builds the project for publishing
The repo-wide TypeScript, naming and MCP rules are in the root
AGENTS.md, which is loaded in every session. This file holds
only what is specific to this server, and is loaded when a file in this
directory is read. Beyond the root rules:
- Match the existing code style, import order and module layout of the folder you are working in.
- Use kebab-case for file names and for registered tools, prompts and resources
(e.g.
get-annotated-message, notannotated-message).
The Everything Server is designed to be extended at well-defined points.
See Extension Points and Project Structure.
The server factory is src/everything/server/index.ts and registers all features during startup as well as handling post-connection setup.
- The server serves both protocol eras (2026-07-28 and 2025-era); the factory is
createServer({ era }), and what each era gets is wired inserver/index.tsandtools/index.ts. - Tools live under
src/everything/tools/and are registered viaregisterTools(server, context)(both eras),registerModernTools(2026-07-28) orregisterLegacyTools/registerConditionalTools(2025 era). - Resources live under
src/everything/resources/and are registered viaregisterResources(server, context). - Prompts live under
src/everything/prompts/and are registered viaregisterPrompts(server). - Subscriptions and simulated update routines are under
src/everything/resources/subscriptions.ts. - Logging helpers are under
src/everything/server/logging.ts. - Transport managers are under
src/everything/transports/.
- Follow the existing file/module pattern in its folder (naming, exports, and registration function).
- Export a
registerX(server)function that registers new items with the MCP SDK in the same style as existing ones (taking the per-instancecontexttoo when it needs the era, the change publisher or per-connection state). - Keep no state in module-level maps keyed by session id; see Extension Points.
- Wire your new module into the central index (e.g., update
tools/index.ts,resources/index.ts, orprompts/index.ts). - Ensure schemas (for tools) are accurate JSON Schema and include helpful descriptions and examples.
- Keep the docs in
src/everything/docs/up to date if you add or modify noteworthy features.