Simafri Suite

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "simafri-suite": {
      "type": "http",
      "url": "https://suite-mcp.simafri.com/mcp"
    }
  }
}

68 tools

• list_conversations

  Lists threads, most recently updated first, with the contact, the subject of the mail and the one the team gave the thread ("team_subject", null until rename_conversation gives one), the ticket number of a helpdesk case (what the client quotes, null on somebody's mailbox), the…

• search_conversations

  Finds the threads of one mailbox by their subject, their text, the people on them or the names of the files they carried, best answer first. Call list_sender_addresses to find the box. This is how you look a mail up when you know a word of it and not where it is.

• get_conversation

  Reads one thread whole: every message in order with its direction, its language and its attachments, the contact fiche, the mailbox the thread arrived through, the draft awaiting review when there is one, and in "notes" what the team left on the thread for each other, oldest…

• get_customer_card

  Reads the customer card of a helpdesk ticket: what the account's own system (its client area, CRM or ERP) knows about the correspondent, asked live by their address, such as their account, their services and when they renew, and what they owe. "status" says "found" with the…

• get_attachment

  Reads a file attached to a message and gives back its CONTENT. Text comes back as text, whatever the sender labelled it: a CSV, an XML, a JSON, a Markdown or a log read as text even when they arrive as application/octet-stream. An image comes back as the image itself, a PDF…

• create_attachment_upload

  Opens an address to send a file to, so that a message can attach it without carrying it. Answers with an upload_id and an upload_url: PUT the bytes to that address in one request (no key, nothing to sign, for example `curl -T report.pdf "<upload_url>"`), then pass {"upload_id"…

• send_email

  Writes and sends an email to someone, and opens the thread their answer will land in. The text goes out as given, so this is the tool for a message a person has read and approved. With "send_at" it is scheduled instead: nothing leaves until then, and list_scheduled_sends shows…

• reply_to_conversation

  Sends an answer in an existing thread, written by the caller, from the address the thread arrived through. A draft left pending on that thread is superseded, so the contact reads one answer. With "send_at" the answer is scheduled instead, and supersedes that draft only when it…

• forward_conversation

  Passes the last message of a thread on to someone else: they receive the text quoted under its own header, with the files it carried attached again. Their answer opens a thread of its own, so forwarding to the account support address is how a message reaches the support queue…

• list_drafts

  Lists the answers Iris has written, with the thread each belongs to, the contact it goes to and the text as it stands. Filter on "pending_review" for the review queue.

• approve_draft

  Sends a draft to the contact, with the text as given in "body" when you edited it. The draft keeps the original wording and the sent message keeps what actually left, so the two stay comparable afterwards.

• reject_draft

  Turns a draft down and sends nothing. The thread stays open for another answer, by Iris or by a person.

• list_compose_drafts

  Lists the messages begun on the account addresses and never sent, last written first, with their recipients, subject, text and files. These are unsent texts, not the answers Iris wrote for review, which list_drafts holds.

• save_compose_draft

  Writes down a message being prepared, so it can be finished later from anywhere. Pass "from" to start one; pass its id to write into it again, where the fields you leave out keep the value they had. Saving sends nothing: send_email is what sends.

• delete_compose_draft

  Throws away a message that was started and will not be sent. Nothing was ever delivered, so nothing is lost but the text itself.

• list_scheduled_sends

  Lists the messages given a "send_at" that have not left yet, soonest first: when each leaves (in the zone of the person you act for), from which address, to whom, the subject and text, and the thread an answer goes into. A message that has left is no longer here but in its…

• cancel_scheduled_send

  Calls a scheduled message back before it leaves. Nothing is sent and nothing is lost: it becomes an unsent draft again, with its recipients, text and files, whose draft_id the answer gives (delete_compose_draft throws it away). Refused once the message is already leaving.

• set_conversation_status

  Says where a thread stands, and optionally where it stands in the pipeline. Both are recorded as decided by a person, so a later reading by Iris keeps them. To set the same status on several threads, give conversation_id the list of their ids, in ONE call rather than one call…

• assign_conversation

  Puts a colleague's name on a thread of a helpdesk queue: what says, to everyone working that queue, that this one is being dealt with and by whom. It hands over the WORK and not the access, so the thread stays readable by the whole team and nobody loses sight of it. Somebody who…

• unassign_conversation

  Takes the name off a thread: nobody is handling it, and it goes back to the queue for whoever picks it up. It closes no door, the thread having been readable by everybody working that queue the whole time. Replayed on a thread nobody had taken, it answers the same thing. To give…

• add_note

  Leaves a note on a thread for the people who work it: shown on the thread screen beside the messages, marked as internal, and in "notes" of get_conversation. It never reaches the correspondent: it is not sent, not quoted in a reply and not part of the mail. It is where the…

• rename_conversation

  Gives a thread a subject that says what it is about, for the people who work it: shown in the lists and on the thread screen in place of the subject of the mail, and in "team_subject" of list_conversations and get_conversation. It is the team's label and never the subject of the…

• merge_conversation

  Merges a helpdesk ticket into another of the same contact, for the client who wrote again beside their case rather than in it. Everything it held moves to the ticket named by "into": its messages, their files, its notes, its drafts. Its number keeps leading to the merged case…

• file_conversation

  Files a thread where you say: "archive" puts it away, out of the Inbox and kept for good; "trash" throws it away, where it stays readable and can be brought back; "inbox" brings it back from wherever it was; or "folder_id" files it in a folder a person made (list_folders gives…

• list_folders

  Lists the folders the people of a mailbox made in it, beside the six every mailbox has (inbox, sent, drafts, spam, trash, archive), each with its id, its name, its full path ("Clients/LCS") and its parent. The ids are what list_conversations, search_conversations and…

• create_folder

  Makes a folder in a mailbox, at the top or under another folder, to file threads in. Every holder of the box sees it, in the webmail and in their mail client. A name holds no "/", "*" nor "%", is unique among its neighbours, and at the top is none of the six every mailbox has.

• update_folder

  Renames a folder a person made, moves it under another one or to the top, or both; the folders under it follow, and the threads in it stay. What you leave out keeps its value.

• delete_folder

  Deletes a folder a person made and the folders under it. Their threads go to the Trash, where they stay readable and restorable for 30 days; nothing is deleted for good. The answer says how many went there.

• delete_conversation

  Deletes a thread and everything it holds: every message, the drafts written on it, and the files that came with them, down to the bytes they were stored as. This is FINAL and there is no trash to fish it back out of, so it is not the gesture for tidying an inbox…

• report_spam

  Moves a thread of a mailbox into its Spam folder, where it stays readable and can be taken back out, and blocks its sender: their next message is filed in Spam too, without anybody being asked again. Spam is emptied 30 days after a thread lands there, and that deletion is final…

• mark_not_spam

  Puts a thread the filter or someone else filed as spam back into the Inbox of its mailbox, and unblocks its sender. A thread that is not in Spam is left where it is, and nothing is unblocked. To take several threads out of Spam, give conversation_id the list of their ids, in ONE…

• unsubscribe

  Leaves the mailing list a thread came from (a newsletter, a promotional mailing, a notification list), in the name of the mailbox it arrived in, with what the last message received in the thread offers: one POST to the list's unsubscribe address when it accepts a one-click…

• list_blocked_senders

  Lists the addresses whose mail this account files straight into Spam, most recently blocked first, with the day each was blocked. A block is what report_spam leaves behind, so this is where a rule the account is living under becomes visible again: a sender blocked from a thread…

• unblock_sender

  Lets an address write to the Inbox again: their next message is filed like anybody else's. Threads already sitting in Spam stay where they are, a block having always been about the mail still to come; file_conversation with "inbox" is what brings one of them back. An address…

• list_suppressed_recipients

  Lists the addresses that pressed "this is spam" on this account's mail, with the day and the label their provider gave it. The account writes to none of them, and it does so SILENTLY: a message to one of these addresses is stopped before it leaves, with no bounce and nothing in…

• remove_suppression

  Takes an address off the list above, so this account can write to them again. Weigh it before calling it: the row means a person pressed "this is spam" on mail from this account, and writing to them again is what turns a complaint into a sending reputation the whole platform…

• mark_read

  Clears the bold on a thread for YOU, exactly as opening it on screen does: a colleague reading the same shared mailbox keeps their own. Reading a thread with get_conversation does not do this by itself, on purpose: fetching a mail is not the same as having read it. A message…

• mark_unread

  Puts a thread back among the bold rows, for you alone: what you want to come back to. A colleague sees no change. To put several threads back among the bold rows, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in…

• poll_mailboxes

  Reads the account mailboxes right away instead of waiting for the next scheduled round, and answers with what came in. Call it when you expect a message that has not appeared yet.

• list_sender_addresses

  Lists the inbound addresses of the account, each with the block that closes what is written from it and, for a mailbox, the other names that deliver into it. Sending from any of these is what brings the answer back into the mailbox.

Security scan

Recent checks