Direct In Process Tool Invocation With Dependency Injection

via “direct in-process tool invocation with dependency injection”

A NestJS library for building transport-agnostic MCP tool services. Define tools once with decorators, consume them over HTTP, stdio, or directly via the registry. The documentation and examples generally focus one enterprise monorepos but can be easily a

Unique: Provides direct in-process tool access via NestJS dependency injection, allowing tools to be consumed as regular service methods without transport overhead — most MCP libraries only support network-based access, making testing and internal integration cumbersome

vs others: Enables zero-latency tool invocation and simpler testing compared to HTTP/stdio transports, and allows tools to be integrated as first-class NestJS services

via “spring dependency injection integration for tools and resources”

** - Provides auto-configuration for setting up an MCP server in Spring Boot applications.

Unique: Seamlessly integrates Spring's dependency injection container with MCP tool execution, allowing tools to declare dependencies using standard Spring patterns (@Autowired, constructor injection) without MCP-specific wiring code — a capability that bridges Spring's IoC model with MCP's tool abstraction

vs others: Eliminates manual dependency resolution in tools; Spring developers can use familiar injection patterns rather than learning MCP-specific dependency management, whereas standalone MCP implementations require explicit service locator or factory patterns