MCP Registry
Eight MCP servers expose the Real Estate Agency's back-office systems as tools - for agents, assistants, and anything else that speaks the Model Context Protocol.
Why a Registry
A language model doesn't need an interface description, it needs tools: clearly named calls with clearly named parameters. The Model Context Protocol (MCP) is the format for that.
The servers in this registry don't exist alongside the APIs, they're built from them. If you know the APIs, you'll find the same operations here - just as a tool instead of an endpoint. What applies to the API catalog therefore applies here too: the same error format, the same authentication, the same permissions.
The Kong AI Gateway sits in front either way. It decides who may call which server and which tool, logs every call, and keeps the tool list current.
MCP Servers for Developers
This list comes directly from the Konnect MCP registry real-estate-agency. It always shows the published state - when a server is added, it appears here without this page needing to change.
Commission Settlement
1.0.0
Retrieve commission settlements and pre-calculate the commission.
Geo Portal
1.0.0
Query zoning plans, noise maps and protected-area designations.
Land Value Index
1.0.0
Query official land value indices for a location.
Leads & Prospects
1.0.0
Manage prospects and inquiries, find search profiles that match a property.
Market Valuation
1.0.0
Determine market values, comparable sales and rent-index figures for a property.
Property Management
1.0.0
List, retrieve, create and update properties in the agency portfolio.
Title Deed Extract
1.0.0
Retrieve encumbrances and restrictions for a parcel of land.
Viewing Appointments
1.0.0
Schedule and reschedule viewings, check open time slots and log feedback.
Real Estate Agency Back-Office Systems
These servers expose the agency's own APIs as tools. Each entry is reachable at its path on the gateway.
| Server | Path | Tools |
|---|---|---|
| Property Management | /mcp/property-management | list-propertiesget-propertycreate-propertyupdate-propertylist-media |
| Leads and Prospects | /mcp/leads | list-leadsget-leadlog-inquiryget-inquiry-scorematching-leads |
| Viewing Appointments | /mcp/viewing-appointments | list-appointmentscreate-appointmentreschedule-appointmentavailable-timeslotslog-feedback |
| Market Valuation | /mcp/market-valuation | request-valuationget-valuationquery-comparablesquery-rent-index |
| Commission Settlement | (tool library) | list-settlementsget-settlementcalculate-commission |
Commission Settlement is deliberately set up without its own endpoint. It serves as a library that other servers draw their tools from - settlement data shouldn't accidentally end up on an open endpoint.
Connected Third-Party Systems
These servers already speak MCP. The gateway passes them through unchanged and adds access control and logging.
| Server | Path | What it's for |
|---|---|---|
| Land Value Index | /land-value-index | Official land value indices for a location |
| Title Deed Extract | /mcp/title-deed-extract | Encumbrances and restrictions for a parcel of land |
| Geo Portal | /mcp/geo-portal | Zoning plans, noise maps and protected-area designations |
Third-party systems get the same access control as the agency's own servers. A key that isn't allowed to see title-deed data doesn't even get that tool shown in its list.
From the Spec, Not Beside It
The back-office tools are generated from the same OpenAPI specifications that feed the API catalog. When an endpoint changes, the tool changes with it - there's no second description that can drift out of date.
Permissions per Tool
Access is controlled not just per server, but per tool. A read-only key gets list-properties but not update-property - and sees the difference right in the tool list.
Every Call Is Traceable
The gateway logs which key called which tool when, and with what result. For an agent that decides on its own, that's not a nice-to-have, it's the prerequisite.
Access: MCP servers are called with the same API key as the other interfaces. To learn how to generate a key, see Authentication. The gateway's base address depends on the environment - the paths above stay the same across all environments.
Server Operating Modes
An MCP server in the gateway is always one of several operating modes. Three of them are in use for the Real Estate Agency:
| Mode | What it does | In use here |
|---|---|---|
conversion-listener | Translates a REST API into tools and accepts MCP requests | The four back-office systems |
conversion-only | Translates a REST API into tools without being reachable itself | Commission Settlement |
passthrough-listener | Passes a third-party MCP server through without changing its tools | The three third-party systems |
If you want to rebuild the servers yourself, the full declarative configuration is in the repository under ai-gateway/config/mcp-servers.yaml.
Ready for Your First Integration?
Register, create an application, and generate your first listing in under ten minutes.