Docs Feedback: /products/mcp/claude-desktop

[therickfactr]

Page URL

https://docs.pieces.app/products/mcp/claude-desktop

What’s wrong?

1. On macOS, the location of the Claude configuration file has moved to ~/.claude.json.
2. MCP servers are now defined (and, thus, enabled) per project. Claude pre-populated my config file with 9 different projecgts - legit ones, though - and it looks like I have to configure Pieces' MCP server for every project where I want to use it.
3. Even after adding the Pieces MCP server to every project, Claude Code in VS Code, still doesn't see it.

Suggested fix (optional)

Not sure what to do.

Additional context

[nolan-at-pieces]

So sorry about the delay in response. These are FANTASTIC comments. Thank you so much - will be looking into it. Will also look into Claude Code and MCP servers in VS Code.

[nolan-at-pieces]

@therickfactr
After further review, yes you're right. Though, this was written for Claude Desktop. I will be adding a new section for Claude Code; Since Claude Code was newer and not as widely used, I hadn't added docs for this implementation, but now that it's popping off: it definitely makes sense (20/20 hindsight)!

In the meantime, you can add a local_user MCP server to CC with the command: claude mcp add --scope user PiecesMCP --transport sse SSE_MCP_URL. This will set it up, so that you can use PiecesMCP across all of your Claude Code projects.

This will be documented in the next documentation release.

As for Claude Code not seeing the MCP in VSCode, it's a bit outside of my scope, as it seems to be an issue with VSCode and/or Claude Code. I would recommend trying the command I sent above and VSC restart to see if that fixes your issue. You can also look for any VSC environment files that may be automatically disabling the MCP. This setting is typically found under the tag: disabledMcpjsonServers.

Let me know if this all helps, thank you!