@crypto512/jicon-mcp 1.0.2 → 1.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -115,15 +115,17 @@ Add to `opencode.jsonc` in your project root or `~/.config/opencode/opencode.jso
|
|
|
115
115
|
| `JIRA_URL` | Your Jira instance URL |
|
|
116
116
|
| `JIRA_USERNAME` | Your email (omit for Data Center PAT) |
|
|
117
117
|
| `JIRA_API_TOKEN` | API token or Personal Access Token |
|
|
118
|
+
| `JIRA_AUTH_TYPE` | Optional: `basic` or `bearer` (auto-detected from username) |
|
|
118
119
|
| `CONFLUENCE_URL` | Your Confluence instance URL |
|
|
119
120
|
| `CONFLUENCE_USERNAME` | Your email (omit for Data Center PAT) |
|
|
120
121
|
| `CONFLUENCE_API_TOKEN` | API token or Personal Access Token |
|
|
122
|
+
| `CONFLUENCE_AUTH_TYPE` | Optional: `basic` or `bearer` (auto-detected from username) |
|
|
121
123
|
|
|
122
124
|
**Note:** Tempo uses the same Jira credentials - no separate configuration needed.
|
|
123
125
|
|
|
124
126
|
### Configuration File (Optional)
|
|
125
127
|
|
|
126
|
-
Create `.jicon.json` in your project root for project-specific settings:
|
|
128
|
+
Create `.jicon.json` in your project root for project-specific settings, or `~/.config/jicon/jicon.json` for user-wide settings:
|
|
127
129
|
|
|
128
130
|
```json
|
|
129
131
|
{
|
|
@@ -140,6 +142,8 @@ Create `.jicon.json` in your project root for project-specific settings:
|
|
|
140
142
|
}
|
|
141
143
|
```
|
|
142
144
|
|
|
145
|
+
**Priority:** Project config → User config → Environment variables
|
|
146
|
+
|
|
143
147
|
**Important:** Add `.jicon.json` to your `.gitignore`!
|
|
144
148
|
|
|
145
149
|
### Permission Modes
|
|
@@ -156,12 +160,13 @@ Control what operations are allowed. **By default, Jicon runs in read-only mode*
|
|
|
156
160
|
{ "permissions": { "mode": "full" } }
|
|
157
161
|
```
|
|
158
162
|
|
|
159
|
-
**Custom** - fine-grained control:
|
|
163
|
+
**Custom** - fine-grained control with whitelist and blacklist:
|
|
160
164
|
```json
|
|
161
165
|
{
|
|
162
166
|
"permissions": {
|
|
163
167
|
"mode": "custom",
|
|
164
|
-
"whitelist": ["
|
|
168
|
+
"whitelist": ["jira_all", "confluence_all", "tempo_all"],
|
|
169
|
+
"blacklist": ["confluence_delete_page", "tempo_delete_worklog"]
|
|
165
170
|
}
|
|
166
171
|
}
|
|
167
172
|
```
|
|
@@ -184,7 +189,9 @@ This configuration allows:
|
|
|
184
189
|
|
|
185
190
|
The `confluenceWriteHome: true` setting ensures all Confluence write operations (drafts, comments, attachments) can only target your personal space, preventing accidental modifications to shared team spaces.
|
|
186
191
|
|
|
187
|
-
|
|
192
|
+
**Virtual actions** (for whitelist): `jira_read`, `jira_write`, `jira_all`, `confluence_read`, `confluence_write`, `confluence_all`, `tempo_read`, `tempo_write`, `tempo_all`
|
|
193
|
+
|
|
194
|
+
**Individual tools** (for blacklist): See [TOOL_LIST.md](TOOL_LIST.md) for all tool names (e.g., `confluence_delete_page`, `tempo_delete_worklog`)
|
|
188
195
|
|
|
189
196
|
## Authentication
|
|
190
197
|
|