what_to_read_next — siftivo MCP Tool
what_to_read_next
(what to read next) is one of 12 tools on the
siftivo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call what_to_read_next from your client
- Claude Code siftivo what_to_read_next run in your project directory
- Claude Desktop siftivo what_to_read_next ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor siftivo what_to_read_next ~/.cursor/mcp.json
- VS Code siftivo what_to_read_next .vscode/mcp.json
- Zed siftivo what_to_read_next ~/.config/zed/settings.json
- Windsurf siftivo what_to_read_next ~/.codeium/windsurf/mcp_config.json
- Cline siftivo what_to_read_next ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI siftivo what_to_read_next ~/.gemini/settings.json
- Grok siftivo what_to_read_next .mcp.json (in your project root)
- ChatGPT siftivo what_to_read_next Settings → Connectors → Advanced → Developer mode
- Claude.ai siftivo what_to_read_next Settings → Connectors → Add custom connector
- LangChain siftivo what_to_read_next pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http siftivo https://api.siftivo.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.