ResMan MCP Server

What is the ResMan MCP server?

The ResMan MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write leasing, resident, accounting, maintenance, and compliance data in ResMan through a standard protocol.

In short: ResMan is a cloud multifamily property-management platform connecting front-office leasing, back-office accounting, maintenance and turns, resident portals, and affordable-housing compliance across management teams, residents, prospects, and vendors.

ResMan doesn't ship an official MCP server, and ResMan offers limited bulk exports and partner-gated or costly APIs (teams often resort to scheduled CSVs and manual reports), and key flows live in role-aware portals. Supergood builds and maintains the connector by reverse-engineering ResMan's authenticated web flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.

What you can do with ResMan via MCP

Once connected, an agent can:

• List properties, buildings, units, and floorplans with availability.
• Pull prospects, guest cards, applications, and screening results.
• Look up leases and households: primary resident, roommates, occupants, pets, vehicles.
• Retrieve charges and payments: codes, recurring charges, ledgers, deposits, batches.
• Create and track work orders and inspections, including make-ready boards.
• Pull vendors, purchase orders, and vendor bills.
• Surface affordable-housing compliance data: certifications, HUD/LIHTC, HAP and household data.

How to connect ResMan to Claude, ChatGPT & Cursor

Connecting works like any other MCP server. The short version:

• Claude (Desktop or claude.ai): add the ResMan MCP server under Settings → Connectors (or your MCP config), authorize the ResMan account Supergood provisions, and the tools show up in any chat, including agent runs.
• ChatGPT: add it as a connector under Settings → Connectors, authorize, and ChatGPT can call the ResMan tools in conversations and in agent mode.
• Cursor: add the server to your MCP config (mcp.json or Settings → MCP), reload, and the tools are available to the agent.

Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.

How Supergood builds the ResMan MCP server

Supergood doesn't wait for ResMan to ship an API. We reverse-engineer the authenticated web flows behind ResMan, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.

• Auth and MFA, handled. Supergood provisions a dedicated ResMan account (email and phone managed by us) and keeps the session alive through MFA, token expiry, and re-auth.
• Normalized data. Responses come back in consistent JSON shapes across modules, not the raw shape ResMan's front-end happens to return.
• Monitored and adapted. When ResMan changes its web UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
• Reports into APIs. Where ResMan offers only long-running report exports, Supergood orchestrates them into synchronous or webhook-driven calls so the agent gets an answer, not a queued job.

Getting Started

• Schedule Integration Assessment

Book a 30-minute call to confirm which ResMan modules and workflows you need and how authentication should work.

• Supergood Builds and Validates Your MCP Server

We deliver a hardened ResMan connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.

• Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as ResMan changes.