tick_next_runs — Tick MCP Tool
tick_next_runs
(tick next runs) is one of 2 tools on the
Tick
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tick_next_runs from your client
- Claude Code Tick tick_next_runs run in your project directory
- Claude Desktop Tick tick_next_runs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tick tick_next_runs ~/.cursor/mcp.json
- VS Code Tick tick_next_runs .vscode/mcp.json
- Zed Tick tick_next_runs ~/.config/zed/settings.json
- Windsurf Tick tick_next_runs ~/.codeium/windsurf/mcp_config.json
- Cline Tick tick_next_runs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tick tick_next_runs ~/.gemini/settings.json
- Grok Tick tick_next_runs .mcp.json (in your project root)
- ChatGPT Tick tick_next_runs Settings → Connectors → Advanced → Developer mode
- Claude.ai Tick tick_next_runs Settings → Connectors → Add custom connector
- LangChain Tick tick_next_runs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tick https://tick.clawhard.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.