MCP Hub
Back to servers

Telebugs MCP Server

An MCP server that enables AI agents to retrieve and analyze error reports from a self-hosted Telebugs instance. It provides tools for listing projects, searching error groups, and fetching detailed reports directly from the Telebugs SQLite database.

Updated
Jan 23, 2026

Telebugs MCP Server

An MCP (Model Context Protocol) server that allows AI agents to retrieve error reports from Telebugs, a self-hosted Sentry alternative.

Architecture

┌─────────────────┐                           ┌─────────────────────────────────────┐
│  Local Machine  │                           │              Remote VPS             │
│                 │         HTTPS             │                                     │
│  Claude Desktop │ ◄───────────────────────► │  Bun MCP Server   ───►  Telebugs    │
│                 │      (SSE transport)      │     :3100              SQLite DB    │
└─────────────────┘                           └─────────────────────────────────────┘

Features

  • Direct database access - Reads from Telebugs SQLite database (read-only)
  • API key authentication - Uses existing Telebugs user API keys
  • Access control - Users only see projects they're members of
  • SSE transport - Allows remote Claude Desktop connections
  • Token efficient - Compact JSON, defaults to open errors only
  • Single binary - Cross-compile to Linux, no runtime dependencies

Available Tools

ToolDescription
list_projectsList all accessible projects
list_error_groupsList deduplicated error groups with filtering
get_error_groupGet details of a specific error group
list_reportsList individual error occurrences
get_reportGet full report with backtrace, breadcrumbs, context
get_statisticsGet aggregated error statistics
search_errorsFull-text search across errors

list_error_groups

ParameterTypeDefaultDescription
project_idnumber-Filter by project ID
statusstring"open""open", "resolved", "muted", or "all"
error_typestring-Filter by exact error type
error_messagestring-Filter by error message (substring match)
fromstring-Start date (ISO 8601)
tostring-End date (ISO 8601)
limitnumber20Max results (1-100)
offsetnumber0Skip N results for pagination

Returns total_count for pagination.

list_reports

ParameterTypeDefaultDescription
group_idnumber-Filter by error group ID
project_idnumber-Filter by project ID
fromstring-Start date (ISO 8601)
tostring-End date (ISO 8601)
limitnumber20Max results (1-100)
offsetnumber0Skip N results for pagination

Returns total_count for pagination.

search_errors

ParameterTypeDefaultDescription
querystringrequiredFull-text search query
project_idnumber-Filter by project ID
limitnumber20Max results (1-100)

Installation

cd telebugs-mcp
bun install

Build

# Build for current platform
bun run build

# Build for Linux (for VPS deployment)
bun run build:linux

Configuration

VariableDescriptionDefault
TELEBUGS_DB_PATHPath to Telebugs SQLite database/var/lib/docker/volumes/telebugs-data/_data/db/production.sqlite3
PORTHTTP port to listen on3100

Running Locally

TELEBUGS_DB_PATH=/path/to/telebugs/storage/db/development.sqlite3 bun run dev

Deployment

Single Binary

# Copy to server
scp telebugs-mcp-linux root@your-server:~/telebugs-mcp-linux

# On server
chmod +x ~/telebugs-mcp-linux
./telebugs-mcp-linux

systemd Service

Copy telebugs-mcp.service to /etc/systemd/system/:

cp telebugs-mcp.service /etc/systemd/system/
systemctl daemon-reload
systemctl enable telebugs-mcp
systemctl start telebugs-mcp

Check status:

systemctl status telebugs-mcp

Nginx Reverse Proxy (Optional)

location /mcp {
    proxy_pass http://127.0.0.1:3100;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    # SSE support
    proxy_set_header Connection '';
    proxy_buffering off;
    proxy_cache off;
    chunked_transfer_encoding off;
}

Claude Desktop Configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "telebugs": {
      "url": "http://your-server:3100/mcp",
      "headers": {
        "Authorization": "Bearer your_telebugs_api_key"
      }
    }
  }
}

Getting Your API Key

  1. Log into your Telebugs instance
  2. Go to User → Account Settings → Security
  3. Copy your API key

Or query directly:

sqlite3 /path/to/production.sqlite3 "SELECT api_key FROM users WHERE active = 1;"

Security

  • Database opened in read-only mode
  • API keys validated against active users only
  • All queries filtered by user's project memberships
  • Parameterized queries (no SQL injection)

Health Check

curl http://localhost:3100/health
# {"status":"ok"}

License

MIT

Reviews

No reviews yet

Sign in to write a review