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