MCP App Store
by KeenEthics
Ruby CRM icon

Ruby CRM MCP Server for ChatGPT

By Ruby CRM

Overview

Ruby CRM connects ChatGPT to a Dubai real estate brokerage's Ruby workspace. Agents can find and review their leads, see which WhatsApp conversations are waiting on a reply, check overdue and upcoming follow-ups, search the brokerage's property inventory, and get property suggestions that fit a lead's brief. They can also update a lead's status and requirements, add call notes, book and complete follow-ups, and draft WhatsApp messages as tap-to-send links that the agent sends themselves. Every result is limited to what the signed-in user's role allows them to see in Ruby.

How to connect

  1. ChatGPT: Open the Ruby CRM listing in the ChatGPT app directory and choose Connect. ChatGPT listing Ruby CRM exposes 27 tools here.

Tools

add_lead_note

ChatGPT
Record what happened on a call or meeting against a lead. Notes are visible to colleagues who can see the lead, so write them as a handover would read.

add_task_checklist_item

ChatGPT
Add a subtask to the end of an existing task's checklist. Only the task's creator or an admin can do this (get_task's editable_fields is null for them); the assignee of someone else's task can only tick items. Confirm the wording with the user first, and refer to the item by its title.

complete_follow_up

ChatGPT
Mark a follow-up done and record how it went. The result note is written onto the lead's timeline, so summarise the outcome rather than just saying 'done'. Completion cannot be undone. Ruby's AI reads a substantive result note and may update the lead's requirements and book, reschedule or cancel their other follow-ups to match — so confirm the outcome with the user before calling this.

complete_task

ChatGPT
Mark a task done. If it repeats, the next occurrence is created and returned as next_task (null for a one-off). Completing a task that is already done changes nothing. Confirm with the user first. Refer to a task by its title and due date; its uuid is the identifier to use when one is needed. Never show its id.

create_follow_up

ChatGPT
Schedule the next contact with a lead. Always confirm the date, time and channel with the user before calling this — the follow-up appears in their calendar and may trigger a reminder. Times are interpreted in the user's timezone, which get_my_context reports.

create_lead

ChatGPT
Create a new lead assigned to the signed-in user. Needs at least a name, phone or email. Before calling: if you have a phone, call find_leads_by_phone; if it returns any lead, tell the user it already exists (Lead #, name, status and assignee, whose name list_team_members gives) and only create after they confirm they want a separate lead. If you have no phone, tell the user no duplicate check was possible. Confirm the details with the user before creating. No WhatsApp is sent to the lead: offer get_whatsapp_send_link if they want to message them. Call a lead 'Lead #<lead_number>' when you refer to it; never show its id.

create_task

ChatGPT
Capture a task. Confirm the title, due date and assignee with the user first. Assigning someone else notifies them, and the task syncs to the assignee's connected Microsoft To Do / Google Tasks. Times are in the user's timezone. Refer to a task by its title and due date; its uuid is the identifier to use when one is needed. Never show its id.

find_leads_by_phone

ChatGPT
Check whether the user already has a lead with this phone number. Call this before create_lead whenever you have a phone. Accepts local or international format. Only leads this user can see are searched: no match does not prove a colleague has no lead for this number, so do not say the number is new to the company. Call a lead 'Lead #<lead_number>' when you refer to it; never show its id.

get_lead

ChatGPT
The full record for one lead, including their stated requirements, AI summary and linked listing. Use after search_leads when you need detail the summary does not carry. Call a lead 'Lead #<lead_number>' when you refer to it; never show its id.

get_listing

ChatGPT
Full details for one property, including its description, terms and photos. Owner details, documents and agreements are never returned. Show image_urls as an image carousel. If you cannot display a carousel, show cover_image_url as the cover image instead. These URLs are the only photos of the property. Never search the web or use image search for photos of a listing — any photo found that way is of a different property. If you cannot display these URLs as images, give them as links, or show no photo at all. Refer to a property by its reference_number (or its title if it has none), never by its id.

get_my_context

ChatGPT
Who you are acting as in Ruby and what this connection can and cannot do. Call this first in a new conversation: the user's role decides which leads and listings every other tool will return, so knowing it avoids promising the user something their permissions do not allow.

get_suggested_properties

ChatGPT
Properties from the workspace's inventory that match a lead's stated budget, size, bedrooms and area. Use this instead of hand-building a search when the question is 'what can I send this lead?' — the matching already reflects how Ruby scores fit. Refer to a property by its reference_number (or its title if it has none), never by its id.

get_task

ChatGPT
One task in full: its notes, reminder, checklist items (with the ids update_task_checklist_item and remove_task_checklist_item need) and editable_fields — the fields the signed-in user may change on it, or null for all of them. For an all-day task (is_all_day), due_at is midnight in the user's timezone: read only its date. Refer to a task by its title and due date; its uuid is the identifier to use when one is needed. Never show its id.

get_whatsapp_conversation

ChatGPT
The message history with one lead, oldest first. Read this before drafting a reply so the message follows what was actually discussed. Identify a conversation by the lead's name and phone number, never by an id.

list_follow_ups

ChatGPT
Scheduled follow-ups visible to the signed-in user. Use is_overdue=true for the chase list, or status='pending' with scheduled_at__gte and scheduled_at__lte spanning today to answer 'what's on for today?'. Pass lead to see one lead's history. Refer to a follow-up by its title and time; its uuid is the identifier to use when one is needed. Never show its id.

list_property_types

ChatGPT
The property types available (apartment, villa, office and so on) with their ids. Use this to resolve a type name into the id that search_listings and search_leads expect. The id is a filter argument only — say 'villa' to the user, never the number.

list_team_members

ChatGPT
The people in this workspace, with their ids, names, roles and teams. Use this to turn a name into an id — for example to filter leads by the agent they are assigned to. Contact details are not included. The id is a filter argument only: refer to a colleague by name, and turn an assignee id in another tool's result back into a name with this tool rather than showing the number.

list_whatsapp_conversations

ChatGPT
Leads with WhatsApp activity, most recent message first, so you can answer the question agents ask most: 'who is waiting on a reply from me?'. Use conversation_state='needs_reply' for conversations where the customer spoke last, and 'awaiting_reply' for ones where we did and they have not come back. Any search_leads filter narrows it further. Identify a conversation by the lead's name and phone number, never by an id.

remove_task_checklist_item

ChatGPT
Remove a subtask from a task's checklist; the items after it move up. Only the task's creator or an admin can do this (get_task's editable_fields is null for them); the assignee of someone else's task can only tick items. Name the item by its title and confirm with the user before removing it. Returns the removed item.

search_leads

ChatGPT
Find leads assigned to or visible to the signed-in user. This is the main way to answer questions like 'which leads haven't I replied to?', 'who is overdue for a follow-up?' or 'show me hot buyers in JVC under 2M'. Results are limited to what this user is allowed to see — an agent sees only their own leads. Returns a summary per lead; call get_lead for the full record. Call a lead 'Lead #<lead_number>' when you refer to it; never show its id.

search_listings

ChatGPT
Find properties in this workspace's inventory — for matching a buyer's brief, checking what is live, or finding a specific unit. Results are limited to listings the signed-in user may see. Pass a reference the user quotes to search — that is how a reference number resolves to a listing. When you present a listing, show its cover_image_url as the listing's cover image; skip it silently when it is null. These URLs are the only photos of the property. Never search the web or use image search for photos of a listing — any photo found that way is of a different property. If you cannot display these URLs as images, give them as links, or show no photo at all. Refer to a property by its reference_number (or its title if it has none), never by its id.

search_locations

ChatGPT
Find Dubai areas by name. A result's id is what search_leads takes as preferred_areas; its pf_location is what search_listings takes as location. Call this before filtering leads by area — guessing an id will not work. Both are filter arguments only — name the area to the user, never the number.

search_tasks

ChatGPT
Tasks visible to the signed-in user (agents see tasks assigned to or created by them; managers also their team's; admins everything). Use date_filter='my_day' for 'what's on today?', 'overdue' for the chase list, lead=<id> for one lead's tasks. Returns a summary per task; call get_task for notes and the checklist. For an all-day task (is_all_day), due_at is midnight in the user's timezone: read only its date. Refer to a task by its title and due date; its uuid is the identifier to use when one is needed. Never show its id.

update_lead

ChatGPT
Change a lead's status or recorded requirements after speaking to them. Only the fields you pass are changed. You cannot reassign a lead to a different agent with this tool. Confirm with the user before changing a lead's status.

update_task

ChatGPT
Change a task. Only the fields passed change, and at least one must be passed or named in clear. To remove a due date, reminder, linked lead or listing, or the notes, name the field in clear; passing null or an empty value does nothing. On a task someone else created, the assignee can change or clear only status, reminder_at and is_important — editable_fields from get_task says which applies. status='done' completes the task (a recurring task spawns its next occurrence); moving it out of done reopens it. Confirm before reassigning, changing a due date, or clearing anything. Refer to a task by its title and due date; its uuid is the identifier to use when one is needed. Never show its id.

update_task_checklist_item

ChatGPT
Tick a subtask off (is_done=true) or untick it, or rename it; pass at least one of is_done and title. The assignee of someone else's task can only tick. Take item_id from get_task's checklist_items, and refer to the item by its title.

Capabilities

WritesInteractive

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/ruby-crm"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/ruby-crm)