cron-explain__cron_explain — Fatstack MCP Tool
cron-explain__cron_explain
(cron explain cron explain) is one of 14 tools on the
Fatstack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call cron-explain__cron_explain from your client
- Claude Code Fatstack cron-explain__cron_explain run in your project directory
- Claude Desktop Fatstack cron-explain__cron_explain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fatstack cron-explain__cron_explain ~/.cursor/mcp.json
- VS Code Fatstack cron-explain__cron_explain .vscode/mcp.json
- Zed Fatstack cron-explain__cron_explain ~/.config/zed/settings.json
- Windsurf Fatstack cron-explain__cron_explain ~/.codeium/windsurf/mcp_config.json
- Cline Fatstack cron-explain__cron_explain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fatstack cron-explain__cron_explain ~/.gemini/settings.json
- Grok Fatstack cron-explain__cron_explain .mcp.json (in your project root)
- ChatGPT Fatstack cron-explain__cron_explain Settings → Connectors → Advanced → Developer mode
- Claude.ai Fatstack cron-explain__cron_explain Settings → Connectors → Add custom connector
- LangChain Fatstack cron-explain__cron_explain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http registry https://www.fatstack.net/api/mcpOther tools on this server
- fatstack__free_demo
- echo__echo_json
- json-schema-validate__json_schema_validate
- html-to-markdown__html_to_markdown
- url-metadata__url_metadata
- csv-to-json__csv_to_json
- text-language-detect__text_language_detect
- regex-test__regex_test
- unit-convert__unit_convert
- uuid-batch__uuid_batch
- markdown-lint__markdown_lint
- askzephy-quick-scan__sol_audit
- askzephy-quick-scan__sol_quick_scan
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.