send_emailLABSCO SUMMARY
Indirection is the security model, and it is the right one.
Passing a password as a tool argument means it lands in the model's context, the transcript and anywhere either of those is logged. Replacing it with a pair of identifiers that only the local vault can resolve removes that whole class of exposure without asking anyone to be careful. The scope is deliberately narrow — plain text, no attachments, one tool — which keeps the surface small enough that the guarantee is easy to believe.
What it is
An MCP server that sends plain-text email over SMTP, built so the credentials never reach the assistant. The SMTP address, password, host and port are stored in MGC Blackbox, a local encrypted vault; the tool call carries only the identifiers naming which stored credential to use.
What you get
- One email sent, taking
to,subjectandbodyplus the two identifiers that select the stored credential —send_email - A credential boundary that holds by construction: the password is read from the local vault at send time, so it is never part of the tool arguments the model produces
- Compatibility with any SMTP provider, since the stored config is just address, password, server and port
- Trigger phrases the client can match on, so the tool fires on ordinary requests to send something
Requirements
An SMTP account and MGC Blackbox: pip install mgc-blackbox, then run mgc. Write a JSON file with your address, password, smtp_server and smtp_port and store it with mgc_save info_type=config info_owner=your_email < config.json — those two identifiers are what you later pass to the tool, and you choose them. Clone the skill folder from the repository and run python mcp_server.py. Limits worth knowing before you wire it in: plain-text bodies only, no attachments and no HTML. MIT licensed.
Setup effort
Follow the published steps — pip install mgc-blackbox
USE CASES
01
Letting an assistant send mail from your own address
Store the SMTP credentials once in the local vault, then send by naming them — the password stays out of the conversation.
02
Keeping automation credentials out of transcripts
Use it where an agent sends notifications regularly and the logs of those sessions would otherwise contain a password.
03
Sending from more than one account
Save several credential entries under different identifiers and pick which one a given message goes out from.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install mgc-blackboxRun the MGC Blackbox command once it is installed: mgc
TERMINAL
git clone https://github.com/zkeviny/MGC-Blackbox
cd MGC-Blackbox/mgc_skill/zero_exposure_smtp_senderCreate config.json holding your SMTP address, password, smtp_server and smtp_port
Store it in the local vault — info_type and info_owner are identifiers you choose and later use to retrieve it: mgc_save info_type=config info_owner=<YOUR_INFO_OWNER> < config.json
TERMINAL
python mcp_server.py
