Show HN: Slack CLI for Agents
github.com35 points by nwparker a day ago
35 points by nwparker a day ago
Our team lives in Slack, but we don’t have access to the Slack MCP and couldn’t find anything out there that worked for us, so we coded our own agent-slack CLI
* Can paste in Slack URLs
* Token efficient
* Zero-config (auto auth if you use Slack Desktop)
Auto downloads files/snippets.
Also can read Slack canvases as markdown!MIT License
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. 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 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. 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. 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
impulser_ - 13 minutes ago
apimade - an hour ago
Wuzzy - 2 hours ago
Hansenq - 2 hours ago
BlueOrigin50 - a day ago
slopusila - 3 hours ago