This repository brings together practical examples and ready-made MCP Server projects created with Delphi, following the official Model Context Protocol (MCP) specification.
MCP is a standard created by Anthropic that allows LLMs (Language Models) to discover and use external tools in a standardized way, such as accessing databases, reading files, and executing APIs, all in real time and with loose coupling.
- Database (STDIO communication) - For connecting to, querying, and working with databases (SQLite, MySQL, Firebird, MS SQL, or PostgreSQL).
- Database-HTTP (HTTP communication) - For connecting to, querying, and working with databases (SQLite, MySQL, Firebird, MS SQL, or PostgreSQL).
- FileSystem (STDIO communication) - For manipulating files and folders in the file system.
- DateTime (STDIO communication) - Exposes the current date and time.
- ServerInfoPC (STDIO communication) - PC/Windows Information
Want to learn how to use the thousands of MCP Servers and MCP Clients already available and, even better, create your own easily with Delphi?
On the Code4Delphi channel, you'll find a series of practical videos that show you, step by step, how to implement the Model Context Protocol in your systems, easily connecting LLMs to real data and external tools.
- Communication via standard input/output.
- Used in local scenarios or when you want to directly control process execution.
- Best suited for integration between processes on the same machine.
- The client starts the MCP server locally and exchanges messages via binary text streams or JSON.
- Requires the MCP server to be started by the client and the data stream to be manually managed.
- Lowest level, requires the client to manage execution.
- Communication via HTTP streaming (events sent from the server to the client).
- Best suited for remote connections or web applications.
- The MCP server must already be running on an accessible endpoint. - Less process management work, as transport is handled via the HTTP protocol.
- The client listens for events sent continuously by the MCP server.
- Communication via standard HTTP, with requests and responses.
- Not streaming, it works in a request/response model.
- Good for one-off operations or when continuous traffic is not necessary.
- Easier to integrate with systems that already work with REST APIs.
👉 In short:
- STDIO: Local, direct, and client-controlled.
- SSE: Remote via HTTP, continuous streaming.
- HTTP: Remote, on-demand requests.
