@crypto512/jicon-mcp 2.2.0 → 2.3.0

package/.env.example

@@ -1,9 +1,9 @@
 # Jira Configuration
 JIRA_URL=https://jira.example.com
-JIRA_USERNAME=your-email@example.com
+# JIRA_USERNAME=your-email@example.com  # Optional: omit for Data Center PAT
 JIRA_API_TOKEN=your-jira-api-token
 
 # Confluence Configuration
 CONFLUENCE_URL=https://confluence.example.com
-CONFLUENCE_USERNAME=your-email@example.com
+# CONFLUENCE_USERNAME=your-email@example.com  # Optional: omit for Data Center PAT
 CONFLUENCE_API_TOKEN=your-confluence-api-token

package/README.md

@@ -66,10 +66,8 @@ Add to your `claude_desktop_config.json`:
       "args": ["-y", "@crypto512/jicon-mcp"],
       "env": {
         "JIRA_URL": "https://jira.example.com",
-        "JIRA_USERNAME": "your-email@example.com",
         "JIRA_API_TOKEN": "your-api-token",
         "CONFLUENCE_URL": "https://confluence.example.com",
-        "CONFLUENCE_USERNAME": "your-email@example.com",
         "CONFLUENCE_API_TOKEN": "your-api-token"
       }
     }
@@ -89,8 +87,9 @@ Add to `~/.claude/settings.json` or project `.mcp.json`:
       "args": ["-y", "@crypto512/jicon-mcp"],
       "env": {
         "JIRA_URL": "https://jira.example.com",
-        "JIRA_USERNAME": "your-email@example.com",
-        "JIRA_API_TOKEN": "your-api-token"
+        "JIRA_API_TOKEN": "your-api-token",
+        "CONFLUENCE_URL": "https://confluence.example.com",
+        "CONFLUENCE_API_TOKEN": "your-api-token"
       }
     }
   }
@@ -110,8 +109,9 @@ Add to `opencode.jsonc` in your project root or `~/.config/opencode/opencode.jso
       "command": ["npx", "-y", "@crypto512/jicon-mcp"],
       "environment": {
         "JIRA_URL": "https://jira.example.com",
-        "JIRA_USERNAME": "your-email@example.com",
-        "JIRA_API_TOKEN": "your-api-token"
+        "JIRA_API_TOKEN": "your-api-token",
+        "CONFLUENCE_URL": "https://confluence.example.com",
+        "CONFLUENCE_API_TOKEN": "your-api-token"
       }
     }
   }
@@ -144,6 +144,7 @@ All configuration is done through environment variables.
 | `JICON_HTTP_PORT` | number | `3000` | HTTP server port |
 | `JICON_HTTP_HOST` | string | `0.0.0.0` | HTTP bind address |
 | `JICON_HTTP_BASE_PATH` | string | `/mcp` | MCP endpoint path |
+| `JICON_SESSION_TIMEOUT_MS` | number | `1800000` | Session timeout in milliseconds (default: 30 min). Also controls HTTP server timeouts for SSE connections. MCP clients should use matching timeout. |
 
 **Note:** Tempo uses the same Jira credentials - no separate configuration needed.
 
@@ -209,7 +210,7 @@ This configuration allows:
 }
 ```
 
-**Virtual actions** (for whitelist): `jira_read`, `jira_write`, `jira_all`, `confluence_read`, `confluence_write`, `confluence_draft`, `confluence_all`, `tempo_read`, `tempo_write`, `tempo_all`
+**Virtual actions** (for whitelist): `jira_read`, `jira_write`, `jira_all`, `confluence_read`, `confluence_write`, `confluence_write_home`, `confluence_draft`, `confluence_all`, `tempo_read`, `tempo_write`, `tempo_all`
 
 **Individual tools** (for blacklist): See [TOOL_LIST.md](TOOL_LIST.md) for all tool names
 
@@ -258,7 +259,7 @@ Jicon supports two transport modes:
 | Mode | Use Case | Protocol |
 |------|----------|----------|
 | **stdio** (default) | Local usage with `npx`, Claude Desktop, Claude Code | Standard I/O |
-| **http** | Containers, Kubernetes, remote servers | HTTP with StreamableHTTP |
+| **http** | Containers, remote servers | HTTP with StreamableHTTP |
 
 For containerized deployments, use HTTP mode which exposes the MCP protocol over HTTP.
 
@@ -324,6 +325,9 @@ docker-compose logs -f
 | `JICON_HTTP_PORT` | `3000` | HTTP server port |
 | `JICON_HTTP_HOST` | `0.0.0.0` | HTTP bind address |
 | `JICON_HTTP_BASE_PATH` | `/mcp` | MCP endpoint path |
+| `JICON_SESSION_TIMEOUT_MS` | `1800000` | Session and SSE connection timeout (30 min) |
+
+**Important:** MCP clients using streamable-http should set their `timeout` to match `JICON_SESSION_TIMEOUT_MS` for stable SSE connections.
 
 ### HTTP Endpoints
 
@@ -357,130 +361,10 @@ JICON_TRANSPORT=http \
   npm start
 ```
 
-### Kubernetes Deployment
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
-  name: jicon-secrets
-type: Opaque
-stringData:
-  jira-url: "https://jira.example.com"
-  jira-token: "your-api-token"
----
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: jicon-mcp
-spec:
-  replicas: 1
-  selector:
-    matchLabels:
-      app: jicon-mcp
-  template:
-    metadata:
-      labels:
-        app: jicon-mcp
-    spec:
-      containers:
-      - name: jicon-mcp
-        image: jicon-mcp:latest
-        ports:
-        - containerPort: 3000
-        env:
-        - name: JICON_TRANSPORT
-          value: "http"
-        - name: JIRA_URL
-          valueFrom:
-            secretKeyRef:
-              name: jicon-secrets
-              key: jira-url
-        - name: JIRA_API_TOKEN
-          valueFrom:
-            secretKeyRef:
-              name: jicon-secrets
-              key: jira-token
-        livenessProbe:
-          httpGet:
-            path: /health
-            port: 3000
-          initialDelaySeconds: 5
-          periodSeconds: 30
-        readinessProbe:
-          httpGet:
-            path: /ready
-            port: 3000
-          initialDelaySeconds: 5
-          periodSeconds: 10
-        resources:
-          requests:
-            memory: "128Mi"
-            cpu: "100m"
-          limits:
-            memory: "256Mi"
-            cpu: "500m"
----
-apiVersion: v1
-kind: Service
-metadata:
-  name: jicon-mcp
-spec:
-  selector:
-    app: jicon-mcp
-  ports:
-  - port: 3000
-    targetPort: 3000
-```
-
 ### LibreChat Integration
 
 [LibreChat](https://www.librechat.ai/) supports MCP servers via the `streamable-http` transport type. This allows LibreChat to connect to jicon running in a container.
 
-**Basic configuration in `librechat.yaml`:**
-
-```yaml
-mcpServers:
-  jicon:
-    type: streamable-http
-    url: http://jicon-mcp:3000/mcp
-    timeout: 60000
-    initTimeout: 10000
-    serverInstructions: |
-      Jicon MCP server provides access to Jira, Confluence, and Tempo.
-      Use jicon_help tool to learn about available workflows.
-```
-
-**With environment variables for credentials:**
-
-Jicon reads credentials from its own environment variables. When running with Docker Compose, pass them to the jicon container:
-
-```yaml
-# docker-compose.yml
-version: "3.8"
-
-services:
-  jicon-mcp:
-    build: .
-    environment:
-      - JICON_TRANSPORT=http
-      - JIRA_URL=${JIRA_URL}
-      - JIRA_API_TOKEN=${JIRA_API_TOKEN}
-      - CONFLUENCE_URL=${CONFLUENCE_URL}
-      - CONFLUENCE_API_TOKEN=${CONFLUENCE_API_TOKEN}
-      - JICON_PERMISSIONS_MODE=${JICON_PERMISSIONS_MODE:-readonly}
-
-  librechat:
-    image: ghcr.io/danny-avila/librechat:latest
-    depends_on:
-      - jicon-mcp
-    volumes:
-      - ./librechat.yaml:/app/librechat.yaml
-    # ... other LibreChat configuration
-```
-
-**Per-user credentials with `customUserVars`:**
-
 Each LibreChat user can use their own Jira/Confluence credentials via HTTP headers. Configure `customUserVars` in LibreChat to prompt users for their credentials:
 
 ```yaml
@@ -489,7 +373,7 @@ mcpServers:
   jicon:
     type: streamable-http
     url: http://jicon-mcp:3000/mcp
-    timeout: 60000
+    timeout: 180000
     initTimeout: 10000
     headers:
       X-Jira-Url: "{{JIRA_URL}}"
@@ -525,13 +409,6 @@ mcpServers:
 
 Both URL and Token headers must be provided together for each service. Per-request credentials take priority over environment variables.
 
-**Timeout recommendations:**
-
-| Setting | Value | Description |
-|---------|-------|-------------|
-| `timeout` | `60000` | Request timeout (60s) - allows for large searches |
-| `initTimeout` | `10000` | Initialization timeout (10s) - jicon starts quickly |
-
 For more details, see [LibreChat MCP documentation](https://www.librechat.ai/docs/features/mcp).
 
 ## API Limitations
@@ -594,8 +471,9 @@ All data-heavy tools (search, list, get) return **buffered responses** for effic
 
 **Buffer capabilities:**
 - Read content in chunks or search within buffered data
-- Server-side data transformation: filtering, grouping, sorting, aggregations
-- Export to multiple formats: XHTML tables, lists, CSV, JSON, Markdown
+- JavaScript-based transformation: write custom code to filter, transform, aggregate data
+- Built-in helpers: groupBy, sum, avg, min, max, unique, date utilities
+- Generate Confluence tables and lists with auto-linking and conditional formatting
 - Track buffer origin with metadata (resource type, query, title)
 
 ### Safe Confluence Editing (Review Workflow)