1. Conduid
  2. Analytics
  3. Export Sentry Issue
MCP server · Analytics

Export Sentry Issue

Exporting and analyzing Sentry issues

Unclaimed MIT last commit a year ago analytics
51Fair

Scored 8 days ago · breakdown

About Export Sentry Issue

Export Sentry Issue is an MCP server published by cldotdev in the Analytics category: exporting and analyzing Sentry issues.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/cldotdev/export-sentry-issue

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Export Sentry Issue

Powered by Claude · Grounded in docs

I know everything about Export Sentry Issue. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

3 checks have not been run yet.

Releases

0.1.10.1.1
0.1.00.1.0

README

Export Sentry Issue

繁體中文版 (Traditional Chinese)

A collection of tools for exporting and analyzing Sentry issues.

Packages

This repository contains multiple packages:

📦 export-sentry-issue

A Python CLI tool for exporting Sentry issues to plain text files.

Features:

  • Export complete error messages and stack traces
  • Support both Self-hosted Sentry and SaaS version
  • Include Request information, Breadcrumbs, Spans, and Context data
  • Secure token management with file permissions
  • Batch export multiple issues

Quick Start:

pip install export-sentry-issue

# Initialize configuration (secure, token hidden)
export-sentry-issue init

# Export issues
export-sentry-issue export --ids "12345,67890"

📖 Full Documentation

🔌 export-sentry-issue-mcp

An Model Context Protocol (MCP) server that allows AI assistants like Claude to export and analyze Sentry issues.

Features:

  • 🔧 MCP Tools for Sentry issue management
  • 🤖 Auto-triggered when you mention Sentry URLs or issue numbers
  • 🔐 Secure configuration with file permissions
  • 📝 Rich export format with stack traces, breadcrumbs, spans
  • 🚀 Multiple transport modes (STDIO and HTTP/SSE)

Quick Start:

Using Docker:

docker pull ghcr.io/jlhg/export-sentry-issue-mcp:latest

Or install via pip:

pip install export-sentry-issue-mcp

# Initialize configuration
export-sentry-issue-mcp init

# Add to Claude Desktop config (~/.config/claude/claude_desktop_config.json)
{
  "mcpServers": {
    "sentry": {
      "command": "export-sentry-issue-mcp"
    }
  }
}

📖 Full Documentation

Development

This is a monorepo containing multiple Python packages. Each package can be developed and published independently.

Project Structure

export-sentry-issue/
├── packages/
│   ├── export-sentry-issue/      # CLI tool
│   │   ├── src/
│   │   ├── pyproject.toml
│   │   └── README.md
│   └── export-sentry-issue-mcp/  # MCP server
│       ├── src/
│       ├── pyproject.toml
│       └── README.md
├── LICENSE
└── README.md

Local Development

# Install a package in editable mode
cd packages/export-sentry-issue
pip install -e .

# Or for the MCP server
cd packages/export-sentry-issue-mcp
pip install -e .

License

MIT License - see LICENSE file for details.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Export Sentry Issue

How do I install Export Sentry Issue?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Export Sentry Issue safe to use with an AI agent?

Its trust score is 51 out of 100 (fair). It passes 2 of the 3 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Export Sentry Issue still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.