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.
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.
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.
how about support for "auth import-token" so you dont need to keep SLACK_TOKEN in env