docs: add Claude desktop app (Cowork) MCP setup + Teams admin note#6774
docs: add Claude desktop app (Cowork) MCP setup + Teams admin note#6774dgirvin wants to merge 3 commits into
Conversation
- Add 'Configure in Claude Desktop App (Cowork)' section with claude_desktop_config.json path (macOS/Windows) and JSON config - Add Teams/Enterprise admin controls note (Admin > Capabilities) - Update Prerequisites to call out both supported clients - Update Known Limitations to clarify desktop app support - Clarify that org-level MCP directories are not a real config path"
|
Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please sign your name here and we will add you to our approved list of contributors. |
- Replace incorrect claude_desktop_config.json references with ~/.claude.json
(claude_desktop_config.json is for the separate Claude Desktop chat app,
not Claude Code or Cowork)
- Remove clientSecret from JSON config - it is stored in system keychain,
not in the config file
- Reframe desktop/Cowork section: CLI command is the recommended path;
Connectors UI (Code tab) and direct JSON edit are alternatives
- Correct JSON format per official docs: {type, url, oauth: {clientId, callbackPort}}
|
Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please sign your name here and we will add you to our approved list of contributors. |
The OAuth client is an application credential, not per-user. The admin creates it once and shares client ID + secret with the team. Non-admin team members only need to run claude mcp add with those shared credentials and authenticate as themselves via browser OAuth. Previous doc implied every user needed admin access, which made team rollout impossible.
|
Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please sign your name here and we will add you to our approved list of contributors. |
kimsauce
requested review from
JV0812,
amee-sumo,
kimsauce and
mafsumo
as code owners
|
@dgirvin , can you please sync your fork with the latest |
2 participants
Problem
The current
mcp-server.mdonly documents setup for Claude Code CLI. Users on the Claude desktop app (Cowork) — particularly on Teams/Enterprise accounts — have been failing because:claude mcp addis a CLI command that doesn't apply to the desktop appclaude_desktop_config.jsonis never mentionedorg-plugins) which is not a real Claude config path — the doc should clarify thisChanges
claude_desktop_config.jsonlocation (macOS/Windows), JSON config format with OAuth fields, restart instructions, and a per-machine caveatReview notes
oauthkey format in the desktop app JSON config (clientId,clientSecret,callbackPort) should be verified by someone who can test the desktop app OAuth flow end-to-end — flag if the field names differ from the actual implementation.