Conversation
yhsieh1
requested review from
clavery,
patricksullivansf and
wei-liu-sf
as code owners
docs/guide/index.md
Outdated
| **Claude Code:** | ||
| ```bash | ||
| cd /path/to/your/project | ||
| claude mcp add --transport stdio b2c-dx -- npx -y @salesforce/b2c-dx-mcp --allow-non-ga-tools |
There was a problem hiding this comment.
We should default to project level for claude. Is that the default with the claude CLI?
Same for plugin install when we have it. That's what we document in the plugin docs: https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/agent-skills.html#install-plugins
And we really should take advantage of the tabbed code examples. In the above we give both project and user install options in a single block. Vitepress supports this so we should use it
There was a problem hiding this comment.
Its default to local scope which similar to project scope but the configuration is ~/.claude.json. I will update it to project scope to match our recommendation also use tabs to include user scope.
| 1. Flags (`--api-key`, `--project`, `--environment`) | ||
| 2. Environment variables (`MRT_API_KEY`, `MRT_PROJECT`, `MRT_ENVIRONMENT`) | ||
| 1. Flags (`--api-key`, `--project`, `--environment`, `--cloud-origin`) | ||
| 2. Environment variables (`MRT_API_KEY`, `MRT_PROJECT`, `MRT_ENVIRONMENT`, `MRT_CLOUD_ORIGIN`) |
There was a problem hiding this comment.
weird to remove MRT_CLOUD_ORIGIN from here but leave it below; whereas optional MRT_ENVIRONMENT is still in both?
There was a problem hiding this comment.
both MRT_CLOUD_ORIGIN and MRT_ENVIRONMENT are listed and both are optional.
| } | ||
| } | ||
| ``` | ||
| **Cursor:** [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=b2c-dx&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBzYWxlc2ZvcmNlL2IyYy1keC1tY3AiLCItLXByb2plY3QtZGlyZWN0b3J5IiwiJHt3b3Jrc3BhY2VGb2xkZXJ9IiwiLS1hbGxvdy1ub24tZ2EtdG9vbHMiXX0=) |
There was a problem hiding this comment.
is the setup of this magic string documented in our contributing guide? i assume we'll need to change it occasionally in the future.
docs/mcp/configuration.md
Outdated
| } | ||
| } | ||
| ``` | ||
| Telemetry is enabled by default and collects anonymous usage data to help improve the developer experience. To disable it, set `SFCC_DISABLE_TELEMETRY=true` in your MCP client configuration's `env` object. |
There was a problem hiding this comment.
i think we should keep the explicit note about what we don't collect here. otherwise users will opt out because of fear we are collecting something sensitive?
There was a problem hiding this comment.
That's a good point. I will put them back.
|
|
||
| The MCP server collects anonymous usage telemetry to help improve the developer experience. Telemetry is enabled by default. | ||
|
|
||
| **Development mode**: Telemetry is automatically disabled when using `bin/dev.js`, so local development and testing won't pollute production data. |
There was a problem hiding this comment.
do we put this and the SFCC_APP_INSIGHTS_KEY note in the MCP contributing doc. maybe, maybe not?
There was a problem hiding this comment.
I updated CONTRIBUTION.md with telemetry development.
3 participants
Summary
Update MCP docs:
Testing
Dependencies
3pl-approvedis set by a maintainerpnpm test)pnpm run format)