PropertyMe
PropertyMe v1.0.0
Explore PropertyMe data
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Onboarding example
I'm about to call [contact name]. Give me a quick briefing of what they might want to discuss.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.
Description
From the marketplace listing
Connect your PropertyMe account via the AiMe Connect MCP server to explore portfolio information in everyday language. Review team workload and open tasks, find properties and contacts, monitor lease renewals and tenancy dates, track inspections and maintenance jobs, and more. Ask questions across your PropertyMe Advanced portfolios to identify upcoming expiries, overdue actions, work that needs attention, and completed activities. AiMe Connect uses your existing access permissions and is designed for property managers across Australia and New Zealand.
Language: English · Automatically detected from descriptions.
Matches for “task manager”
Exact text from the indicated source. A mention alone does not establish support for your task.
Publisher description
Connect your PropertyMe account via the AiMe Connect MCP server to explore portfolio information in everyday language. Review team workload and open tasks, find properties and contacts, monitor lease renewals and tenancy dates, track inspections and maintenance jobs, and more. Ask questions across your PropertyMe Advanced portfolios to identify upcoming expiries, overdue actions, work that needs attention, and completed activities. AiMe Connect uses your existing access permissions and is designed for property managers across Australia and New Zealand.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Oct 27, 2026. Last seen Nov 17, 2026.
Similar plugins
Similar plugins could not be prepared right now. Please try again in a moment.
Browse plugins →Files & skills
File archives
Skill instructions
propertyme-mcp7.58 KB
---
name: propertyme-mcp
description: >-
PropertyMe AiMe Connect MCP server — how to use its tools effectively as a property management assistant.
Use this skill whenever the user mentions PropertyMe, property management, portfolios,
properties, contacts, jobs, tasks, inspections, lease renewals, or team members in the context
of the PropertyMe AiMe Connect MCP server. Covers domain terminology, tool workflows, presentation rules,
and entity relationships. Trigger even if the user doesn't explicitly say "MCP" — most
questions about their PropertyMe data need this guidance.
---
# PropertyMe AiMe Connect MCP
PropertyMe's AiMe Connect MCP server exposes property management data (properties, contacts, jobs, tasks,
inspections, lease renewals, portfolios, team members) as tools that can be called. This skill
covers **using the tools well**.
## Creating a session
Every session must start with `create_session`. It returns a `sessionId` that must be carried on
every subsequent tool call as the `Mcp-Param-SessionId` header. The session is created against
the user's default portfolio; call `set_portfolio` to switch to a different one.
## Switching portfolios
If you belong to multiple property management businesses (portfolios), use `set_portfolio` to
switch the active context. All subsequent tool calls operate against the selected portfolio's
data. Check which is active with `list_portfolios` — the one with `IsCurrent = true` is active.
## Domain glossary
Speak the user's language. Never use internal field names.
| Term | What it means | Do not say |
|---|---|---|
| **Portfolio** | A property management agency or business entity | "customer" |
| **Property** | A managed property (residential or commercial) | "lot" |
| **Contact** | A person or organisation — owner, tenant, supplier, or agency | — |
| **Job** | A maintenance or repair work order against a property | — |
| **Task** | A to-do item (not a job — tasks are lighter, no supplier/access workflow) | — |
| **Inspection** | A property inspection (Routine, Entry, Exit, or Open) | — |
| **Lease renewal** | The workflow of renewing a tenancy agreement (owner + tenant sign-off) | — |
| **Team member** | A staff user of the property management business (Admin, Standard, Limited, Read-only) | "member" alone |
### Key workflows
**1. Always verify the active portfolio first.**
Before querying data, confirm which portfolio the session is operating in. Call `list_portfolios`
and check which one has `IsCurrent = true`. If the user names a specific portfolio, verify it's
the active one — if not, offer to switch with `set_portfolio`.
**2. "My" queries — resolve the current user first.**
When the user says "my tasks," "jobs assigned to me," or "my inspections," call `get_current_user`
first to get their `MemberId`, then match it against the `ManagerMemberId` field on the returned
records.
```
User: "What jobs are assigned to me?"
1. get_current_user → MemberId = <guid>
2. list_jobs → filter results where ManagerMemberId == MemberId
3. Present matching jobs (address, summary, priority, due date, status)
```
**3. Search before get.**
Most list/search tools return summary records (id + key fields). Use search to find what the user
is looking for, then `get_*` with the id for full details. Search returns max 2000 results — if
there are more, ask the user to refine their search. When the user wants a report (e.g. "all
properties", "all jobs"), use `list_*` and page through results instead of `search_*` — search is
for finding a specific record, not enumerating datasets.
```
User: "Show me the details for the Smith property"
1. search_properties("Smith") → get the property id
2. get_property(id) → full details (address, bedrooms, bathrooms, etc.)
```
**4. Pagination.**
All list tools use `offset` (default 0) and `limit` (default 2000, maximum 2000). Page through by
incrementing offset by 2000. If search returns exactly 2000 results, there maPreview of the first 4,000 characters. Read full instructions →
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- PropertyMe
Package observed Nov 17, 2026.
Technical details
- First seen
- Oct 27, 2026 · 06:00 UTC
- Last seen
- Nov 17, 2026 · 18:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ac7200537dc819196816a1201ece845
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.