Skip to content

Update MCP command to use scoped package name#39

Merged
nicnocquee merged 1 commit intomainfrom
fix-mcp
Mar 15, 2026
Merged

Update MCP command to use scoped package name#39
nicnocquee merged 1 commit intomainfrom
fix-mcp

Conversation

@nicnocquee
Copy link
Owner

Summary

Updates MCP install and config to use the scoped package name @nicnocquee/dataqueue instead of dataqueue-cli, so the MCP server command matches the published package and works correctly when users run the install flow.

Important changes

  • Default MCP server config now uses npx @nicnocquee/dataqueue mcp instead of npx dataqueue-cli mcp
  • Success log message after MCP install shows the new command
  • Existing MCP configs written by this flow will use the scoped package name

Other changes

  • Test expectations and fixtures updated to assert the new command in install-mcp-command.test.ts

How to test

  1. From the repo root, run the MCP install (e.g. npx @nicnocquee/dataqueue mcp install or the equivalent entry point).
  2. Confirm the generated MCP config (e.g. in ~/.cursor/mcp.json or the path you use) has args: ['@nicnocquee/dataqueue', 'mcp'] for the dataqueue server.
  3. Run pnpm test in packages/dataqueue and confirm all tests pass.

- Changed instances of 'dataqueue-cli' to '@nicnocquee/dataqueue' in both the test and implementation files for the `upsertMcpConfig` function.
- Updated related assertions and log messages to reflect the new package name, ensuring consistency across the codebase.

These changes improve clarity and maintainability by aligning the command references with the scoped package structure.
@netlify
Copy link

netlify bot commented Mar 15, 2026

Deploy Preview for dataqueue-demo ready!

Name Link
🔨 Latest commit 0e0712a
🔍 Latest deploy log https://app.netlify.com/projects/dataqueue-demo/deploys/69b6dc62d295ea0008719a52
😎 Deploy Preview https://deploy-preview-39--dataqueue-demo.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Mar 15, 2026

Deploy Preview for docsdataqueuedev ready!

Name Link
🔨 Latest commit 0e0712a
🔍 Latest deploy log https://app.netlify.com/projects/docsdataqueuedev/deploys/69b6dc627e6f45000823ec37
😎 Deploy Preview https://deploy-preview-39--docsdataqueuedev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@nicnocquee nicnocquee merged commit 705a24a into main Mar 15, 2026
10 checks passed
@codecov
Copy link

codecov bot commented Mar 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.28%. Comparing base (a7c6ccd) to head (0e0712a).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #39   +/-   ##
=======================================
  Coverage   81.28%   81.28%           
=======================================
  Files          37       37           
  Lines        7011     7011           
  Branches      908      908           
=======================================
  Hits         5699     5699           
  Misses       1292     1292           
  Partials       20       20           
Flag Coverage Δ
e2e 98.83% <ø> (ø)
unit 76.68% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant