cron_next_run — Penniless Data Utilities MCP Tool
cron_next_run
(cron next run) is one of 9 tools on the
Penniless Data Utilities
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call cron_next_run from your client
- Claude Code Penniless Data Utilities cron_next_run run in your project directory
- Claude Desktop Penniless Data Utilities cron_next_run ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Penniless Data Utilities cron_next_run ~/.cursor/mcp.json
- VS Code Penniless Data Utilities cron_next_run .vscode/mcp.json
- Zed Penniless Data Utilities cron_next_run ~/.config/zed/settings.json
- Windsurf Penniless Data Utilities cron_next_run ~/.codeium/windsurf/mcp_config.json
- Cline Penniless Data Utilities cron_next_run ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Penniless Data Utilities cron_next_run ~/.gemini/settings.json
- Grok Penniless Data Utilities cron_next_run .mcp.json (in your project root)
- ChatGPT Penniless Data Utilities cron_next_run Settings → Connectors → Advanced → Developer mode
- Claude.ai Penniless Data Utilities cron_next_run Settings → Connectors → Add custom connector
- LangChain Penniless Data Utilities cron_next_run pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http penniless-data-utilities https://penniless-json-repair.sjaman.workers.dev/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.