Skip to content

Fix the Claude Desktop guide: connector first, extension caveats - #82

Open
f wants to merge 7 commits into
mainfrom
fix/claude-desktop-plugin
Open

f wants to merge 7 commits into
mainfrom
fix/claude-desktop-plugin

Conversation

@f

@f f commented Oct 23, 2026 •

Copy link
Copy Markdown

content/agents/claude-desktop.mdx started with the .mcpb desktop extension. That extension spawns npx from Claude's built-in Node and fails ("Server disconnected" / "Unable to connect to extension server") when Claude Desktop can't find npx. Reported in #spacefast.

  • The guide now leads with the claude.ai custom connector (https://mcp.spacefast.com), including the Team/Enterprise owner requirement.
  • The spacefast/plugins plugin (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.
  • The verification prompt now asks Claude to make and publish a small page instead of "publish this folder", so it works without local files.
  • The extension section now states the Node.js 20.3+ / npx requirement and how to spot spawn npx ENOENT in the log. The extension starts the server through npx, and @spacefast/mcp only takes a folder path on the native Linux sf build, so the page now says the extension publishes inline files on every system and points to sf publish <path> for local folders.
  • The manifest table now matches the manifest's >=20 and notes the CLI's 20.3 minimum.
  • The agents index card is updated to match.

The matching setup-page change is spacefast/monorepo#4398. generated/setup/claude-desktop.md follows from that export.

npm run check passes and verify:public-safety passes.

View in Indent View in Slack
Tag @indent to continue the conversation here.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

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.
Copilot AI balanced review requested due to automatic review settings October 23, 2026 12:45
@indent

indent Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Issues

All clear! No issues remaining. 🎉

4 issues already resolved
  • The extension section says it needs Node.js 20 or newer, but the launched spacefast CLI requires Node 20.3+, as the quickstart and CLI pages state. On Node 20.0 to 20.2 the extension can still fail. (fixed by commit 1ef8623)
    Found by Indent Review Agent
  • The Claude Desktop card in content/agents/index.mdx still describes "A double-click desktop extension with an optional token field", but the guide now recommends the marketplace plugin first. Update the card text to match. (fixed by commit 388a56d)
    Found by Indent Review Agent
  • The "What the manifest declares" table now says Node 20.3 or newer, but the bundle manifest declares >=20. The 20.3 minimum comes from the launched CLI, so the table misquotes the manifest. (fixed by commit 50beff3)
    Found by Indent Review Agent
  • The extension section and the line after the manifest JSON say publishing by path "needs the native Linux sf build" and that macOS and Windows use inline files. This implies a Linux user can publish a folder by path through the extension, but the extension runs the server through npx, which only accepts inline files on every OS. (fixed by commit 0c3a1c3)
    Found by Indent Review Agent

CI Checks

All required CI checks passed on 0c3a1c3.

Review agents

Select any unchecked box below to run or rerun that agent.

Passed (1)
  • Indent Review Agent · Fix is correct; no remaining issues.
Full results

Indent Review Agent

  • Summary: Fix is correct; no remaining issues.
  • Last ran on commit: 0c3a1c37
  • Latest result
    {
      "summary": "Fix is correct; no remaining issues.",
      "findings": []
    }

@coderabbitai

coderabbitai Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6872689a-2c6c-4f3f-af2e-36166d4f5af1
✨ Finishing Touches: 💡 1
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Comment thread content/agents/claude-desktop.mdx Outdated
Comment thread content/agents/claude-desktop.mdx Outdated

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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 npx prerequisites 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

Comment thread content/agents/claude-desktop.mdx Outdated
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.
Comment thread content/agents/claude-desktop.mdx Outdated

## 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.
@indent indent Bot changed the title Lead the Claude Desktop guide with the Claude plugin marketplace Fix the Claude Desktop guide: connector first, extension caveats Oct 23, 2026
Comment thread content/agents/claude-desktop.mdx Outdated

This branch was successfully deployed

1 active deployment
preview/fix/claude-desktop-plugin — 0c3a1c37 Deployed Oct 23, 2026 by spacefast[bot]
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.

2 participants