{"_id":"@alexsasgg/mcp-glitchtip","name":"@alexsasgg/mcp-glitchtip","dist-tags":{"latest":"0.1.3"},"versions":{"0.1.3":{"name":"@alexsasgg/mcp-glitchtip","version":"0.1.3","description":"An MCP server for GlitchTip error monitoring","type":"module","bin":{"mcp-glitchtip":"build/index.js"},"scripts":{"build":"tsc && node -e \"require('fs').chmodSync('build/index.js', '755')\"","prepare":"npm run build","watch":"tsc --watch","inspector":"npx @modelcontextprotocol/inspector build/index.js"},"repository":{"type":"git","url":"git+https://github.com/coffebar/mcp-glitchtip.git"},"author":{"name":"coffebar"},"license":"MIT","bugs":{"url":"https://github.com/coffebar/mcp-glitchtip/issues"},"homepage":"https://github.com/coffebar/mcp-glitchtip#readme","dependencies":{"@modelcontextprotocol/sdk":"^1.13.2","node-fetch":"^3.3.2","zod":"^3.25.67"},"devDependencies":{"@types/node":"^24.0.6","typescript":"^5.8.3"},"gitHead":"7f0d19d641b85e8f8a55f8cfcf37965dd1a5433b","_id":"@alexsasgg/mcp-glitchtip@0.1.3","_nodeVersion":"24.14.0","_npmVersion":"11.9.0","dist":{"integrity":"sha512-BElXBf1ejX488bD7Q6qdWDdP7Rt2nHVqoNRm50mbK6SM+B66hk5ZICt49zjvTUFknQWEOIo23iU+R49aDUFKJQ==","shasum":"fb7ee8f38a98111d54463f46e787bef5ebb16227","tarball":"https://registry.npmjs.org/@alexsasgg/mcp-glitchtip/-/mcp-glitchtip-0.1.3.tgz","fileCount":6,"unpackedSize":18246,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQDcQzfgVroUR3TImkQdALmA6ANkCA/+t+hcZCvXZCfACAIhAKQ1Z+Xw058R6C51UVi/63VWrocITLNEJ3vyZAkcG59+"}]},"_npmUser":{"name":"alexsasgg","email":"buterfeed@gmail.com"},"directories":{},"maintainers":[{"name":"alexsasgg","email":"buterfeed@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/mcp-glitchtip_0.1.3_1788976667096_0.733813479331942"},"_hasShrinkwrap":false}},"time":{"created":"2026-09-09T17:57:46.899Z","0.1.3":"2026-09-09T17:57:47.228Z","modified":"2026-09-09T17:57:47.467Z"},"maintainers":[{"name":"alexsasgg","email":"buterfeed@gmail.com"}],"description":"An MCP server for GlitchTip error monitoring","homepage":"https://github.com/coffebar/mcp-glitchtip#readme","repository":{"type":"git","url":"git+https://github.com/coffebar/mcp-glitchtip.git"},"author":{"name":"coffebar"},"bugs":{"url":"https://github.com/coffebar/mcp-glitchtip/issues"},"license":"MIT","readme":"# MCP GlitchTip\n\nAn MCP (Model Context Protocol) server that integrates GlitchTip error monitoring with AI assistants like Claude. This allows AI to analyze and help resolve errors from your GlitchTip instance.\n\n## What it does\n\nThis MCP server enables AI assistants to:\n\n- Fetch and analyze current issues from your GlitchTip instance\n- Get detailed error context including stack traces, user data, and breadcrumbs\n- Help debug and suggest solutions based on error patterns\n\n### Example Use Case\n\n```\nUser: \"Check GlitchTip for any payment-related errors\"\n\nAI Assistant:\n- Fetches all unresolved issues from GlitchTip\n- Identifies payment component errors\n- Analyzes stack traces and error patterns\n- Suggests specific fixes based on the error context\n```\n\n## Quick Start\n\n### 1. Get Your GlitchTip Credentials\n\nYou'll need:\n\n- **Authentication**: Either an API token (recommended) or Session ID Cookie\n- **Organization Slug**: Your organization identifier in GlitchTip\n- **Base URL** (optional): Your GlitchTip instance URL if self-hosted\n\n#### Authentication Options\n\n**Option 1: API Token (Recommended)**\n\n1. Log in to your GlitchTip instance\n2. Go to /profile/auth-tokens\n3. Create a new API token with appropriate permissions\n4. Copy the token for use as `GLITCHTIP_TOKEN`\n\n**Option 2: Session ID**\n\n1. Log in to your GlitchTip instance\n2. Open browser developer tools (F12)\n3. Go to Application/Storage > Cookies\n4. Find the `sessionid` cookie value\n5. Copy this value for use as `GLITCHTIP_SESSION_ID`\n\n### 2. Configure Your Project\n\nCreate a `.mcp.json` file in your project root:\n\n```json\n{\n  \"mcpServers\": {\n    \"glitchtip\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"mcp-glitchtip\"],\n      \"env\": {\n        \"GLITCHTIP_TOKEN\": \"your-api-token-here\",\n        \"GLITCHTIP_ORGANIZATION\": \"your-org-slug\",\n        \"GLITCHTIP_BASE_URL\": \"https://app.glitchtip.com\"\n      }\n    }\n  }\n}\n```\n\n**Note**: Add `.mcp.json` to your `.gitignore` to keep credentials secure:\n\n```bash\necho \".mcp.json\" >> .gitignore\n```\n\n### 3. Open Your Project in Claude Desktop\n\nWhen you open your project folder in Claude Desktop, it will automatically detect the `.mcp.json` configuration and connect to your GlitchTip instance.\n\n## Configuration Options\n\n| Environment Variable     | Required | Description                          | Default                     |\n| ------------------------ | -------- | ------------------------------------ | --------------------------- |\n| `GLITCHTIP_TOKEN`        | Yes*     | Your GlitchTip API token (recommended) | -                           |\n| `GLITCHTIP_SESSION_ID`   | Yes*     | Your GlitchTip session cookie        | -                           |\n| `GLITCHTIP_ORGANIZATION` | Yes      | Organization slug from GlitchTip URL | -                           |\n| `GLITCHTIP_BASE_URL`     | No       | GlitchTip instance URL               | `https://app.glitchtip.com` |\n\n*Either `GLITCHTIP_TOKEN` or `GLITCHTIP_SESSION_ID` is required. If both are provided, `GLITCHTIP_TOKEN` takes priority.\n\n### Self-Hosted GlitchTip\n\nIf you're using a self-hosted GlitchTip instance, update the `GLITCHTIP_BASE_URL`:\n\n```json\n\"GLITCHTIP_BASE_URL\": \"https://glitchtip.your-domain.com\"\n```\n\n## Available Tools\n\n### `glitchtip_issues`\n\nFetches all issues from GlitchTip (unresolved by default).\n\n**Usage**: \"Show me all GlitchTip errors\"\n\n### `glitchtip_latest_event`\n\nGets the most recent event for a specific issue with full error context.\n\n**Parameters**:\n\n- `issueId`: The issue ID to get details for\n\n**Usage**: \"Get details for GlitchTip issue #123\"\n\n## Available Resources\n\n### `glitchtip://issues`\n\nA resource endpoint that provides all current issues in JSON format.\n\n## Example Workflows\n\n### Debugging a Production Error\n\n```\nUser: \"Check GlitchTip for recent 500 errors\"\n\nAI: [Fetches issues] I found 3 recent 500 errors:\n1. DatabaseConnectionError in /api/users\n2. TimeoutError in payment processing\n3. ValidationError in checkout flow\n\nUser: \"Show me details about the payment timeout\"\n\nAI: [Gets latest event] The TimeoutError occurs when...\n[Provides stack trace analysis and suggested fixes]\n```\n\n### Monitoring Error Trends\n\n```\nUser: \"What are the most frequent errors in GlitchTip?\"\n\nAI: [Analyzes issue counts] The top errors by frequency are:\n1. CORS policy errors (145 occurrences)\n2. Missing authentication token (89 occurrences)\n3. Rate limit exceeded (67 occurrences)\n```\n\n## Development\n\n### Building from Source\n\n```bash\ngit clone https://github.com/coffebar/mcp-glitchtip.git\ncd mcp-glitchtip\nnpm install\nnpm run build\n```\n\n### Development Mode\n\n```bash\nnpm run watch  # Auto-rebuild on changes\n```\n\n### Testing with MCP Inspector\n\n```bash\nnpm run inspector\n```\n\nSet the required environment variables before running the inspector:\n\n```bash\nexport GLITCHTIP_TOKEN=\"your-api-token\"\n# OR export GLITCHTIP_SESSION_ID=\"your-session-id\"\nexport GLITCHTIP_ORGANIZATION=\"your-org\"\nnpm run inspector\n```\n\n## Troubleshooting\n\n### Authentication Errors\n\nIf you see \"Authentication failed. Check your token or session ID\":\n\n1. If using a token: Verify it's valid and has appropriate permissions\n2. If using a session ID: Your session may have expired - get a new session ID from GlitchTip\n3. Verify you're using the correct organization slug\n4. Check if your GlitchTip instance requires additional authentication headers\n\n### Connection Errors\n\nIf you see \"Failed to connect to GlitchTip\":\n\n1. Verify your `GLITCHTIP_BASE_URL` is correct\n2. Check if you're behind a proxy or firewall\n3. Ensure your GlitchTip instance is accessible from your network\n\n### No Issues Found\n\nIf the tool returns empty results:\n\n1. Verify there are actually issues in your GlitchTip project\n2. Check if your organization slug is correct\n3. Ensure your session has permission to view the issues\n\n## Security Notes\n\n- **Never commit `.mcp.json` to version control** - it contains sensitive credentials\n- For team usage, each developer should use their own API token or session ID\n\n## Contributing\n\nContributions are welcome! Please:\n\n1. Fork the repository\n2. Create a feature branch\n3. Make your changes\n4. Add tests if applicable\n5. Submit a pull request\n\n## License\n\nMIT License - see [LICENSE](LICENSE) file for details.\n\n## Support\n\n- **Issues**: [GitHub Issues](https://github.com/coffebar/mcp-glitchtip/issues)\n- **Documentation**: [GitHub README](https://github.com/coffebar/mcp-glitchtip#readme)\n- **GlitchTip Docs**: [GlitchTip Documentation](https://glitchtip.com/documentation)","readmeFilename":"README.md","_rev":"1-58df0ca07333c7ffcbe2165e21fa20f3"}