4 ms·
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
by bikelang 6mo ago
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.
- hnlmorg 6mo agoCan you share more about acli? Literally my biggest use case for MCP is Jira and Confuence
- dugmartin 6mo agoIt is available here: https://developer.atlassian.com/cloud/acli/guides/introduction/ 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.
- walthamstow 6mo ago`acli` doesn't cover Confluence and I found it limited compared to the MCP by sooperset on GitHub.
- 0x696C6961 6mo agoIf Atlassian put out a horrible CLI tool, would your conclusion be that "CLIs are bad"?
- bikelang 6mo agoThe 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.