Skip to main content
Glama
stan13

ripper-mcp

by stan13

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_contacts

Search the user's contacts by name, email, or phone and return matching contacts with their ids. Call this first to get a contactId before updating a contact, creating a task for a contact, or logging a timeline event. Omit the query to list recent contacts.

create_contactB

Create a new contact. Provide whatever details are known — every field is optional, but include at least a name.

update_contactA

Update details on an existing contact. Only include the fields you want to change. Use find_contacts first to get the contactId.

create_taskA

Create a task / to-do. Optionally link it to a contact by passing contactId (from find_contacts).

add_timeline_eventA

Log a timeline activity — a phone call, text, meeting, video call, or note. Attach it to a contact (contactId), a listing (listingId), or both. Pass at least one. Use find_contacts / find_listings first to get the id.

list_timeline_eventsA

List a contact's recent timeline events with their ids. Call this to get an activityId before editing or deleting a timeline event. Use find_contacts first to get the contactId.

update_timeline_event

Edit an existing timeline event. Only include the fields you want to change. Use find_contacts then list_timeline_events to get the activityId.

delete_timeline_eventA

Delete a timeline event. Use find_contacts then list_timeline_events to get the activityId. Only delete when the user clearly asks to remove an event.

create_noteA

Save freeform context about a contact that doesn't fit a structured field — budget/price range, motivation, financing, preferences, whether they're represented, reactions, etc. Use this liberally so nothing the user mentions is lost. Use find_contacts first to get the contactId.

get_contactA

Read the full detail of one contact — their fields plus their notes, tasks, listings, and recent timeline. Use this to answer questions about a person or to check what's already recorded before writing. Get the contactId from find_contacts.

list_notesA

List the saved notes on a contact so you can recall context you or the agent captured earlier. Use find_contacts first to get the contactId.

list_tasksA

List tasks / to-dos. By default returns open (incomplete) tasks. Filter by contact, due-date window, priority, or category to answer questions like 'what's due this week?' or 'what's open for this client?'.

complete_taskA

Mark a task done (or reopen it). Use list_tasks to get the taskId. Set completed=false to reopen.

update_taskA

Change fields on an existing task — reschedule (dueDate), reprioritize, re-title, recategorize, or relink to a contact. Only include what changes. Use list_tasks to get the taskId.

delete_taskA

Delete a task. Use list_tasks to get the taskId. Only delete when the user clearly asks to remove it (to just finish it, use complete_task).

find_listingsA

Search the user's property listings by address/city/MLS/description, and/or filter by status, owning contact, or a DATE WINDOW. Returns listings with their ids, owner, and key dates (listDate/expirationDate/saleDate). This is the tool for vague temporal questions about listings — e.g. 'which listing is going live this week' → dateField listDate with dateFrom/dateTo covering this week (optionally status coming-soon); 'what's expiring this month' → dateField expirationDate; 'what closed in June' → dateField saleDate. Also call it to get a listingId before updating a listing or logging a listing event.

get_listingA

Read the full detail of one listing — all property/pricing fields, its owner contact, and its recent timeline. Get the listingId from find_listings.

create_listingA

Create a property listing for a client. Requires the owning contactId (use find_contacts, or create_contact for a new client) and a street address. Provide whatever else is known; status defaults to coming-soon.

update_listingA

Update a listing — including moving it through the pipeline (e.g. set status to pending or sold, with saleDate/salePrice). Only include the fields you want to change. Use find_listings first to get the listingId.

search_crmA

Search across the whole CRM — contacts, listings, tasks, notes, and timeline events — in one call, with each result carrying its linked records (a timeline event includes who it was with and which listing; a listing includes its owner). Use this for recall and cross-record questions like 'who did I meet at the open house last weekend' (filter timeline by dateFrom/dateTo and a keyword like 'open'), 'what listings does this client have', or 'find everything about 123 Maple St'.

find_emailsA

Search or list the user's synced email. Pass a query to full-text search subject + body across the whole mailbox, and/or filter by folder, contactId (email from/to that contact), unreadOnly, starredOnly, or a date window (dateFrom/dateTo). Returns matching emails with their ids, sender, subject, date, folder, read/starred flags, and a snippet. This is the tool for 'did X email me', 'what's unread in my inbox', 'show me emails from this client', or 'find that email about the inspection'. Get an emailId here before get_email / update_email / delete_email.

get_emailA

Read one email in full — headers, folder/read/starred flags, attachment list, the full body text, and its linked contact. Get the emailId from find_emails.

send_emailA

Compose an email and either send it or save it as a draft. Set draft true (the DEFAULT unless the user clearly says to send now) to save to the Drafts folder without sending; set it false only when the user explicitly asks to send. Requires a connected email account (see list_email_accounts). Direct sending is supported for Outlook accounts; for other providers the message is saved as a draft. The recipient is auto-linked to a matching contact when one exists.

update_emailA

Triage an email: mark it read/unread, star/unstar, flag important, move it to a folder (inbox/sent/archive/trash/draft — use trash to remove it from the inbox), or link/unlink it to a contact. Only include the fields you want to change. Get the emailId from find_emails.

delete_email

Permanently delete an email. Only do this when the user clearly asks to delete it — to just clear it from the inbox, use update_email with folder trash instead. Get the emailId from find_emails.

list_email_accounts

List the user's connected email accounts (address, provider, which is default, whether sync is on). Use this to check whether email is set up before composing, or to pick an account to send from.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stan13/ripper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server