change to use the official Smartsheet remote MCP server#4
change to use the official Smartsheet remote MCP server#4smar-sean-sekora wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the Smartsheet Roo config-pack to use the official Smartsheet remote MCP server instead of running a local MCP server via npx.
Changes:
- Switches MCP configuration from a local
npx-launched server to a remote HTTP-based MCP server with anAuthorizationheader. - Updates the default Smartsheet endpoint to
https://mcp.smartsheet.comand removes the “allow delete tools” input. - Bumps the package version to
2.0.0(major change).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/assembly/roo-rocket/smartsheet/rocket.config.ts | Updates user prompts/default endpoint and removes the delete-tools parameter mapping. |
| src/assembly/@fuel-garage/smartsheet-mcp.json | Replaces local process config with remote httpUrl + auth header config. |
| package.json | Major version bump to reflect breaking behavior/config changes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| '{{SMARTSHEET_API_KEY}}': '$input-SMARTSHEET_API_KEY', | ||
| '{{SMARTSHEET_ENDPOINT}}': '$input-SMARTSHEET_ENDPOINT', |
There was a problem hiding this comment.
The fuel template no longer contains the {{SMARTSHEET_API_KEY}} / {{SMARTSHEET_ENDPOINT}} placeholders that variablesResolver maps, so these mappings appear unused and the prompted values may never be injected into the generated .roo/mcp.json. Align the placeholder syntax between variablesResolver and smartsheet-mcp.json (either switch the JSON back to {{...}} tokens or update the resolver/build step to replace the ${...} tokens).
| '{{SMARTSHEET_API_KEY}}': '$input-SMARTSHEET_API_KEY', | |
| '{{SMARTSHEET_ENDPOINT}}': '$input-SMARTSHEET_ENDPOINT', | |
| '${SMARTSHEET_API_KEY}': '$input-SMARTSHEET_API_KEY', | |
| '${SMARTSHEET_ENDPOINT}': '$input-SMARTSHEET_ENDPOINT', |
| "httpUrl": "${SMARTSHEET_ENDPOINT}", | ||
| "headers": { | ||
| "Authorization": "Bearer ${SMARTSHEET_API_KEY}" |
There was a problem hiding this comment.
This template uses ${SMARTSHEET_ENDPOINT} / ${SMARTSHEET_API_KEY}, but the accompanying rocket config’s variablesResolver is set up to resolve {{SMARTSHEET_ENDPOINT}} / {{SMARTSHEET_API_KEY}}. Unless the consumer of .roo/mcp.json performs ${...} interpolation at runtime, these values will remain unresolved. Use the same placeholder format that the build system actually replaces.
| "httpUrl": "${SMARTSHEET_ENDPOINT}", | |
| "headers": { | |
| "Authorization": "Bearer ${SMARTSHEET_API_KEY}" | |
| "httpUrl": "{{SMARTSHEET_ENDPOINT}}", | |
| "headers": { | |
| "Authorization": "Bearer {{SMARTSHEET_API_KEY}}" |
| resolver: { | ||
| operation: 'prompt', | ||
| label: 'Please enter your Smartsheet URL:', | ||
| label: 'Please enter your Smartsheet URL (https://developers.smartsheet.com/ai-mcp/smartsheet/install-the-smartsheet-mcp-server):', |
There was a problem hiding this comment.
The prompt label still asks for a generic “Smartsheet URL” but the default has changed to the remote MCP server base (https://mcp.smartsheet.com). To reduce misconfiguration (e.g., users entering the REST API base URL), consider updating the label text to explicitly request the “Smartsheet MCP server URL” and keep the documentation link as a separate hint.
| label: 'Please enter your Smartsheet URL (https://developers.smartsheet.com/ai-mcp/smartsheet/install-the-smartsheet-mcp-server):', | |
| label: 'Please enter your Smartsheet MCP server URL (see https://developers.smartsheet.com/ai-mcp/smartsheet/install-the-smartsheet-mcp-server for details):', |
No description provided.