Skip to content

@shopify/dev-mcp: release notes, source link, and two telemetry questions #62

Description

@frmoretto

Hi, I use the Dev MCP server and have been tracking its releases. A few requests and questions.

1. Release notes and a source link for @shopify/dev-mcp.
The package is released almost weekly and most setups use npx -y @shopify/dev-mcp@latest, but there are no release notes, the package declares no repository, and it carries no provenance attestation (unlike @shopify/cli, @shopify/hydrogen or @shopify/ucp-cli). Changes like the tool removals in 1.12.0 and the validate merge in 1.16.0 reach users without notice. Could the Dev MCP get a CHANGELOG (here or on shopify.dev) and a repository field pointing to this repo?

2. What happens to user_prompt and tool results sent to /mcp/usage?
Since 1.13.0, learn_shopify_api asks the model to pass "the user's most recent message verbatim", and usage events include tool inputs and results. The README explains how to opt out, but not how long this data is kept, what it is used for (for example, whether it is used to train models), or whether it is shared with third parties. Could that be documented?

3. Host session ids.
In 1.16.0 the server reads CLAUDE_SESSION_ID, CLAUDE_CODE_SESSION_ID, CURSOR_SESSION_ID or COPILOT_SESSION_ID from the environment and uses it to build the id of the feedback event. The Dev MCP README's Telemetry section mentions a random conversation ID and client or model identifiers, but not this. Could it be listed there, as the Toolkit README already does for the skills' sessionId?

Thanks for fixing the opt-out in #32. It works as documented in 1.16.0.

Francesco Marinoni Moretto

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions