@kavinga/commerce-tools 0.1.9 → 0.2.0

package/README.md

@@ -1,10 +1,12 @@
 # commerce-tools
 
-A modular AI tooling platform for Adobe Commerce operations, monitoring, and security analysis. Provides a New Relic MCP server for NRQL query execution, plus a composable framework of agents, skills, commands, and providers for building AI-powered Commerce workflows.
+A modular AI tooling platform for Adobe Commerce operations, monitoring, and security analysis. Provides New Relic and Jira MCP servers, plus a composable framework of agents, skills, commands, and providers for building AI-powered Commerce workflows.
 
 ## Features
 
 - **New Relic MCP Server** — executes NRQL queries via NerdGraph and maps Adobe Commerce project IDs to New Relic account IDs
+- **Jira MCP Server** — fetches a Jira issue by key and extracts any New Relic account/project id mentioned in its description or comments
+- **Jira → New Relic Triage Workflow** — a `work-on-ticket` command and `jira-newrelic-triage` skill that chain the two MCP servers to investigate a ticket end-to-end
 - **Commerce & Security Prompts** — built-in specialist prompts for APM monitoring, performance analysis, and attack detection (brute force, SQLi, XSS, DDoS, scraping, carding)
 - **Agent Framework** — automatic tool-use loop with conversation history management and configurable iteration limits
 - **Pluggable Providers** — abstract provider interface supports Claude and other LLM backends
@@ -18,7 +20,8 @@ commerce-tools/
 ├── agents/        # Agent implementations (extend BaseAgent)
 ├── commands/      # CLI command registry
 ├── core/          # Runtime: router, tool-runner, session, hooks
-├── mcps/          # MCP servers (New Relic NRQL)
+├── mcps/          # MCP servers (New Relic NRQL, Jira)
+├── plugins/       # Claude/Cursor plugin build (commands, skills, mcp config)
 ├── providers/     # AI provider implementations and base types
 ├── skills/        # Skill registry and loaders
 ├── dist/          # Compiled output (generated)
@@ -32,6 +35,7 @@ commerce-tools/
 
 - Node.js 18+
 - A New Relic account with a [NerdGraph API key](https://docs.newrelic.com/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/)
+- A Jira Cloud site with an [API token](https://id.atlassian.com/manage-profile/security/api-tokens) (only needed for the Jira MCP server)
 
 ### Installation
 
@@ -52,6 +56,9 @@ cp .env.example .env
 | `NEW_RELIC_API_KEY` | NerdGraph API key |
 | `NEW_RELIC_REGION` | `us` or `eu` (default: `us`) |
 | `NEW_RELIC_ACCOUNT_ID` | Optional default account ID |
+| `JIRA_BASE_URL` | Jira site URL, e.g. `https://yourcompany.atlassian.net` |
+| `JIRA_EMAIL` | Email of the account owning the API token |
+| `JIRA_API_TOKEN` | Jira API token |
 | `MCP_TRANSPORT` | Transport mode (default: `stdio`) |
 
 ### Build
@@ -68,12 +75,21 @@ npm start
 node dist/mcps/newrelic/server.js
 ```
 
+### Run the Jira MCP server
+
+```bash
+npm run start:jira
+# or directly:
+node dist/mcps/jira/server.js
+```
+
 ## Using with Claude Code
 
-The `.mcp.json` file configures the New Relic MCP server for use with Claude Code. To register it:
+The `.mcp.json` file configures both the New Relic and Jira MCP servers for use with Claude Code. To register them manually instead:
 
 ```bash
 claude mcp add newrelic -- node /path/to/commerce-tools/dist/mcps/newrelic/server.js
+claude mcp add jira -- node /path/to/commerce-tools/dist/mcps/jira/server.js
 ```
 
 Or reference the existing `.mcp.json` in your Claude Code project settings. Once connected, Claude can:
@@ -82,6 +98,8 @@ Or reference the existing `.mcp.json` in your Claude Code project settings. Once
 - Resolve Adobe Commerce project IDs to account IDs
 - Analyze logs, transactions, APM metrics, Redis, MySQL, and Elasticsearch data
 - Detect and investigate security attacks
+- Fetch a Jira issue by key and pull its summary, status, description, and comments
+- Chain a Jira ticket straight into a New Relic investigation via the `jira-newrelic-triage` workflow below
 
 ## Architecture
 
@@ -120,6 +138,29 @@ Subclass `BaseAgent` and implement `handleToolCall()` to build custom agents.
 | `newrelic_commerce` | NRQL specialist for Adobe Commerce monitoring and investigation |
 | `newrelic_security` | Extends commerce prompt with attack detection and security analysis |
 
+### Jira MCP Tools
+
+| Tool | Description |
+|---|---|
+| `get_jira_issue` | Fetch a Jira issue by key (e.g. `PRO-234`): summary, status, description, comments, and a best-effort extraction of a New Relic account/project id mentioned in the text |
+
+### Jira → New Relic Triage Workflow
+
+The Jira MCP is paired with a prompt (`mcps/jira/prompts/workflow.ts`) that drives an end-to-end investigation of a ticket:
+
+1. **Fetch the ticket** via `get_jira_issue`.
+2. **Check `extractedIds`** in the result — if an `accountId` or `projectId` was found in the description/comments, use it. If both are empty, the workflow asks the user for one rather than guessing.
+3. **Resolve the New Relic account**, calling `get_account_id_by_project_id` first if only a project ID is known.
+4. **Investigate with NRQL** via `execute_nrql`, following the `newrelic_commerce` prompt's field-discovery rules.
+5. **Summarize findings** back to the user, referencing the ticket key/summary. The ticket itself is never modified — no comments or status changes are made.
+
+This workflow ships as a Claude Code plugin (see `plugins/claude/`):
+
+- **Command** — `/work-on-ticket <issue-key>` runs the workflow directly for a given ticket.
+- **Skill** — `jira-newrelic-triage` is auto-invoked when you mention working on, investigating, or triaging a Jira ticket (e.g. "work on jira ticket PRO-234").
+
+Both are generated from `mcps/jira/prompts/workflow.ts` by `plugins/build.ts` (`npm run build:plugins`) — edit the source prompt, not the generated files under `plugins/*/commands` and `plugins/*/skills`.
+
 ## Development
 
 ```bash

package/package.json

@@ -1,7 +1,25 @@
 {
   "name": "@kavinga/commerce-tools",
-  "version": "0.1.9",
+  "version": "0.2.0",
   "description": "Multi-provider AI tooling platform with MCPs, agents, skills, and commands",
+  "keywords": [
+    "mcp",
+    "model-context-protocol",
+    "mcp-server",
+    "claude",
+    "claude-code",
+    "ai-agent",
+    "llm",
+    "adobe-commerce",
+    "magento",
+    "new-relic",
+    "nrql",
+    "nerdgraph",
+    "jira",
+    "monitoring",
+    "observability",
+    "security-analysis"
+  ],
   "type": "module",
   "bin": {
     "newrelic-mcp": "./dist/mcps/newrelic/server.js",