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.
humanperhaps 49 minutes ago [-]
From my perspective, this also marks the shift towards agent skills instead of MCP, since agent skills rely on CLI tools. To me, this is also better than MCP since third-party developers can easily reuse existing APIs and libraries instead of needing official MCP support.
Wuzzy 4 hours ago [-]
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.
apimade 3 hours ago [-]
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.
nwparker 43 minutes ago [-]
I don't use Slack Grid, but if you open an issue I'm more than happy to work with you on it!
mogili1 2 hours ago [-]
I ended up vibe coding a script that uses slack token from the browser to download my messages locally. It's not been flagged yet. But my account got flagged when I tried slackdump.
Hansenq 5 hours ago [-]
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.
BlueOrigin50 1 days ago [-]
Oh nice. I just installed and it works pretty well. It wasn't able to find the user names on the thread though.
nwparker 1 days ago [-]
You could ask it to convert the names (and it would), since it uses the slack internal userIds
But I will add a flag to do for `slack message read/list`, since it makes sense.
slopusila 6 hours ago [-]
how about support for "auth import-token" so you dont need to keep SLACK_TOKEN in env
1 days ago [-]
Rendered at 04:14:50 GMT+0000 (Coordinated Universal Time) with Vercel.
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.
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.
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.
But I will add a flag to do for `slack message read/list`, since it makes sense.