rex_get_user_profile
Get the signed-in Rex user
The Rex user this server is signed in as: user id, name, email, whether they own the account, position and default office. Good first call. POST /v1/rex/UserProfile/read.
无需输入参数。
io.usefulapi由 usefulapi.io 发布官方发布者v1.8.4更新于 Nov 7, 2026
Read contacts, listings, tenancies and tasks; create a person contact, note or reminder.
发布方自己的服务:Ably MCP by usefulapi
把助手连接到 Rex Software 房产 CRM:搜索并读取联系人、房源、物业、线索、租约和交易,并可新建联系人、备注或提醒。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.usefulapi%2Frex-software/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"rex-software-by-usefulapi": {
"type": "http",
"url": "https://rex-software.usefulapi.io/mcp"
}
}
}https://rex-software.usefulapi.io/mcp.claude mcp add --transport http rex-software https://rex-software.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Rex Software credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/rex-software/
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with rex_upgrade (it returns a Stripe Checkout link). Cancel any time with rex_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running rex_upgrade before then undoes the cancel. Or write to [email protected].
MIT
Use a dedicated agency-invited integration user with only the privileges needed. It may consume a paid agency seat. Rex Verified Integrator status covers seat-fee benefits and sandbox eligibility; this connection uses the documented ordinary live-account integration flow. Choose Australia/New Zealand or the UK and, if needed, an account id. Vendor charges are separate.
Credentials are encrypted. Requested contacts, property and tenancy details, notes and tasks reach the connected AI client and its LLM provider. Connect only records you are authorized to process there. Disconnect UsefulAPI to stop its connection. Password changes stop new sign-ins; issued tokens may remain valid until vendor expiry/revocation. We request one-hour tokens, but API activity can extend them. Billing follows Rex user id and region across that user's accounts.
Only three writes are exposed: create a person contact, an internal note or a reminder. They require a positive created id to report success. No operation is automatically replayed; check Rex before repeating an uncertain create. Notes/reminders may be visible to agency colleagues and interact with configured workflows. No message-send API is exposed. Reminder completion remains unavailable pending a verified success response.
All 33 tools were checked against current vendor documentation and local mocks. No real customer reads or business writes were tested.
来源:servers/rex-software/README.md,提交 4046075
Get the signed-in Rex user
The Rex user this server is signed in as: user id, name, email, whether they own the account, position and default office. Good first call. POST /v1/rex/UserProfile/read.
无需输入参数。
List the Rex accounts the user can access
The Rex agency accounts (account_id and name) this user can sign in to. A user with several accounts picks one with the Account id field when connecting. POST /v1/rex/UserProfile/getAccessibleAccounts.
无需输入参数。
List the search fields of a Rex service
The field names a search on the given service accepts in criteria, each with its label, type and (for enums) the value list. Call this before building criteria on a field you are not sure of. Sorting (order_by) uses a separate list of sortable fields whose names can differ (for example name_last, not contact.name_last): set include_order_by to get it. POST /v1/rex/<Service>/describeSearchFields (and <Service>/describeModel for include_order_by).
matchservice必填include_order_byList the Rex value lists
The names of Rex's value lists (the allowed ids for fields such as note types, reminder types, lead sources and property categories). Use a name with rex_get_value_list. POST /v1/rex/SystemValues/getValueCategories.
无需输入参数。
Get the values of a Rex value list
The allowed values (id and label) of one value list, for example property_category. The ids are what writes and criteria expect. POST /v1/rex/SystemValues/getCategoryValues.
list_name必填Find contacts by name
Quick lookup of contacts by (part of) a name: returns the best matches with id, name, email and phone. Use the id with rex_get_contact. POST /v1/rex/Contacts/autocomplete.
limitsearch_string必填Find listings by address
Quick lookup of listings by (part of) an address: returns the best matches with listing id and address. Use the id with rex_get_listing. POST /v1/rex/Listings/autocomplete.
limitsearch_string必填listing_statesSearch contacts
Search contacts (people and companies). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: contact.name_full, contact.name_first, contact.name_last, contact.email_address, contact.phone_number, contact.type, contact.tags, contact.interest_level, contact.last_contacted_date, system_modtime. To find someone by name, rex_autocomplete_contacts is simpler. POST /v1/rex/Contacts/search.
limitoffsetcriteriaorder_bysearch_stateSearch listings
Search listings (properties for sale or rent). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: listing.system_listing_state (for example "current"), listing.system_publication_status, listing.price_match, listing.listing_agent_id, listing.listing_category_id, property.adr_suburb_or_town, property.adr_postcode, property.adr_street_name, property.attr_bedrooms. To find a listing by address, rex_autocomplete_listings is simpler. POST /v1/rex/Listings/search.
limitoffsetcriteriaorder_bysearch_stateSearch properties
Search properties (the physical addresses behind listings, appraisals and tenancies). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: property.system_search_key, property.adr_suburb_or_town, property.adr_postcode, property.adr_street_name, property.attr_bedrooms, property.attr_bathrooms. POST /v1/rex/Properties/search.
limitoffsetcriteriaorder_bysearch_stateSearch leads
Search leads (enquiries from portals, the website and email). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: lead.contact_id, lead.listing_id, lead.property_id, lead.assignee_id, lead.lead_source_id, lead.lead_status_id, lead.system_completed_time, system_ctime. POST /v1/rex/Leads/search.
limitoffsetcriteriaorder_bysearch_stateSearch appraisals
Search appraisals (listing presentations / market appraisals). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: appraisal_date, appraisal_state, appraisal_type_id, agent_id, property_id, listing_id, pipeline_stage_id, expected_close_date, price_asking. POST /v1/rex/Appraisals/search.
limitoffsetcriteriaorder_bysearch_stateSearch tenancies
Search tenancies (property management leases). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: id, property_id, system_record_state, lease_current_expiry, crt.contact_id. POST /v1/rex/Tenancies/search.
limitoffsetcriteriaorder_bysearch_stateSearch reminders and tasks
Search reminders (follow-up tasks) linked to contacts, properties and listings. Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: reminder_date, system_completed_time, remindee_user_id, contact_id, property_id, listing_id, reminder_type_id, priority_id. Open reminders have no system_completed_time (type is, value Null). POST /v1/rex/Reminders/search.
limitoffsetcriteriaorder_bysearch_stateSearch appointments
Search appointments (calendar items such as inspections and meetings). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). The searchable fields follow Reminders (reminder_date, remindee_user_id, contact_id, property_id, listing_id). Call rex_describe_search_fields with service Appointments for the full list. POST /v1/rex/Appointments/search.
limitoffsetcriteriaorder_bysearch_stateSearch notes
Search notes recorded against contacts and properties. Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: system_ctime, system_created_user_id, id. Call rex_describe_search_fields with service Notes for related contact and property fields. POST /v1/rex/Notes/search.
limitoffsetcriteriaorder_bysearch_stateSearch deals
Search deals (the sales pipeline). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: deal.deal_state, deal.expected_close_date, deal.archive_date, deal.tags, deal.description. POST /v1/rex/Deals/search.
limitoffsetcriteriaorder_bysearch_stateSearch activities
Search activities (the log of calls, emails and other actions on records). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: parent_object_type, parent_object_id, type_id, system_ctime, system_created_user_id. POST /v1/rex/Activities/search.
limitoffsetcriteriaorder_bysearch_stateSearch listing events
Search listing events (open homes and inspections). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Call rex_describe_search_fields with service ListingEvents for the searchable fields. POST /v1/rex/ListingEvents/search.
limitoffsetcriteriaorder_bysearch_stateSearch users
Search the users (staff) of the agency account. Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: first_name, last_name, email, status, user_group_id. User ids are used elsewhere as agent, assignee and remindee ids. POST /v1/rex/AccountUsers/search.
limitoffsetcriteriaorder_bysearch_stateSearch campaigns
Search campaigns (nurture and marketing campaigns with their members). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Call rex_describe_search_fields with service Campaigns for the searchable fields. POST /v1/rex/Campaigns/search.
limitoffsetcriteriaorder_bysearch_stateGet a contact
One contact by id (names, emails, phones, addresses, tags, relationships and the related properties and listings). The id comes from a search or autocomplete. POST /v1/rex/Contacts/read.
id必填fieldsGet a listing
One listing by id (state, price, agents, the property with its attributes, images, related contacts and events). The id comes from a search or autocomplete. POST /v1/rex/Listings/read.
id必填fieldsGet a property
One property by id (address, attributes (bedrooms, land area and so on), features, owners and the property's history). The id comes from a search or autocomplete. POST /v1/rex/Properties/read.
id必填fieldsGet a lead
One lead by id (contact, source, status, assignee and the original enquiry). The id comes from a search or autocomplete. POST /v1/rex/Leads/read.
id必填Get an appraisal
One appraisal by id (date, state, agents, property, price expectations and commission estimate). The id comes from a search or autocomplete. POST /v1/rex/Appraisals/read.
id必填Get a tenancy
One tenancy by id (property, tenants, lease dates and rent). The id comes from a search or autocomplete. POST /v1/rex/Tenancies/read.
id必填Get a note
One note by id (text, type and the contacts and properties it is linked to). The id comes from a search or autocomplete. POST /v1/rex/Notes/read.
id必填Get a deal
One deal by id (state, value, parties and expected close date). The id comes from a search or autocomplete. POST /v1/rex/Deals/read.
id必填Get a reminder
One reminder by id (description, date, remindee, completion state and linked records). The id comes from a search or autocomplete. POST /v1/rex/Reminders/read.
id必填Create a person contact
WRITE: create a new person contact in Rex with a name and optionally one email and one phone. Search first (rex_autocomplete_contacts) to avoid duplicates. Not retried. Returns the new contact id. POST /v1/rex/Contacts/create.
emailphonelast_name必填first_name必填phone_typeCreate a note
WRITE: add a note to one or more contacts and/or properties (for example after a call or an open home). Not retried. Returns the new note id. POST /v1/rex/Notes/create.
note必填note_typecontact_idsproperty_idsupdate_last_contactedCreate a reminder
WRITE: create a follow-up reminder (task) due on a date, optionally linked to a contact, property or listing and assigned to a user (default: Rex's default remindee). Not retried. Returns the new reminder id. POST /v1/rex/Reminders/create.
date必填prioritycontact_idlisting_iddescription必填property_idreminder_typeremindee_user_id已满足适用检查项的 100%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
io.usefulapi官方发布者
面向 Ably 实时消息的托管 MCP 服务器:查看频道历史、在线状态与占用情况,发布消息,并查看应用用量与配置。
io.usefulapi官方发布者
托管式只读 MCP 服务器,让助手查询 Woffu 公司的用户、劳动合同、部门和办公地点。
io.usefulapi官方发布者
面向 White Label Loyalty 的托管 MCP 服务器:浏览奖励、查看客户积分钱包与等级进度,并用积分购买奖励。
io.usefulapi官方发布者
托管的 Weekdone 连接器,让助手读取周报、团队、目标与 KPI,并新增报告条目、评论和 KPI 数值。
io.usefulapi官方发布者
托管式只读 MCP 服务器,让助手列出 WebinarKit 的网络研讨会、场次时间、系列、会议以及白标子账户。
{ "mcpServers": { "rex-software": { "url": "https://rex-software.usefulapi.io/mcp" } }}