{"id":"phialsbasement-scheduler-mcp","name":"scheduler-mcp","homepage":null,"repo_url":"https://github.com/PhialsBasement/scheduler-mcp","category":"automation","subcategories":[],"tags":["mcp","scheduler","cron","automation","task-management","python","ai-integration","stdio-transport","sse","sqlite"],"what_it_does":"Provides an MCP (Model Context Protocol) server that lets clients schedule and manage automated tasks using cron expressions. Tasks can include shell commands, HTTP/API calls, AI prompt executions (via OpenAI), and desktop reminders/notifications. It persists tasks/execution history in a SQLite DB and can run over stdio or SSE (HTTP), including an auto-discovery endpoint for MCP schema.","use_cases":["Cron-based automation of recurring scripts/commands","Scheduled polling of external HTTP APIs","Automated report generation or content drafting driven by LLM prompts","On-user-machine reminders via desktop notifications","MCP client integration (e.g., Claude Desktop) to create/manage scheduled tasks"],"not_for":["High-security environments without additional hardening (no explicit auth/TLS details in docs)","Executing untrusted shell commands or untrusted AI-generated prompts without sandboxing/validation","Multi-tenant production use cases that require strong per-user authorization boundaries","Use cases needing strict SLA guarantees or documented uptime"],"best_when":"You control the deployment environment (local or trusted internal network), want MCP integration for an AI assistant to create/manage scheduled tasks, and are comfortable securing secrets (OpenAI key) and the host machine environment.","avoid_when":"You need robust, documented authentication/authorization and rate limiting for external callers, or you cannot mitigate risks from scheduled shell execution (command injection/abuse) and outbound network calls.","alternatives":["General-purpose schedulers (cron/systemd timers) for shell-only tasks","Workflow tools like Airflow/Prefect/Temporal for richer orchestration","Server-side job runners with REST APIs (e.g., cron-like APIs)","MCP-compatible automation servers if available in your stack","Custom lightweight MCP server wrapping your existing scheduler and execution sandbox"],"af_score":54.0,"security_score":34.5,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:20:06.844771+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["None described for MCP server transport itself","OpenAI API key for AI tasks via OPENAI_API_KEY"],"oauth":false,"scopes":false,"notes":"Docs describe an OpenAI API key for AI tasks, but do not describe authentication/authorization for the MCP server endpoints/tools. That implies access control may be absent or deployment-provided (not documented)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; costs likely come from OpenAI usage for AI tasks plus infrastructure hosting."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":54.0,"security_score":34.5,"reliability_score":27.5,"mcp_server_quality":78.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":25.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":20.0,"scope_granularity":20.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"Potential risks: (1) Scheduled shell command execution can be abused if task inputs are attacker-controlled; sandboxing/allowlisting is not described. (2) No documented authentication/authorization for MCP tools/endpoints; exposure over network transports could permit unauthorized task creation/execution. (3) AI tasks require OPENAI_API_KEY; docs do not specify whether keys are stored securely (vs. config/environment) or whether logs redact secrets. (4) TLS requirements for SSE/HTTP transport are not specified in the README. (5) Dependency hygiene and CVE status are not verifiable from provided content.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":0.0,"error_recovery":65.0,"idempotency_support":"false","idempotency_notes":"The README lists operations like add/update/remove/run_task_now but does not document idempotency behavior for repeated tool calls.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Scheduled shell/API/AI tasks can have side effects; ensure you fully validate parameters before calling add_* tools.","If running over SSE, the schema auto-discovery endpoint appears on HTTP port+1; clients must know this convention.","No documented auth/rate-limit semantics for the MCP server tools; assume deployment may be permissive unless otherwise configured."]}}