Issuecapture

io.github.issuecapturePublished by GitHub account issuecapturev1.0.4Updated Oct 25, 2026

Install the IssueCapture bug reporting widget for Jira. Auto-detects your framework.

Overview

AI-generated overview

A local MCP server that installs the IssueCapture bug reporting widget for Jira, auto-detecting the project's framework.

What you can do
Installs the IssueCapture bug reporting widget for Jira into a project, with framework auto-detection to guide the setup. No tool list is published, so the exact operations the assistant can perform are not documented beyond this installation purpose.
When to use it
Useful when you want an assistant to add Jira-connected bug reporting to a web project and have it detect the framework in use.
Requirements
Runs as a local process over stdio, installed from the npm package @issuecapture/mcp-server, so Node.js and npm are needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
It modifies project files to add the widget, so review changes before committing. No credentials are declared, but the widget connects to Jira, so account or project configuration may be requested during setup.

Installation

In SourceWeft

  1. Open Issuecapture in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.