I use CLI tools for Git, Atlassian (ACLI), and Metabase, plus custom SigNoz shell scripts to drive API calls instead of an MCP server. This setup works very well at the moment for me.
I run a few agents side by side and I've been going back and forth on whether to bother with MCP servers at all. I'm not clear on what each of those is doing in your loop though. Could you go into a bit more detail?
I have a simple workflow consisting of:
- acli to pull ticket details from Jira.
- gh for GitHub remote pushes, PR generation, and GitHub Actions tracking.
- A SigNoz shell script to monitor changes in the dev/stage/prod(logs, metrics, traces) environments.
- The Metabase CLI (mb) to verify data in the database.
awscli and kubectl to fetch read-only Kubernetes data for the agent.
I also have the skills to understand how this workflow operates and how to use each of these tools.
For example:
I give the agent the ticket URL or ID, the jira-ticket-pull skill gets invoked, and the agent now knows how to use acli to pull tickets. The agent goes through the ticket details and uses its skills to grill me on the description until the agent and I reach a common understanding of what to do. Then, it uses the TDD skill for implementation. At the end, there is a commit-and-push skill to enforce commit conventions, push the code, and create a PR using the gh CLI.
If the ticket is about monitoring or bugs, the agent uses SigNoz scripts instead to get more context. If it needs data from the database to ground itself, it uses mb to get it.
Comments
I use CLI tools for Git, Atlassian (ACLI), and Metabase, plus custom SigNoz shell scripts to drive API calls instead of an MCP server. This setup works very well at the moment for me.
I run a few agents side by side and I've been going back and forth on whether to bother with MCP servers at all. I'm not clear on what each of those is doing in your loop though. Could you go into a bit more detail?
I have a simple workflow consisting of: - acli to pull ticket details from Jira.
- gh for GitHub remote pushes, PR generation, and GitHub Actions tracking.
- A SigNoz shell script to monitor changes in the dev/stage/prod(logs, metrics, traces) environments.
- The Metabase CLI (mb) to verify data in the database. awscli and kubectl to fetch read-only Kubernetes data for the agent.
I also have the skills to understand how this workflow operates and how to use each of these tools.
For example: I give the agent the ticket URL or ID, the jira-ticket-pull skill gets invoked, and the agent now knows how to use acli to pull tickets. The agent goes through the ticket details and uses its skills to grill me on the description until the agent and I reach a common understanding of what to do. Then, it uses the TDD skill for implementation. At the end, there is a commit-and-push skill to enforce commit conventions, push the code, and create a PR using the gh CLI.
If the ticket is about monitoring or bugs, the agent uses SigNoz scripts instead to get more context. If it needs data from the database to ground itself, it uses mb to get it.