MCP Cron

Created By
jolksa year ago
MCP Server that schedule command or AI prompt
Overview

what is MCP Cron?

MCP Cron is a Model Context Protocol (MCP) server designed for scheduling and managing tasks through a standardized API, utilizing the go-mcp SDK for task scheduling capabilities.

how to use MCP Cron?

To use MCP Cron, clone the repository, build the application, and start the server using either SSE (Server-Sent Events) or stdio transport modes. You can then interact with the server via HTTP endpoints or standard input/output.

key features of MCP Cron?

  • Schedule tasks using cron expressions
  • Manage tasks through various MCP tools
  • Capture command output during task execution
  • Seamless integration with AI models and applications via MCP protocol

use cases of MCP Cron?

  1. Automating routine tasks on a schedule
  2. Integrating with AI applications for task management
  3. Running background jobs in a microservices architecture

FAQ from MCP Cron?

  • What programming language is MCP Cron built with?

MCP Cron is built using Go.

  • Is MCP Cron free to use?

Yes! MCP Cron is open-source and free to use under the MIT License.

  • How can I report issues or contribute?

You can report issues or contribute by visiting the project's GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jolks
Star
3
Language
Go
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago
Alloy

2 days ago