residenceportal-interface-mcp
Provides an interface layer to access detailed operational data resident within the BuildingLink ecosystem, encompassing resident profiles, vendor registries, pending consignments, official advisories, and scheduled happenings. Enables the extraction of tailored occupant and property datasets for building advanced, context-aware applications.
Author

johnagan
Quick Info
Actions
Tags
BuildingLink Interfacing Conduit (MCP)
This component acts as a specialized Machine Communication Protocol (MCP) server interfacing directly with the BuildingLink infrastructure.
It facilitates the systematic extraction of proprietary BuildingLink information streams for consumption by Large Language Models (LLMs) or other connected agents.
Available Data Access Points (Tools)
This MCP service exposes the following specific data retrieval functionalities:
| Function Name | Purpose |
|------------------|-------------------------------------------------------------------|
| fetchResidentDetails | Retrieves the profile information for the currently authenticated resident. |
| queryPreferredSuppliers | Returns a curated registry of recognized service providers/vendors. |
| obtainAuthCredential | Fetches the current authentication token utilized by the session. |
| enumerateManagedProperties | Lists all physical properties (buildings) linked to the active user account. |
| lookupUserIdentity | Gathers the comprehensive BuildingLink profile data for the active user. |
| retrieveIncomingShipments | Accesses a log of all recent and pending package deliveries for the resident. |
| accessRepositoryIndex | Provides a catalog of all archived or shared library resources for the user/property. |
| fetchOfficialNotices | Obtains all official communications or advisories pertinent to the resident and location. |
| queryScheduledActivities | Retrieves the itinerary of community or building-specific planned occurrences (events). |
Operational Configuration Mandates
The linkage parameters for this MCP server must be defined within the host configuration file under the mcpServers designation.
Authentication credentials (username and password) must precisely match those used for direct portal access via the BuildingLink web interface.
{
"mcpServers": {
"buildinglink": {
"command": "npx",
"args": ["-y", "johnagan/buildinglink-mcp"],
"env": {
"BUILDINGLINK_USERNAME": "your-credential-id",
"BUILDINGLINK_PASSWORD": "your-secret-key"
}
}
}
}
