Oh nice. I just installed and it works pretty well. It wasn't able to find the user names on the thread though.

how about support for "auth import-token" so you dont need to keep SLACK_TOKEN in env

Oh this is smart! Reading where Slack stores the local data in your filesystem instead of using their API/MCP (which they charge for).

Very clever; similar to OpenAI launching Atlas when websites start blocking bot requests--just build your own browser so your bot becomes an actual user.

I believe in an MCP-less future of agent-service interactions and have recently submitted this general alternative (which also supports Slack) based on curl: https://github.com/imbue-ai/latchkey

With that said, a specialized tool like this will almost certainly work better if Slack is the only service you want your agents to interact with. I like that the auth is transparent.

Warning: in Enterprise (Grid) your account will likely be flagged as hijacked, and all of your sessions will be killed.

Slack implemented session hijacking detection a while ago, and using LLM’s without throttling will very likely result in alerts. If you’re on Enterprise; I’d suggest re-slopping a re-implementation of this with ghost Chrome puppeteer.

I'm glad more people are catching onto lightweight CLI tools and using skills to give llms more tools. It's way better than MCP. I been doing this for awhile now and it's just the best way to gets LLMs to do things with APIs built for humans.