# Propertyware MCP connector

The Propertyware connector brings bills, bill payments, bank deposits and building records into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works in Propertyware as themselves with every action logged.

Source: https://elaichi.ai/connectors/propertyware/

## Facts

| | |
| --- | --- |
| Application | Propertyware |
| Category | CRM |
| AI tools | 177 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Propertyware is connected

- List unpaid Propertyware bills for the Maple Street building this month
- Record yesterday's bank deposit for Oakwood Apartments
- Which management fees apply to the Riverside building?

## Connect Propertyware in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Propertyware.
2. Optionally set Share with, then press Connect.
3. Paste a Propertyware API key. One person generates a token in Propertyware and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Propertyware tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Propertyware MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Propertyware MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Propertyware MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Propertyware MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Propertyware MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Propertyware to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Propertyware tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Propertyware through Elaichi

### Enter vendor bills without opening Propertyware

Accounting. Paste the details from a vendor invoice and have the bill created in Propertyware against the right building. Fix a wrong amount or due date later with one plain-language ask.

### Record bill payments after a check run

Accounts payable. Once checks go out, log the whole batch of bill payments in Propertyware at once instead of keying each one. Pull up any single payment by its reference when a vendor calls to ask.

### Reconcile bank deposits against the ledger

Finance. List the deposits recorded in Propertyware for a building and compare them with the bank statement. Create a missing deposit, or remove one that was entered twice.

### Set up recurring auto bills for a building

Property management. Create an auto bill in Propertyware for landscaping, pest control or any fixed monthly service so it posts on its own. Add a bill credit when a vendor issues one.

### Check management fees before an owner call

Owner relations. Ask for the management fees set on a building and see them in seconds, so the conversation with an owner starts from the numbers in Propertyware rather than memory.

### Keep building records and amenities current

Operations. Review the conversations logged against a building, tidy up ones that no longer apply, and update custom fields across many buildings in one go. See which amenities are on record for each property.

## Elaichi vs Zapier MCP vs Composio for Propertyware

All three can connect Propertyware to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Propertyware tools | Allow or restrict single Propertyware tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Propertyware call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Propertyware to Claude?

Connect Propertyware in Elaichi by pasting the API key from your Propertyware account, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Claude then asks you to sign in to Elaichi, and from that point every Propertyware request runs as you.

### Does Propertyware work with ChatGPT and Cursor as well as Claude?

Yes. The same Propertyware connection and the same endpoint, https://api.elaichi.ai/mcp, serve Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Propertyware once in Elaichi and add the endpoint to whichever clients your team uses.

### What can an AI agent actually do with my Propertyware data?

With Propertyware connected, an agent can create and update bills, record bill payments one at a time or as a batch, create bank deposits, add bill credits and auto bills, and look up building amenities, conversations and management fees. It can also update custom fields across many buildings at once. Short, concrete asks such as "list unpaid bills for the Oakwood building" work better than long paragraphs.

### Does connecting Propertyware give the AI access to every building and ledger?

No. Access follows the person who signed in, so an agent working through Propertyware sees only the portfolios, buildings and ledgers that person can already reach in Propertyware. Elaichi can narrow that further with roles and restrictions, and it never widens it.

### Can my team share one Propertyware connection?

Yes. One person connects Propertyware with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created a bill or recorded a deposit, not the account that connected it.

### Can I stop an agent from deleting or changing things in Propertyware?

Yes. Restrictions in Elaichi work per action, so you can allow reading Propertyware bills while restricting deleting a bank deposit or updating a bill payment, set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Propertyware connection when someone leaves?

Offboarding that person in Elaichi ends their access to Propertyware through every client at once. A Propertyware connection that was shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting Propertyware once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

### Does the Propertyware MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Propertyware is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Propertyware?

Yes. Both let Claude, ChatGPT or Cursor use Propertyware. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Propertyware call.

### How is Elaichi different from Composio for Propertyware?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Propertyware: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 177 Propertyware tools

Every tool below is callable through https://api.elaichi.ai/mcp once Propertyware is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Propertyware auto bill** (Create). Create an auto Bill (POST /pw/api/rest/v1/bills/autobills). Creates an auto bill for a vendor. Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: Bills - Write. Required: billSplits, postEveryX, postInterval, postStartDate, postTimesLeft, vendorID.
- **Create a Propertyware bank deposit** (Create). Create a bank deposit (POST /pw/api/rest/v1/accounting/bankdeposits). Creates a bank deposit. Propertyware permission: General Ledger - Write. Required: bankGLAccountID, dateOpened, listOfTxIDs.
- **Delete a Propertyware bank deposit by ID** (Delete). Delete a Bank Deposit (DELETE /pw/api/rest/v1/accounting/bankdeposits/{bankDepositID}). Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: General Ledger - Delete. Returns no content (HTTP 204). Required: id.
- **Create a Propertyware bill credit** (Create). Create a credit (POST /pw/api/rest/v1/bills/credit). Creates a credit. Propertyware permission: Bills - Write. Required: billDate, billSplits, vendorID.
- **Update a Propertyware bill credit by ID** (Update). Update a Credit (PUT /pw/api/rest/v1/bills/credit/{creditID}). Update an existing Credit. Propertyware permission: Bills - Write. Required: id, billDate, billSplits, vendorID.
- **Create a Propertyware bill payment** (Create). Create a Bill Payment (POST /pw/api/rest/v1/bills/payment). Propertyware permission: Vendors - Write. Required: bills, paymentAccountID, paymentDate, paymentMethod, vendorID.
- **Update a Propertyware bill payment by ID** (Update). Partially Update a Bill Payment (PATCH /pw/api/rest/v1/bills/payment/{billPaymentID}). Utilize JSON Merge Patch to selectively update specific fields of a Bill Payment in our REST API, allowing for efficient and precise modifications without altering the entire resource. Partial update: send only the fields to change. Propertyware permission: Vendors - Write. Required: id.
- **Propertyware bill payments replace** (Action). Update a Bill Payment (PUT /pw/api/rest/v1/bills/payment/{billPaymentID}). PUT: a full update; fields left out may be cleared (use update for a partial change). Propertyware permission: Vendors - Write. Required: bill_payment_id, bills, paymentAccountID, paymentDate, paymentMethod, vendorID.
- **List all Propertyware bill payments** (List). Retrieve all bill payments (GET /pw/api/rest/v1/bills/payments). Retrieves a list of bill payments. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Bills - Read.
- **Get single Propertyware bill payment by ID** (Get). Retrieve a bill payment (GET /pw/api/rest/v1/bills/payments/{billPaymentID}). Retrieves a specific bill payment. Propertyware permission: Bills - Read. Required: id.
- **Propertyware bill payments bulk create** (Create). Create bill payments in bulk (POST /pw/api/rest/v1/bills/payments/bulk). Creates bill payments in bulk. Send the records as items (a list). Propertyware permission: Vendors - Write. Required: items.
- **List all Propertyware bills** (List). Retrieve all bills (GET /pw/api/rest/v1/bills). Retrieves a list of bills. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Bills - Read.
- **Create a Propertyware bill** (Create). Create a bill (POST /pw/api/rest/v1/bills). Creates a bill. Propertyware permission: Bills - Write. Required: billDate, billSplits, dueDate, vendorID.
- **Get single Propertyware bill by ID** (Get). Retrieve a bill (GET /pw/api/rest/v1/bills/{billID}). Retrieves a specific bill. Propertyware permission: Bills - Read. Required: id.
- **Update a Propertyware bill by ID** (Update). Partially Update a Bill (PATCH /pw/api/rest/v1/bills/{billID}). Utilize JSON Merge Patch to selectively update specific fields of a Bill in our REST API, allowing for efficient and precise modifications without altering the entire resource. Partial update: send only the fields to change. Propertyware permission: Bills - Write. Required: id.
- **Delete a Propertyware bill by ID** (Delete). Delete a Bill (DELETE /pw/api/rest/v1/bills/{billID}). Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: Bills - Delete. Returns no content (HTTP 204). Required: id.
- **Propertyware bills replace** (Action). Update a Bill (PUT /pw/api/rest/v1/bills/{billId}). Update an existing bill. PUT: a full update; fields left out may be cleared (use update for a partial change). Propertyware permission: Bills - Write. Required: bill_id, billDate, billSplits, dueDate, vendorID.
- **Propertyware bills bulk create** (Create). Create bills in bulk (POST /pw/api/rest/v1/bills/bulk). Creates bills in bulk. Send the records as items (a list). Propertyware permission: Bills - Write. Required: items.
- **List all Propertyware building amenities** (List). Retrieve all building amenities (GET /pw/api/rest/v1/buildings/amenities). Retrieves a list of available amenities for buildings within a Property Management Company. Propertyware permission: Buildings - Read.
- **List all Propertyware building conversations** (List). Retrieve all building conversations (GET /pw/api/rest/v1/buildings/{buildingID}/conversations). Retrieves all the conversations of a building. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Buildings - Read. Required: building_id.
- **Get single Propertyware building conversation by ID** (Get). Retrieve a building conversation (GET /pw/api/rest/v1/buildings/{buildingID}/conversations/{conversationID}). Retrieves a specific building conversation. Propertyware permission: Buildings - Read. Required: building_id, id.
- **Delete a Propertyware building conversation by ID** (Delete). Delete a building conversation (DELETE /pw/api/rest/v1/buildings/{buildingID}/conversations/{conversationID}). Deletes a specific building conversation. Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: Buildings - Delete. Returns no content (HTTP 204). Required: building_id, id.
- **Propertyware building custom fields bulk update** (Update). Update a building custom fields (PUT /pw/api/rest/v1/buildings/customfields). Updates an existing building custom fields. Propertyware permission: Buildings - Write. Returns Propertyware's status object (statusCode and an optional body). Required: entityId, fieldSetDTOS.
- **List all Propertyware building management fees** (List). Retrieves all the management fee rules of a building (GET /pw/api/rest/v1/buildings/{buildingID}/managementfees). Propertyware permission: Buildings - Read. Required: building_id.
- **List all Propertyware building managers** (List). Retrieves all the property managers of a building (GET /pw/api/rest/v1/buildings/{buildingID}/managers). Propertyware permission: Buildings - Read. Required: building_id.
- **List all Propertyware building notes** (List). Retrieves all the notes of a building (GET /pw/api/rest/v1/buildings/{buildingID}/notes). Propertyware permission: Buildings - Read. Required: building_id.
- **List all Propertyware buildings** (List). Retrieve all buildings (GET /pw/api/rest/v1/buildings). Retrieves a list of buildings. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Buildings - Read.
- **Create a Propertyware building** (Create). Create a building (POST /pw/api/rest/v1/buildings). Creates a building. Propertyware permission: Buildings - Write. Required: abbreviation, category, countUnit, name, portfolioID, propertyType, rentable, type.
- **Get single Propertyware building by ID** (Get). Retrieve a building (GET /pw/api/rest/v1/buildings/{buildingID}). Retrieves a specific building. Propertyware permission: Buildings - Read. Required: id.
- **Update a Propertyware building by ID** (Update). Partially Update a Building (PATCH /pw/api/rest/v1/buildings/{buildingID}). Utilize JSON Merge Patch to selectively update specific fields of a building in our REST API, allowing for efficient and precise modifications without altering the entire resource. Partial update: send only the fields to change. Propertyware permission: Buildings - Write. Required: id.
- **Propertyware buildings replace** (Action). Update a building (PUT /pw/api/rest/v1/buildings/{buildingID}). Updates a building. PUT: a full update; fields left out may be cleared (use update for a partial change). Propertyware permission: Buildings - Write. Required: building_id, abbreviation, category, countUnit, name, propertyType, rentable, type.
- **Delete a Propertyware building by ID** (Delete). Delete a building (DELETE /pw/api/rest/v1/buildings/{buildingID}). Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: Buildings - Delete. Returns no content (HTTP 204). Required: id.
- **Propertyware buildings bulk create** (Create). Create buildings in bulk (POST /pw/api/rest/v1/buildings/bulk). Creates buildings in bulk. Send the records as items (a list). Propertyware permission: Buildings - Write. Required: items.
- **List all Propertyware contact categories** (List). Retrieve all contact categories (GET /pw/api/rest/v1/contacts/categories). Retrieves a list of contact categories. Propertyware permission: Contacts - Read.
- **List all Propertyware contact conversations** (List). Retrieve all contact conversations (GET /pw/api/rest/v1/contacts/{contactID}/conversations). Retrieves all the conversations of a contact. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Contacts - Read. Required: contact_id.
- **Get single Propertyware contact conversation by ID** (Get). Retrieve a contact conversation (GET /pw/api/rest/v1/contacts/{contactID}/conversations/{conversationID}). Retrieves a specific contact conversation. Propertyware permission: Contacts - Read. Required: contact_id, id.
- **Delete a Propertyware contact conversation by ID** (Delete). Delete a contact conversation (DELETE /pw/api/rest/v1/contacts/{contactID}/conversations/{conversationID}). Deletes a specific contact conversation. Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: Contacts - Delete. Returns no content (HTTP 204). Required: contact_id, id.
- **Propertyware contact custom fields bulk update** (Update). Update a contact custom fields (PUT /pw/api/rest/v1/contacts/customfields). Updates an existing contact custom fields. Propertyware permission: Contacts - Write. Returns Propertyware's status object (statusCode and an optional body). Required: entityId, fieldSetDTOS.
- **List all Propertyware contacts** (List). Retrieve all contacts (GET /pw/api/rest/v1/contacts). Retrieves a list of contacts. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Contacts - Read.
- **Create a Propertyware contact** (Create). Create a contact (POST /pw/api/rest/v1/contacts). Creates a contact. Propertyware permission: Contacts - Write. Required: firstName, lastName.
- **Get single Propertyware contact by ID** (Get). Retrieve a contact (GET /pw/api/rest/v1/contacts/{contactID}). Retrieves a specific contact. Propertyware permission: Contacts - Read. Required: id.
- **Update a Propertyware contact by ID** (Update). Partially Update a Contact (PATCH /pw/api/rest/v1/contacts/{contactID}). Utilize JSON Merge Patch to selectively update specific fields of a Contact in our REST API, allowing for efficient and precise modifications without altering the entire resource. Partial update: send only the fields to change. Propertyware permission: Contacts - Write. Required: id.
- **Propertyware contacts replace** (Action). Update a contact (PUT /pw/api/rest/v1/contacts/{contactID}). Updates a contact. PUT: a full update; fields left out may be cleared (use update for a partial change). Propertyware permission: Contacts - Write. Required: contact_id, firstName, lastName.
- **Delete a Propertyware contact by ID** (Delete). Delete a contact (DELETE /pw/api/rest/v1/contacts/{contactID}). Deletes a contact. Beta: Propertyware allows this write only for customers in its API beta program (ask Propertyware support). Propertyware permission: Contacts - Delete. Returns no content (HTTP 204). Required: id.
- **Propertyware contacts bulk create** (Create). Create contacts in bulk (POST /pw/api/rest/v1/contacts/bulk). Creates contacts in bulk. Send the records as items (a list). Propertyware permission: Contacts - Write. Required: items.
- **List all Propertyware custom field definitions** (List). Retrieve list of custom field definitions (GET /pw/api/rest/v1/customfields/{entityType}/definitions). Propertyware permission: Custom Field - Read. Required: entity_type.
- **List all Propertyware documents** (List). Retrieve all documents (GET /pw/api/rest/v1/docs). Retrieves a list of documents associated with a specific entity. The connector pages with offset / limit (limit = page size, 1-500, default 100). Propertyware permission: Documents - Read. Required: entityType.
- **Create a Propertyware document** (Create). Upload a document (POST /pw/api/rest/v1/docs). Multipart upload: the file goes in file; entityId and entityType are query fields. Propertyware permission: Documents - Write. Required: entityId, entityType, file.
- **Get single Propertyware document by ID** (Get). Retrieve a document (GET /pw/api/rest/v1/docs/{documentId}). Retrieves the metadata of a specific document. Propertyware permission: Documents - Read. Required: id.
- **Update a Propertyware document by ID** (Update). Update a document (PUT /pw/api/rest/v1/docs/{documentId}). Updates the metadata of a specific document. Propertyware permission: Documents - Write. Required: id, fileName.
- ...and 127 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
