Simafri Suite

Connect it to your AI

Claude Code

claude mcp add --transport http professional-email https://suite-mcp.simafri.com/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://suite-mcp.simafri.com/mcp

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "professional-email": {
      "url": "https://suite-mcp.simafri.com/mcp"
    }
  }
}

Tools it offers

60 tools, as the server itself reported during our check on Oct 31, 2026.

• list_conversationsLists 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
• search_conversationsFinds 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
• get_conversationReads 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"
• get_customer_cardReads 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 re
• get_attachmentReads 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-
• create_attachment_uploadOpens 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 `cu
• send_emailWrites 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:
• reply_to_conversationSends 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
• forward_conversationPasses 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 su
• list_draftsLists 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_draftSends 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_draftTurns a draft down and sends nothing. The thread stays open for another answer, by Iris or by a person.
• list_compose_draftsLists 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_draftWrites 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:
• delete_compose_draftThrows 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_sendsLists 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.
• cancel_scheduled_sendCalls 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
• set_conversation_statusSays 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
• assign_conversationPuts 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 b
• unassign_conversationTakes 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
• add_noteLeaves 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
• update_noteReplaces the text of an internal note left on a thread, for a typo, a wrong figure or a word that no longer holds. The note keeps its author, its place and its files, and shows it was corrected ("updated_at" in get_conve
• delete_noteDeletes an internal note from a thread, and the files it carried with it: a note left on the wrong thread, or one that is no longer true. It cannot be undone; to fix a word, update_note keeps the note. Allowed to the aut
• rename_conversationGives 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_conver
• merge_conversationMerges 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,
• file_conversationFiles 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_i
• list_foldersLists 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 wh
• create_folderMakes 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 neighbo
• update_folderRenames 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_folderDeletes 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_conversationDeletes 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
• report_spamMoves 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 d
• mark_not_spamPuts 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
• unsubscribeLeaves 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 l
• list_blocked_sendersLists 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 u
• unblock_senderLets 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 w
• list_suppressed_recipientsLists 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
• remove_suppressionTakes 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
• mark_readClears 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: fetch
• mark_unreadPuts 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 r

Questions