scriptrunner-discoverylisted

# ScriptRunner Jira Discovery ## Overview Before writing ScriptRunner scripts, you often need to know custom field IDs, test JQL queries, or inspect issue data structures. This skill provides three methods in priority order. Use whatever is available in your environment. **MCP Detection:** Check if Atlassian MCP is available by looking for the MCP server configuration: - **Claude Code:** `.mcp.json` - **OpenCode:** `.opencode/opencode.json` If found, also check which token type is configured — this determines which tool categories are available. Look for a `headers` block inside the `atlassian` server entry (`mcpServers.atlassian.headers` in Claude Code, `mcp.atlassian.headers` in OpenCode): | Config auth | Token type | Standard Jira tools | Teamwork Graph tools | |-------------|-----------|---------------------|---------------------| | No `headers` block | OAuth (browser) | ✓ | ✓ | | `headers` with non-`ATATT3x` token | Fine-grained (scoped) | ✓ | ✓ | | `headers` with `ATATT3x…` token | Classic (legacy) | ✓ (if org setting on) | ✗ — will 403 | ### Client config notes **Claude Code** uses `"type": "http"` in `.mcp.json`: ```json { "mcpServers": { "atlassian": { "type": "http", "url": "https://mcp.atlassian.com/v1/mcp" } } } ``` **OpenCode** uses `"type": "remote"` in `.opencode/opencode.json` (not `"http"` — that field means something different in OpenCode): ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "atlassian": { "type": "remote",