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