project-intake — abcommunity MCP Prompt
project-intake
is one of 2 prompts on the
abcommunity
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke project-intake from your client
- Claude Code abcommunity Prompt/project-intake run in your project directory
- Claude Desktop abcommunity Prompt/project-intake ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor abcommunity Prompt/project-intake ~/.cursor/mcp.json
- VS Code abcommunity Prompt/project-intake .vscode/mcp.json
- Zed abcommunity Prompt/project-intake ~/.config/zed/settings.json
- Windsurf abcommunity Prompt/project-intake ~/.codeium/windsurf/mcp_config.json
- Cline abcommunity Prompt/project-intake ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI abcommunity Prompt/project-intake ~/.gemini/settings.json
- Grok abcommunity Prompt/project-intake .mcp.json (in your project root)
- ChatGPT abcommunity Prompt/project-intake Settings → Connectors → Advanced → Developer mode
- Claude.ai abcommunity Prompt/project-intake Settings → Connectors → Add custom connector
- LangChain abcommunity Prompt/project-intake pip install langchain-mcp-adapters
Other prompts on this server
abcommunity 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 14 November 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.