What happened?
Two related problems with the local MCP server (@pascal-app/mcp) and cloud/local project sync:
-
Cloud-to-local bridge: We're building a pipeline where a room is scanned via Pascal Capture (iPad LiDAR) into a cloud project (editor.pascal.app/editor/<project_id>), and we want to operate on that project via the local MCP server (get_walls, export_json, etc.) instead of manually re-measuring. Testing shows the cloud web editor and the local MCP server are two entirely separate data stores: calling get_project_status against a real cloud project id from the local MCP server returns project_not_found.
-
Separate connection failure: in Claude's Cowork/Code environment, the Local MCP servers panel shows the pascal server status as "failed", with the error:
"Couldn't start this server for Cowork and Code sessions (they run their own copy of it), so they can't use its tools: Connection closed"
This is a different symptom from the draft-07 outputSchema error reported separately — this one is the server process itself failing to start when a second/independent copy is spawned for these session types.
Steps to reproduce
For (1):
- Scan a room with Pascal Capture on iPad, creating a cloud project at editor.pascal.app/editor/<project_id>
- Run the local MCP server (bunx @pascal-app/mcp) and call get_project_status with that same project id
- Observe project_not_found
For (2):
- Open Claude's Cowork/Code environment with @pascal-app/mcp configured as a local MCP server
- Check the Local MCP servers panel
- Observe status "failed" with "Connection closed"
Expected behavior
(1) A documented or supported way to load/sync a Pascal Capture cloud-scanned project into the local MCP server's project store, so walls scanned on an iPad can be worked on locally without manual re-entry.
(2) The local MCP server should start successfully as an independently-spawned copy (as Cowork/Code environments apparently require), not fail immediately with "Connection closed".
Browser & OS
No response
Screenshots or screen recordings
macOS (Claude Desktop + Claude Cowork/Code), Node/bun runtime via bunx @pascal-app/mcp
Additional context
No response
What happened?
Two related problems with the local MCP server (@pascal-app/mcp) and cloud/local project sync:
Cloud-to-local bridge: We're building a pipeline where a room is scanned via Pascal Capture (iPad LiDAR) into a cloud project (editor.pascal.app/editor/<project_id>), and we want to operate on that project via the local MCP server (get_walls, export_json, etc.) instead of manually re-measuring. Testing shows the cloud web editor and the local MCP server are two entirely separate data stores: calling get_project_status against a real cloud project id from the local MCP server returns project_not_found.
Separate connection failure: in Claude's Cowork/Code environment, the Local MCP servers panel shows the pascal server status as "failed", with the error:
"Couldn't start this server for Cowork and Code sessions (they run their own copy of it), so they can't use its tools: Connection closed"
This is a different symptom from the draft-07 outputSchema error reported separately — this one is the server process itself failing to start when a second/independent copy is spawned for these session types.
Steps to reproduce
For (1):
For (2):
Expected behavior
(1) A documented or supported way to load/sync a Pascal Capture cloud-scanned project into the local MCP server's project store, so walls scanned on an iPad can be worked on locally without manual re-entry.
(2) The local MCP server should start successfully as an independently-spawned copy (as Cowork/Code environments apparently require), not fail immediately with "Connection closed".
Browser & OS
No response
Screenshots or screen recordings
macOS (Claude Desktop + Claude Cowork/Code), Node/bun runtime via
bunx @pascal-app/mcpAdditional context
No response