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