get_next_project_action — abcommunity MCP Tool Read-only
get_next_project_action
(get next project action) is one of 13 tools on the
abcommunity
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_next_project_action from your client
- Claude Code abcommunity get_next_project_action run in your project directory
- Claude Desktop abcommunity get_next_project_action ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor abcommunity get_next_project_action ~/.cursor/mcp.json
- VS Code abcommunity get_next_project_action .vscode/mcp.json
- Zed abcommunity get_next_project_action ~/.config/zed/settings.json
- Windsurf abcommunity get_next_project_action ~/.codeium/windsurf/mcp_config.json
- Cline abcommunity get_next_project_action ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI abcommunity get_next_project_action ~/.gemini/settings.json
- Grok abcommunity get_next_project_action .mcp.json (in your project root)
- ChatGPT abcommunity get_next_project_action Settings → Connectors → Advanced → Developer mode
- Claude.ai abcommunity get_next_project_action Settings → Connectors → Add custom connector
- LangChain abcommunity get_next_project_action pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http abcommunity https://mcp.abcommunity.org/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.