Name: Simafri Suite
Author: com.simafri

Tools observed via MCP handshake

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_co
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_ad
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,
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 add
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
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 addr
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
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
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 answe
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
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
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, no
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
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 who
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, who
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
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
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
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
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
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 t
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 bac
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,
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
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 k
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
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. Thi
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
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 i
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 l
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 le
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 a
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, a
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
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 ge
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 row
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 ha
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. Se
set_signature — Writes the block that closes what is written from an address. It belongs to the address, so everyone who writes from it signs the same way; it is put into a mes
set_archive_on_reply — Says whether a thread of a mailbox leaves the Inbox for the Archive as soon as the box answers it, whether the answer is written in the webmail, through these t
list_mailboxes — Lists the mailboxes of the account: each one with the people who hold it, the other names that deliver into it and the storage its plan entitles the account to,
add_mailbox_holder — Puts a person of the account on a mailbox, which is what lets them read it. This is how a company takes back the correspondence of someone who has left; it is r
remove_mailbox_holder — Takes a person off a mailbox: they stop reading it from that moment. Nothing is deleted, and a box left with no holder keeps receiving and keeps everything it h
add_mailbox_alias — Points another address at a mailbox: mail sent to it lands in that box, threads there and counts against the storage of the account. An alias has no password, n
remove_mailbox_alias — Stops an address delivering into a box. What already arrived through it stays in the box, and each message still says which name it came in on.
list_people — Lists everyone on the account: how they sign in, the rank they hold, and how far they see into the mail. An owner and a manager work every helpdesk queue, which
invite_person — Opens an access for a colleague without a password: an invitation goes to send_to, and whoever opens it chooses the password from its link, which opens for seve
add_queue_operator — Names a person of the account on a helpdesk queue, which is what lets them work it: they see the threads that arrived on that address, and none of the others. T
remove_queue_operator — Takes a person off a helpdesk queue: they stop seeing its threads from that moment. Nothing is deleted, and a queue nobody is named on keeps receiving and is st
list_teams — Lists the teams of the account, the administrative team or the technical one for instance, each with its slug (what assign_conversation and the other team tools
create_team — Opens a team by its name; its slug comes from the name and never changes, even when the team is renamed. A name too close to one the account already has is refu
rename_team — Gives a team a new name. Its slug stays, so every reference to it keeps working.
delete_team — Deletes a team. The threads handed to it go back to their queue with nobody's name on them; the threads one of its members took stay on that member's name.
add_team_member — Puts a person of the account in a team, whatever their rank. It opens no queue: they see the threads handed to the team only on the queues they already work, wh
remove_team_member — Takes a person out of a team. The threads they took from it stay on their name.
list_brands — Lists the brands of the account, its subdivisions, each with the slug the other tools take.
list_contacts — Lists the contacts of the account with their fiche, most recently seen first, and searches them by name, company or address.
get_contact — Reads one contact whole: their fiche, the addresses they write from and where each field came from.
create_contact — Opens a fiche for someone before any exchange has happened. An address the account already holds returns that contact as it stands, so calling it twice keeps on
update_contact — Writes the fiche fields you pass, and leaves the others as they are. What is written here is recorded as coming from a person, which keeps a later reading by Ir
list_knowledge — Lists the playbook docs of the account with their full content: this is the material Iris reads before drafting, and the place to look when an answer needs to s
create_knowledge — Adds a doc to the playbook Iris reads, scoped to the brands and addresses you give it. Use it to record a price list, an argument that works or a rule to follow
update_knowledge — Writes a doc whole, keeping the previous version dated in its history. Send the title and the content each time, plus the brands and addresses it applies to.
delete_knowledge — Takes a doc out of the playbook, with every version it ever had. This is FINAL and there is no trash: Iris stops reading it from the next draft on. A doc that i
get_settings — Reads the settings of the account, starting with whether an incoming message has Iris draft an answer on its own. "own_domain_spoofs" says what the account does
set_auto_draft — Says whether an incoming message has Iris draft an answer on its own. With it off, a draft is written when someone asks for one from the inbox, which is what ke

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	61 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
13 h ago	mcp initialize	ok	200	96 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
20 h ago	mcp initialize	ok	200	58 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
27 h ago	mcp initialize	ok	200	76 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
34 h ago	mcp initialize	ok	200	54 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
2 d ago	mcp initialize	ok	200	77 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
2 d ago	mcp initialize	ok	200	95 ms	server simafri-suite 1.0.0 · protocol 2025-06-18 · 68 tools
2 d ago	mcp initialize	ok	401	41 ms	auth required
3 d ago	mcp initialize	ok	401	96 ms	auth required
3 d ago	mcp initialize	ok	401	54 ms	auth required

Simafri Suite

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from