Description

A powerful, attribute-driven framework for building Model Context Protocol (MCP) Servers in Delphi. MCPConnect is a framework for building Model Context Protocol (MCP) servers with Embarcadero Delphi & C++Builder. It uses attributes (for C++Builder there is a function-based registration mechanism) to turn your existing Delphi classes and business logic into MCP tools, resources and prompts, while the library takes care of serialization, routing and context management on the server side of the MCP protocol.

MCPConnect is developed by Paolo Rossi and Luca Minuti and released as open source under the MIT license. The project started in July 2025 (the first commit on GitHub is dated August 12, 2025) and has grown quickly since then, also thanks to contributions from the community.

An introduction to MCP

The Model Context Protocol is a protocol introduced by Anthropic in 2024 to standardize the way large language models (LLMs) talk to external systems. On their own, LLMs can only produce text (tokens): they can’t act on the outside world, and they can only answer with what they learned during training.

OpenAI tried to solve a similar problem back in 2023 with “function calling”. Most other vendors copied the idea, but each implementation was tied to its own API, so anyone who wanted to support more than one model had to write the same integration several times. MCP fixes this with a single, vendor-neutral protocol: you write the server once and any compatible host can use it.

Some typical uses of MCP:

• Databases: query InterBase, PostgreSQL, Firebird or SQLite for data analysis
• Filesystem: read, search and analyze local files
• Browser automation: web scraping, automated testing, interacting with web applications
• Third-party services: Slack, GitHub, Linear, Jira and similar
• Internal tools: give the LLM access to your company’s APIs and systems
• Data processing: work on Excel, CSV or other formats with your own logic
• Existing Delphi applications: expose the code you already have (a FireDAC query, an invoicing module, a report generator) without rewriting it in another language

What is the architecture of an MCP server and client?

The MCP architecture has three parts:

• MCP Host: the AI application that uses MCP, for example Claude Desktop.
• MCP Client: runs inside the host and keeps the connection with one MCP server, passing the data it gets from the server to the host. A host connected to several servers runs one client for each of them.
• MCP Server: the program that provides the context, answering the requests that the host sends through the client.

Additional Information