by theanonymousone
2 subcomments
- Haha. Nobody ever cared that some humans preferred to use services via a CLI versus GUI. But now that "AI" needs it, CLI programs and APIs get released left and right :D
by impulser_
2 subcomments
- 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.
- 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.
- For the CLI > MCP folks: https://cliwatch.com/
- 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.
by BlueOrigin50
1 subcomments
- Oh nice. I just installed and it works pretty well. It wasn't able to find the user names on the thread though.
- Nice! Fits very well to my cli based cron job deamon for agents https://github.com/t0dorakis/murmur
- I just built something very similar too: https://github.com/lox/slack-cli
- what about a way to read channels rather than messages? seems missing?
also... any shortcut for UNREAD messages? for yknow making a recap
by FranklinJabar
2 subcomments
- Using slack makes me so depressed. The interactions we have today pale in comparison to what we had in IRC 30 years ago.
Of course I accept we're stuck with slack. I just have no clue what to write with such a limited interface. The above posted link is a great example of making the most of a tiny interface and coming up short compared to... 30 years ago
- > we don’t have access to the Slack MCP
ok, why?
- how about support for "auth import-token" so you dont need to keep SLACK_TOKEN in env
Hacker News