@speajus/diblob-mcp

Model Context Protocol (MCP) server implementation for diblob dependency injection containers.

Overview

@speajus/diblob-mcp provides an MCP server that exposes diblob container functionality through the Model Context Protocol, enabling AI assistants and other MCP clients to interact with your dependency injection containers.

Features

• MCP Server: Expose diblob containers through the Model Context Protocol
• Container Introspection: Query registered blobs and their dependencies
• Dynamic Registration: Register and unregister blobs through MCP tools
• Type-Safe: Full TypeScript support with type inference
• Diblob Architecture: Follows diblob patterns with separate interface/implementation files

Installation

npm install @speajus/diblob-mcp @speajus/diblob @modelcontextprotocol/sdk

Requirements: Node.js >= 22.0.0

Quick Start

import { createContainer } from '@speajus/diblob';
import { registerMcpBlobs, mcpServer } from '@speajus/diblob-mcp';

// Create a diblob container
const container = createContainer();

// Register MCP server blobs
registerMcpBlobs(container);

// Start the MCP server by resolving the mcpServer blob.
// The registration uses lifecycle hooks to call server.start() for you.
await container.resolve(mcpServer);

Architecture

Following diblob conventions, this package separates:

• Interface/Blob Definitions (src/blobs.ts): Type definitions and blob declarations
• Implementations (src/server.ts): Concrete MCP server implementation
• Registration (src/register.ts): Registration function that accepts a container

API Reference

registerMcpBlobs(container)

Registers all MCP-related blobs with the provided container.

import { createContainer } from '@speajus/diblob';
import { registerMcpBlobs, mcpServer } from '@speajus/diblob-mcp';

// Start the MCP server (lifecycle hooks will call start() for you)
await container.resolve(mcpServer);

## Lifecycle

The `registerMcpBlobs` helper registers the `mcpServer` blob as a
`Lifecycle.Singleton` with lifecycle hooks:

- `initialize: 'start'` – called the first time the blob is resolved
- `dispose: 'stop'` – called when the blob is invalidated (for example, when
  it or one of its dependencies is re-registered or unregistered)

This means:

- The MCP server starts automatically the first time you resolve `mcpServer`,
  e.g. with `await container.resolve(mcpServer)`.
- The MCP server is stopped automatically when its registration (or its
  dependencies) are invalidated, following diblob's cascading disposal
  semantics.

const container = createContainer();
registerMcpBlobs(container);

License

MIT