[connectors] feat: Add Jira connector for web-security#23
Merged
Conversation
…-security # Conflicts: # capabilities/web-security/agents/web-security.md # capabilities/web-security/capability.yaml
…-security # Conflicts: # capabilities/web-security/agents/web-security.md # capabilities/web-security/capability.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Jira Cloud MCP connector to the
web-securitycapability so validated findings can be exported as internal Jira remediation tickets.The connector is intentionally scoped to the post-validation delivery path. The web-security agent guidance now instructs agents to use Jira only after the normal reporting pipeline has completed:
assess_confidence,report-preflight,exploit-verifier, andreport-writer.Changes
capabilities/web-security/mcp/jira.pyas a self-containeduv runFastMCP server.jiraMCP server intocapabilities/web-security/capability.yaml.Connector Surface
jira_healthjira_get_create_metadatajira_create_issuejira_get_issuejira_add_commentAuth uses
JIRA_BASE_URL,JIRA_EMAIL, andJIRA_API_TOKEN.Validation
uv run pytest capabilities/web-security/tests/test_jira_mcp.pypassed: 10 tests.mypy capabilities/web-security/mcp/jira.py capabilities/web-security/tests/test_jira_mcp.py --ignore-missing-importspassed.pre-commit run --files capabilities/web-security/capability.yaml capabilities/web-security/agents/web-security.md capabilities/web-security/mcp/jira.py capabilities/web-security/tests/test_jira_mcp.pypassed.just validatecompleted with 0 failures.uv run capabilities/web-security/mcp/jira.py; process stayed running until timeout as expected for stdio MCP.PYTHONPATH=capabilities/web-security/tools uv run pytest capabilities/web-security/testspassed: 146 passed, 7 existing warnings.git diff --checkpassed.Known
just validatewarnings are pre-existing environment warnings unrelated to this change:bloodhound-enterpriseruntime imports, local web-securitycaido-cli/Burp checks, andwindows-reversingJava 17 check.