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