Request Context And Logging With Request Id Tracking

via “request-scoped context and observability with structured logging”

Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It provides a comprehensive suite of tools for reading, writing, searching, and managing notes, tags, and frontmatter, acting as a bridge to the Obsidian

Unique: Uses async-local-storage pattern to propagate request context through the entire call stack without explicit parameter passing, enabling automatic context injection into all logs and Obsidian REST API calls. Integrates with structured logging to correlate logs across multiple service calls.

vs others: Automatic context propagation (unlike manual parameter passing) reduces boilerplate and ensures consistent context across all layers. Structured logging enables machine-readable log aggregation and correlation, whereas unstructured logs are difficult to parse and correlate.

via “request context and correlation tracking for agent operations”

A Model Context Protocol (MCP) server for ATLAS, a Neo4j-powered task management system for LLM Agents - implementing a three-tier architecture (Projects, Tasks, Knowledge) to manage complex workflows. Now with Deep Research.

Unique: Uses AsyncLocalStorage to propagate request context implicitly through the call stack, avoiding the need to thread context through every function signature. Enables correlation of distributed operations without explicit parameter passing.

vs others: Cleaner than manual context threading because context is automatically available in any async operation; more efficient than request-scoped logging because context is stored once and accessed multiple times.

** (TypeScript)

Unique: Injects Context object into all handlers containing requestId, sessionId, and log() method, enabling structured logging and request tracing without requiring developers to manually pass context or implement request ID generation

vs others: More ergonomic than manual logging because request IDs are generated and injected automatically, whereas raw MCP SDK requires developers to manually generate request IDs and pass them through function signatures