Files
Gabriel Brown eb0056ac94 Register the self-hosted Sentry MCP server and keep OAuth sign-ins across updates
link-mcp gains a stdio transport: the servers row names a launcher under user/agents/mcp/, run from the checkout so every machine runs the same script, and the token reaches it as MCP_TOKEN. sentry-gbrown is the first, pointing Sentry's MCP server at sentry.gbrown.org with a read-only token from the ignored env file.

A server already registered exactly as its row would register it is now left alone. Re-adding it every run threw away the sign-in of the OAuth servers, bill-tracker and atlassian, on every update.
2026-10-01 17:33:12 -04:00

13 lines
693 B
Bash
Executable File

#!/usr/bin/env bash
# Sentry's MCP server, pointed at the self-hosted sentry.gbrown.org.
#
# link-mcp registers this file as a stdio server and hands it the token as
# MCP_TOKEN, read from SENTRY_GBROWN_TOKEN in user/agents/mcp/env. The token is
# a read-only personal token (Sentry > User settings > Personal Tokens, scopes
# alerts/event/org/project/team:read). The hosted sentry.io server cannot reach
# a self-hosted instance, which is why this one runs locally.
set -euo pipefail
: "${MCP_TOKEN:?MCP_TOKEN is not set; register this server through link-mcp}"
export SENTRY_ACCESS_TOKEN="$MCP_TOKEN"
exec npx -y @sentry/mcp-server@latest --host=sentry.gbrown.org --organization-slug=sentry