create_recurring_calendar_event — haus MCP Tool Mutating
create_recurring_calendar_event
(create recurring calendar event) is one of 69 tools on the
haus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_recurring_calendar_event from your client
- Claude Code haus create_recurring_calendar_event run in your project directory
- Claude Desktop haus create_recurring_calendar_event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor haus create_recurring_calendar_event ~/.cursor/mcp.json
- VS Code haus create_recurring_calendar_event .vscode/mcp.json
- Zed haus create_recurring_calendar_event ~/.config/zed/settings.json
- Windsurf haus create_recurring_calendar_event ~/.codeium/windsurf/mcp_config.json
- Cline haus create_recurring_calendar_event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI haus create_recurring_calendar_event ~/.gemini/settings.json
- Grok haus create_recurring_calendar_event .mcp.json (in your project root)
- ChatGPT haus create_recurring_calendar_event Settings → Connectors → Advanced → Developer mode
- Claude.ai haus create_recurring_calendar_event Settings → Connectors → Add custom connector
- LangChain haus create_recurring_calendar_event pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http haus https://mcp.onehaus.appOther tools on this server
- create_contact
- update_contact
- delete_contact
- list_contacts
- create_appliance
- update_appliance
- delete_appliance
- list_appliances
- create_calendar_event
- update_calendar_event
- delete_calendar_event
- list_calendar_events
- create_document
- update_document
- delete_document
- list_documents
- create_pet
- update_pet
- delete_pet
- list_pets
- create_subscription
- update_subscription
- delete_subscription
- list_subscriptions
- create_vehicle
- update_vehicle
- delete_vehicle
- list_vehicles
- create_task
- update_task
- delete_task
- complete_task
- uncomplete_task
- assign_task
- list_tasks
- get_weather_forecast
- get_house
- list_house_members
- list_houses
- get_profile
- list_shopping_lists
- list_shopping_list_items
- add_shopping_list_item
- buy_shopping_list_item
- get_house_review
- defer_recommendation
- skip_recommendation
- store_memory
- update_memory
- forget_memory
- recall_memory
- create_meal_plan
- update_meal_plan
- delete_meal_plan
- list_meal_plans
- create_recipe
- update_recipe
- delete_recipe
- list_recipes
- list_global_recipes
- batch_add_shopping_list_items
- update_shopping_list_item
- remove_shopping_list_item
- update_recurring_calendar_event
- delete_recurring_calendar_event
- create_recurring_task
- update_recurring_task
- delete_recurring_task
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.