Repository navigation
chore(mcp): Update the MCP Registry manifest - #1986
Merged
Merged
Conversation
Point repository.url at getsentry/toolkit (sentry-mcp now redirects there), add title, websiteUrl, and icons, and make SENTRY_AUTH_TOKEN optional: `auth login` works without it. Declare SENTRY_HOST and SENTRY_URL, which the CLI reads for self-hosted Sentry. Co-Authored-By: David Cramer <23610+dcramer@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sentry-junior Bot
added a commit
that referenced
this pull request
Nov 5, 2026
Add a vitest linter for the initialize and tools/list surface in mcp-core, a structured-output guard for the mcp-core suite, and server.json checks in @sentry/mcp-server, so the MCP metadata we just added does not drift back. Tools whose outputSchema PR is still open, and server.json checks that wait on #1986, are listed as pending and fail once they pass, so the PR that lands each one also deletes its entry. Co-Authored-By: David Cramer <23610+dcramer@users.noreply.github.com>
7 tasks done
This was referenced Nov 7, 2026
sentry-junior Bot
added a commit
that referenced
this pull request
Nov 7, 2026
The MCP Registry drops false booleans from a listing, so after #1986 spelled out isRequired: false and isSecret: false, the listing no longer deep-equals server.json. Craft's mcp-registry target checks exactly that after publishing, so the 0.49.0 publish failed there, and a retry fails the same check against the existing listing. Leave the fields out (false is their default) and add a server.json check that keeps them out. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
kashish00208
pushed a commit
to kashish00208/toolkit
that referenced
this pull request
Nov 8, 2026
The MCP Registry drops false booleans from a listing, so after getsentry#1986 spelled out isRequired: false and isSecret: false, the listing no longer deep-equals server.json. Craft's mcp-registry target checks exactly that after publishing, so the 0.49.0 publish failed there, and a retry fails the same check against the existing listing. Leave the fields out (false is their default) and add a server.json check that keeps them out. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the metadata that
server.jsonpublishes to the MCP Registry.repository.urlnow points atgetsentry/toolkit.getsentry/sentry-mcp301-redirects there, andpackages/mcp-server/package.jsonalready uses it. Thesubfolderstayspackages/mcp-server.SENTRY_AUTH_TOKENis nowisRequired: false, becausenpx -y @sentry/mcp-server auth loginworks without it (seepackages/mcp-server/README.md). The live listing still declares the oldSENTRY_ACCESS_TOKENas required.SENTRY_HOSTandSENTRY_URLas optional, non-secret variables.getConfiguredSentryUrlinpackages/cli/src/lib/constants.tsreadsSENTRY_HOSTfirst, thenSENTRY_URL.title: "Sentry",websiteUrl: https://mcp.sentry.dev, and an icon, matching the serverInfo fields.Depends on #1985 for the icon.
https://mcp.sentry.dev/sentry-icon.pngis served only once #1985 merges and Cloudflare deploys. This manifest reaches the registry only at the next CLI release, so merge #1985 first, or at least before the release.Craft: the
mcp-registrytarget (.craft.yml) only overwritesversionandpackages[].versionand sends every other field as written, so it keeps the new fields. After publishing, it deep-compares the listing with the manifest. The liveio.github.getsentry/sentry-mcplisting returns its fields unchanged, and other listings already returntitle/websiteUrl/icons, so the check should pass. Registry versions are immutable, so these changes go live with the next release; existing versions don't change.Checks: passes validation against
https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json(ajv + ajv-formats). Rootpnpm run lintpasses. Typecheck and tests don't apply because no code changed. Rootpnpm run tsc/pnpm run testwere skipped because they build Cloudflare and upload source maps.via @dcramer.
--
View Session [Sentry]