io.usefulapi/robly · v1.0.0 · sales-and-crm
Robly MCP by usefulapi is healthy: it completed an MCP handshake in 930 ms and exposes 13 tools.
Find Robly contacts and lists; subscribe, update and move contacts between lists.
Endpoint: https://robly.usefulapi.io/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 13 |
| Latency | 930 ms |
| Last checked (UTC) | 2026-10-24T11:30:16.787Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-24T11:30:16.787Z | Healthy | 930 |
robly_list_contacts | List contacts (members) of the Robly account, newest first as Robly orders them: id, email, subscribed/deleted flags, subscription date, sign-up source, timestamps. Filter by status, by list, or by last-updated time; optionally include each contact's lists and data fields. Pages with limit (max 100) |
robly_find_contact | Look up one contact by email address or member id: status, subscription date, sign-up source and, on request, the lists and data fields. Returns found: false when Robly has no such contact. GET /api/v1/contacts/search. |
robly_check_list_membership | Whether one contact (by email or member id) is on one list. GET /api/v1/contacts/exists_in_sub_list. |
robly_list_sub_lists | List the account's sub lists (the lists contacts belong to): id, name, position, timestamps. Public lists only unless include_all is true. Use the ids for list filters and for adding contacts. GET /api/v1/sub_lists/show. |
robly_list_fields | List the contact data fields (First Name, Last Name, custom fields): id, label, type, required flag and the user_tag that robly_subscribe_contact and robly_update_contact use as the field key. GET /api/v1/fields/show. |
robly_get_signup_form | The data fields and sub lists a new subscriber can be given through the sign-up API (public ones unless include_all is true). GET /api/v1/sign_up/show. |
robly_subscribe_contact | WRITE: add a new subscribed contact (or re-submit an existing one through the sign-up form). With double_opt_in Robly EMAILS the contact a confirmation link first; with welcome_email it EMAILS the welcome message right away; with include_autoresponder it triggers matching autoresponders, which email |
robly_add_contact_to_list | WRITE: put an existing contact on a list. With include_autoresponder Robly triggers autoresponders matching the newly listed contact, which EMAIL the contact. POST /api/v1/contacts/add_sub_list. |
robly_remove_contact_from_list | WRITE: take a contact off one list (the contact itself is kept). POST /api/v1/contacts/remove_sub_list. |
robly_update_contact | WRITE: change an existing contact's data fields and/or list memberships in one call. Name the contact by member_id (look it up with robly_find_contact). `fields` are keyed by user_tag (robly_list_fields); the email address cannot be changed here. add_to_list_ids puts the contact on those lists, remo |
robly_unsubscribe_contact | WRITE: unsubscribe a contact so Robly stops emailing it. Robly's API cannot undo this: an unsubscribed contact can only come back through a sign-up form. Use it for a contact that asked to stop. POST /api/v1/contacts/unsubscribe. |
robly_create_sub_list | WRITE: create a new, empty sub list. Robly does not say whether a list with the same name already exists, so check robly_list_sub_lists first. POST /api/v1/sub_lists/add_sub_list. |
robly_rename_sub_list | WRITE: rename a sub list. POST /api/v1/sub_lists/rename_sub_list. |