MCP Server

The last few days has been exciting! I had the opportunity to setup my new Macbook Pro at work. The catch was I was doing this over the weekend and I was yet to be given access to the corporate’s Claude Code.

I had access to Slack and not much else.

My theory is a company’s culture and decision making bleeds into the medium of team communication such as Slack and analyzing these messages would give me just enough insight into hit the ground running.

I could have used my personal Claude Code account and setup the Slack plugin however I would had hit a block with the Identity and Access Management (IAM) rules that were yet to be added to my corporate user.

Instead I “built” a local MCP Server for Slack that would use session token and cookies to talk to Slack, enter babel-fish

I proceeded to install Crush and connected it to Slack via babel-fish.

Some of the insights I gained from analyzing the company wide Slack messages were really helpful. I got an insight into

• what the #1 focus of my new team is
• the channels to keep an eye on
• the business temrinology used across all teams
• how support issues flow to engineering, just to name a few things.