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