timer_schedule — zerm MCP Tool

timer_schedule (timer schedule) is one of 24 tools on the zerm MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call timer_schedule from your client

Claude Code zerm timer_schedule run in your project directory
Claude Desktop zerm timer_schedule ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor zerm timer_schedule ~/.cursor/mcp.json
VS Code zerm timer_schedule .vscode/mcp.json
Zed zerm timer_schedule ~/.config/zed/settings.json
Windsurf zerm timer_schedule ~/.codeium/windsurf/mcp_config.json
Cline zerm timer_schedule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI zerm timer_schedule ~/.gemini/settings.json
Grok zerm timer_schedule .mcp.json (in your project root)
ChatGPT zerm timer_schedule Settings → Connectors → Advanced → Developer mode
Claude.ai zerm timer_schedule Settings → Connectors → Add custom connector
LangChain zerm timer_schedule pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http zerm https://zerm.dev/mcp

Other tools on this server

kv_set
kv_get
kv_delete
kv_list
timer_verify_origin
timer_cancel
timer_status
name_check
email_check
url_check
cron_next
regex_test
fixture_rows
tz_convert
tz_info
dns_query
request_tool
lock_acquire
lock_release
counter_next
inbox_create
inbox_poll
inbox_delete

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.

zerm MCP server