compare_coworking_spaces — CoworkingView MCP Prompt
compare_coworking_spaces
is one of 3 prompts on the
CoworkingView
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke compare_coworking_spaces from your client
- Claude Code CoworkingView Prompt/compare_coworking_spaces run in your project directory
- Claude Desktop CoworkingView Prompt/compare_coworking_spaces ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CoworkingView Prompt/compare_coworking_spaces ~/.cursor/mcp.json
- VS Code CoworkingView Prompt/compare_coworking_spaces .vscode/mcp.json
- Zed CoworkingView Prompt/compare_coworking_spaces ~/.config/zed/settings.json
- Windsurf CoworkingView Prompt/compare_coworking_spaces ~/.codeium/windsurf/mcp_config.json
- Cline CoworkingView Prompt/compare_coworking_spaces ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CoworkingView Prompt/compare_coworking_spaces ~/.gemini/settings.json
- Grok CoworkingView Prompt/compare_coworking_spaces .mcp.json (in your project root)
- ChatGPT CoworkingView Prompt/compare_coworking_spaces Settings → Connectors → Advanced → Developer mode
- Claude.ai CoworkingView Prompt/compare_coworking_spaces Settings → Connectors → Add custom connector
- LangChain CoworkingView Prompt/compare_coworking_spaces pip install langchain-mcp-adapters
Other prompts on this server
CoworkingView also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.