Agents Index

Sergio by Serviche

OnlineNew

Make sure nothing falls through the cracks in your cleaning business, even when you're not watching.

Visit publisherConnectJSON

What it can do: 80 tools

  • whoami read-onlyReturns this agent seat: its name, role, member id, the organization it belongs to, the key id this call used, whether the owner allowed it to run SQL queries, and what it reads as (readsAs: "owner" when the owner allowe
  • catalog read-onlyReturns `asks`, a short list of things a person can ask (give your user these when they ask what you can do), then lists every tool this seat can call right now, grouped by family, with whether each one changes anything,
  • report_feedbackFiles a bug report or feature request with the Sergio team. It lands in the team's one Feedback inbox, the same place the in-app help bubble's reports go, tagged with this agent seat, and the team is notified the moment
  • events_subscribeCreate or update this seat's one event subscription. inputs: which arrivals (omit for all: text_in, text_out, email_in, email_out, call_answered, call_missed, voicemail, booking_created, booking_changed, booking_cancelle
  • events_list read-onlyReturns the next events for this seat, oldest first, after `cursor` (omit it to continue from your last ack). Each event names an arrival by id (a text, email, call, or booking change); fetch its detail with read(). Deli
  • events_ackStores `cursor` (a next_cursor you received) as this seat's high-water mark, so events_list with no cursor resumes after it. It only moves forward; an older cursor changes nothing.
  • read read-onlyRead ANYTHING about the business: read(entity, filters). ENTITIES (key: purpose [main filters]): conversations: The inbox list of conversations [status, from, to, needs_reply, conversation_id, ...] | conversation_transcr
  • query read-onlyRun a read-only SQL SELECT over the business database and get rows back. It is the FALLBACK, not the first move: when a read(entity) answers the question (leads, clients, conversations, bookings and the rest of read's ca
  • findClientByIdentifier read-onlyLook up a client ID by a single identifier (phone or email). Returns the client ID or null. Simpler than resolveClient. No creation, no merge. Use for a quick check: "is this phone number already a client?".
  • send_textTexts a client or teammate on your person's order, from the business number, as a Manual send under the business's Sending setting. Use it whenever your person asks you to text someone now, with their words or words you
  • start_group_textOpens the one group text thread for 2 to 9 contacts who each have a phone, as the inbox's New conversation with several people checked does (an existing group for the same people is reused). Nothing is sent; texting it i
  • open_conversation_by_phoneOpens (or finds) the one conversation for a phone number nobody is saved under, as the inbox search's Text <number> does. Nothing is sent. Pass the same idempotency_key when retrying.
  • assign_conversationAssigns a conversation to a teammate, as the thread header's Assign menu does: assigned_member_id is the teammate's id (read entity org_members), or null to unassign; assigned_to (the teammate's exact name) is accepted i
  • set_conversation_statusMarks a thread done (status resolved) or reopens it (status new), as the inbox's Done and Reopen do; the Quo inbox follows when the business's write setting allows. A thread that still owes the customer a reply is refuse
  • bulk_clear_conversationsClears every thread older than a cutoff at once, as the inbox's bulk Clear does (owner or admin seats only): mode date clears threads quiet for olderThanDays (default 14) or since cutoff (ISO date); mode leads clears thr
  • snooze_conversationMutes a conversation until snoozed_until (ISO 8601, in the future), at most 10 minutes from now (a later time is cut to 10 minutes), as the inbox's Mute does while someone is on a call. note is optional. For a later foll
  • unsnooze_conversationEnds a conversation's mute now, as the inbox's Unmute does. Pass the same idempotency_key when retrying.
  • set_conversation_reminderAdds a reminder on a conversation, as the thread's bell does: remind_at (ISO 8601) and an optional note become a task due then. hide_until_due: true also tucks the thread away until the reminder is due (a reply from the
  • dismiss_conversation_remindersDismisses every open reminder on a conversation, as the bell's Dismiss does. Pass the same idempotency_key when retrying.
  • link_conversation_to_clientLinks a conversation to a contact, as the inbox's Link to a contact does: if the contact already has a one-to-one thread, it is folded into this one, and an email thread's address is saved to the contact. Sergio learns t
  • merge_conversationsMoves everything in conversation_id (messages, calls, emails, tasks) into target_conversation_id and removes the empty one, as the thread menu's Merge does. It cannot be split back. Pass the same idempotency_key when ret
  • track_conversation_as_leadOpens a lead for this thread's contact, as the thread header's Track this as a new lead does, for a customer asking about new work. request is what they asked for, in a line. Refused when lead follow-up is off, the threa
  • disposition_conversationRecords why a quiet thread needs no reply, as the clear gate's picker does: spam (the contact becomes spam; its lead work stops and its Quo card is tagged when the business's write setting allows), lead (the contact beco
  • start_conversation_flowStarts a flow on a conversation, as the thread's flow picker does: flowId names an active flow (read entity flows); its steps become tasks with deadlines. label is optional. Pass the same idempotency_key when retrying.
  • close_conversation_flowMarks a conversation's flow done, as the flow chip's Mark done does. conversationFlowId names the flow when the thread has more than one. outcome (for example declined) closes it early without marking its steps done; clo
  • remove_conversation_flowTakes one flow off a conversation, as the flow chip's Remove does; its open step tasks are removed. conversationFlowId names the flow. reason is optional. Pass the same idempotency_key when retrying.
  • edit_draftEdits a draft in a conversation's draft box, as a person typing in it does: body, subject (email), whyNote, isReady, or status 'discarded' to throw it away. Nothing is sent; a person still presses Send. draft_id comes fr
  • send_emailEmails a client from the business mailbox on your person's order, as a Manual send under the business's Sending setting. First call without confirm_token: nothing is sent; you get a preview (to, subject and the exact tex
  • create_draftWrites a message into a client conversation's draft box. It never sends: a person on the team reviews the exact text and presses Send in Sergio, where the organization's sending policy applies. Give conversationId, or cl
  • redraft_lead_stepRewrites the text of a lead's upcoming step that a person sends, from the conversation so far, as the journey's Update draft does (one AI draft, billed like the composer's Draft). Refused for a call step, a step Sergio s
  • set_lead_outcomeRecords what happened with a lead, as the lead card's Close menu and taps do. tap: quoted (they have a price); booked (closes it won, on the booking when one for them exists, else on your word); confirmed_booked (the sam
  • move_lead_journeyMoves a lead to another follow-up journey (segmentId, as Settings > Lead follow-ups names them: read the lead program), at the same place in the sequence, as the lead's journey tag does. Pass the same idempotency_key whe
  • hold_follow_upsPuts a lap's automatic follow-ups on hold, as its Hold follow-ups switch does: lead follow-ups, a feedback check-in and a review request all obey the one hold. No step goes out on its own; each is drafted for a person. T
  • hold_lead_follow_upsPuts a lap's automatic follow-ups on hold, as its Hold follow-ups switch does: lead follow-ups, a feedback check-in and a review request all obey the one hold. No step goes out on its own; each is drafted for a person. T
  • edit_lead_stepChanges one step of one lead's follow-ups, as the journey list does. Send one or more of: dueAt (ISO time, or null for the plan's timing; must stay after the step before it), channel ('message', 'email', 'call', 'reply',
  • update_payroll_settingsChanges one payroll setting per call, as Payroll settings on the staff page does: providerPayFallbackPct (0 to 1), providerPayDefault ({ unit: visit or hour, cents }), or payHoursFrom (booked or approved_time_logs). Staf
  • add_staff_memberTo rename someone already on the roster, pass rename_staff_id with the new name; the old spelling keeps pointing at them. Otherwise adds a field worker to the roster, as the staff page's Add staff does: name (a profile w
  • edit_staff_memberChanges one staff member (staff_id, from read staff_roster or staff_detail) as Save in their staff drawer does. Pass only what changes: employmentType (employee reads Staff, contractor reads Contractor), payRateCents wit
  • clear_staff_availability_overrideClears one field worker's schedule change on a date (YYYY-MM-DD), so their normal weekly hours apply again, as Clear on the staff calendar does. To set a change, use set_staff_availability. Nothing is sent. Pass the same
  • set_staff_weekly_hoursReplaces the regular weekly hours of the workers named in staffNames with exactly the windows in entries (day_of_week 0 = Sunday to 6 = Saturday, HH:MM times; several windows a day allowed; a named worker with no entries

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http sergio-by-serviche https://sergio.serviche.com/api/agent/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://sergio.serviche.com/api/agent/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "sergio-by-serviche": {
      "url": "https://sergio.serviche.com/api/agent/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "sergio-by-serviche": {
      "type": "http",
      "url": "https://sergio.serviche.com/api/agent/mcp"
    }
  }
}

Questions

What does Sergio by Serviche do?

Make sure nothing falls through the cracks in your cleaning business, even when you're not watching. It exposes 80 tools to AI assistants.

What tools does Sergio by Serviche provide?

80 tools, including whoami, catalog, report_feedback, events_subscribe, events_list, events_ack, read, query, findClientByIdentifier, send_text, start_group_text, open_conversation_by_phone….

How do I connect Sergio by Serviche to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://sergio.serviche.com/api/agent/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Sergio by Serviche require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Sergio by Serviche online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Sergio by Serviche?

serviche.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Productivity & Docs