mORMot

The mORMot MCP Server implements the Model Context Protocol (MCP) using the high-performance mORMot2 framework. It exposes a bidirectional HTTP transport with Server-Sent Events (SSE) for real-time notifications, plus a stdio transport option for local development or integration with desktop clients. Core MCP capabilities are exposed through a JSON-RPC 2.0 API, including tools (register, list, and call), resources (list, read, templates, and subscriptions), prompts (list and get), and management operations like logging level configuration and completion for auto-completion assistance. The server provides a session-based workflow with cryptographic session IDs and an event bus for internal pub/sub routing, making it suitable for integrating custom tools, resources, and prompts.

To use the HTTP transport, run the server (for example via Docker as shown in the installation notes) and connect your client to http://<host>:<port>/mcp. The API supports initialize to establish a session, tools/list to enumerate registered tools, and tools/call to execute a tool with proper arguments. SSE connections at the /mcp endpoint deliver real-time updates such as list_changed events for tools, resources, and prompts, along with progress and log notifications. For local testing, the stdio transport can be used, which communicates via newline-delimited JSON over standard I/O, with logs emitted to stderr.

Prerequisites:

• Docker installed and configured if using the docker-based deployment example.
• Optionally, a Delphi 10.3+ or Free Pascal 3.2+ toolchain if compiling locally from source (for development or custom builds).

Recommended deployment via Docker (fastest for MCP):

1. Pull and run the MCP server image: docker pull javierustk/mormot-mcp-server:latest docker run --name mormot-mcp -p 3000:3000 -i javierustk/mormot-mcp-server:latest
2. Ensure the container exposes the HTTP endpoint at http://<host>:3000/mcp (default configuration in the image).

If you prefer to build from source (Delphi/FP):

1. Retrieve the repository sources (mORMot-MCP-Server/).
2. Ensure you have a compatible Delphi 10.3+ or Free Pascal 3.2+ installed and configured with mORMot2 sources.
3. Open the solution/project (MCPServer.dproj for Delphi or the Free Pascal/Lazarus project) and build the executable.
4. Run the resulting binary with the desired transport (HTTP with SSE, or stdio) as described in the Usage section.

Notes and tips:

• Transport options: stdio is suitable for desktop clients or local testing; HTTP with SSE is intended for web clients and remote integrations. TLS is supported for HTTP transport when configured with certificates.
• Endpoint and defaults: The HTTP transport defaults to port 3000 and the MCP endpoint is /mcp. You can customize port and other options when starting the server.
• Configuration references: Settings like ServerName, ServerVersion, Port, Host, Endpoint, and SSEKeepaliveIntervalMs are defined in MCP.Types.pas. Adjust these if you build from source.
• Notifications: The server emits a variety of notifications (list_changed, updated, progress, cancelled, message) via SSE for real-time updates to clients and tools. Ensure clients subscribe to the SSE stream for live updates.
• Security: Consider enabling TLS for HTTP transport and protecting exposed endpoints. Manage sessions using cryptographic session IDs as per MCP specifications.
• Extensibility: Tools, Resources, and Prompts are modular and can be extended by adding new units (e.g., new tool implementation in MCP.Tool.*.pas or new resource/prompts in their respective folders) and registering them in the server initialization.