[sebyx07]

What

Remove the internal GlitchTip host from this public repo.

Why

The hostname is internal infrastructure and has no reason to be published. The sentry-mcp server already reaches GlitchTip through ${SENTRY_HOST}, which the platform provisions per repo and a developer exports in the shell that launches the client, so nothing loses access.

Changes

• Drop the literal-URL glitchtip MCP entry; sentry-mcp is the one that remains, driven by ${SENTRY_HOST} and ${SENTRY_ACCESS_TOKEN}.
• Point any command docs at mcp__sentry-mcp, and any example DSN at a placeholder.

Verification

git grep glitchtip.infra over the tree returns nothing after this change, and .mcp.json parses as JSON. The host remains in git history, which this PR does not rewrite.

🤖 Generated with Claude Code

[developerz-ai]

✅ Reviewed — nothing blocking

0 actionable comment(s) · grounded on your code

_{⚠️ 1 config note(s): test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against}

_{⏱ 34s wall clock · gpt-6.1-sol via router · 1 model call(s) · 212 output token(s)}

_{🤖 developerz.ai — automated review, running on your model and your box.}

[developerz-ai]

Review summary — 2 file(s), 0 finding(s).

completed Removes the hard-coded internal MCP endpoint and updates command references to the existing environment-configured Sentry server. No blocking defects found in the supplied diff.

• test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against

🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/gpt-6.1-sol on box sebastian-2 — 18.7k in / 212 out over 1 call; cost unknown: no price on record for router/gpt-6.1-sol.