Repository navigation
Conversation
The desktop extension spawns npx and fails when Claude Desktop can't find it. Recommend adding spacefast/plugins through Customize -> Plugins, keep the connector as a fallback, and document the extension's Node.js requirement and its spawn npx ENOENT failure.
|
All clear! No issues remaining. 🎉 4 issues already resolved
All required CI checks passed on
Select any unchecked box below to run or rerun that agent. Full resultsIndent Review Agent
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
✨ Finishing Touches: 💡 1
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟡 Changes recommended
The guide needs accurate publishing limitations, a hosted-compatible verification prompt, and the connector’s owner prerequisite.
3 open issues
What changed in this PR
Updates the Claude Desktop guide to recommend the Spacefast plugin marketplace first, while retaining connector and local-extension alternatives.
Changes:
- Adds marketplace installation steps, account sign-in, and plan requirements.
- Documents the extension’s Node.js and
npxprerequisites and connection-error troubleshooting. - Updates hosted-server and CLI guidance to mention the plugin.
| File | Description |
|---|---|
content/agents/claude-desktop.mdx |
Leads with plugin setup and expands local-extension troubleshooting. |
Review effort: Balanced
| Then ask for something small to prove the extension is live. | ||
| Plugins need a paid Claude plan. On a Team or Enterprise plan, an owner may limit which marketplaces you can add. See [Use plugins in Claude](https://support.claude.com/en/articles/13837440-use-plugins-in-claude). | ||
|
|
||
| You can also add only the connector: on claude.ai, open Customize → Connectors, choose + → Add custom connector, name it Spacefast, and use `https://mcp.spacefast.com` as its URL. |
|
|
||
| You can also add only the connector: on claude.ai, open Customize → Connectors, choose + → Add custom connector, name it Spacefast, and use `https://mcp.spacefast.com` as its URL. | ||
|
|
||
| Then ask for something small to prove Spacefast is connected. |
|
|
||
| ## Install the desktop extension | ||
|
|
||
| The extension runs the Spacefast MCP server on your computer, so `publish` can read local files. It starts the server with `npx`, so it needs Node.js 20 or newer with `npx` installed where Claude Desktop can find it. |
The plugin loads its skills but does not connect its Spacefast connector in chat yet, so the custom connector is the setup that works today. Keep the plugin as the second option, use a verification prompt that works without local files, and state that folder publishing by path needs the Linux sf build.

content/agents/claude-desktop.mdxstarted with the.mcpbdesktop extension. That extension spawnsnpxfrom Claude's built-in Node and fails ("Server disconnected" / "Unable to connect to extension server") when Claude Desktop can't findnpx. Reported in #spacefast.https://mcp.spacefast.com), including the Team/Enterprise owner requirement.spacefast/pluginsplugin (Customize → Plugins → Add marketplace) is the second option. It notes that you should add the connector if Claude says it isn't connected, which is what happens in chat today.npxrequirement and how to spotspawn npx ENOENTin the log. The extension starts the server throughnpx, and@spacefast/mcponly takes a folder path on the native Linuxsfbuild, so the page now says the extension publishes inline files on every system and points tosf publish <path>for local folders.>=20and notes the CLI's 20.3 minimum.The matching setup-page change is spacefast/monorepo#4398.
generated/setup/claude-desktop.mdfollows from that export.npm run checkpasses andverify:public-safetypasses.Tag
@indentto continue the conversation here.Need help on this PR? Tag
@codesmith-botwith what you need.