Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think many of us have been burned by the absolutely awful and unstable JIRA MCP and found that skills using `acli` actually work and view the rest of the MCP space thru that lens. Lots of early - and current! - MCP implementations were bad. So it’s an uphill battle to rebuild reputation.


`acli` doesn't cover Confluence and I found it limited compared to the MCP by sooperset on GitHub.


If Atlassian put out a horrible CLI tool, would your conclusion be that "CLIs are bad"?


The Atlassian CLI is pretty bad too! But at least the robot can consistently use it. And I can use it to help the robot figure out Atlassian’s garbage data structures. There’s not much I can do to debug their awful MCP.


Can you share more about acli?

Literally my biggest use case for MCP is Jira and Confuence


It is available here:

https://developer.atlassian.com/cloud/acli/guides/introducti...

It has a pretty discoverable cli syntax (at least for Claude). I use it in my custom skills to pull Jira story info when creating and reviewing specs.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: