send_slack_messageLABSCO SUMMARY
The secret never reaches the part of the system that talks to the model.
Most Slack integrations put a bot token in an MCP config file, where every process that can read the config can read the token. Here the credential lives in an encrypted local store and is fetched at send time, and the project states there is no subprocess, exec or shell usage in the path. Mock mode means you can wire up the workflow before you hand it a real token.
What it is
A Slack sender built around a local credential vault. The webhook URL, bot token and default channel are stored in MGC Blackbox and read at send time, so the agent that posts the message never holds the secret and nothing sensitive lands in a config file or a log line.
What you get
- A Slack message posted with the message body, and optionally a target channel, a custom bot display name and an emoji icon —
send_slack_message, takingtext,channel,usernameandicon_emoji - Either a webhook URL or a bot token as the delivery path, whichever you stored
- A mock mode for development that exercises the same path without making a real Slack request
Requirements
Slack credentials — a webhook URL or a bot token — plus a channel, stored in the local vault rather than passed to the server. Install the vault with pip install mgc-blackbox, then save a JSON file holding webhook_url, bot_token and default_channel with mgc_save info_type=config info_owner=slack_bot; the two identifiers are yours to choose and are how the credentials are retrieved later. Clone the skill and start it with python mcp_server.py.
Setup effort
Follow the published steps — pip install mgc-blackbox
USE CASES
01
Posting deployment and job notifications from an agent
Have the agent announce a finished run to a channel without the workflow file containing the webhook URL.
02
Routing different alerts to different channels
Pass the channel per message while the stored default covers everything else, so one credential serves several destinations.
03
Building the notification flow before you have credentials
Run in mock mode to confirm the wording and the trigger conditions, then switch to the real token once the flow is right.
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_slack_senderCreate slack_config.json holding your webhook_url, bot_token and default_channel
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=slack_bot < slack_config.json
TERMINAL
python mcp_server.py
