owner_block_time — Awning MCP Tool
owner_block_time
(owner block time) is one of 34 tools on the
Awning
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call owner_block_time from your client
- Claude Code Awning owner_block_time run in your project directory
- Claude Desktop Awning owner_block_time ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Awning owner_block_time ~/.cursor/mcp.json
- VS Code Awning owner_block_time .vscode/mcp.json
- Zed Awning owner_block_time ~/.config/zed/settings.json
- Windsurf Awning owner_block_time ~/.codeium/windsurf/mcp_config.json
- Cline Awning owner_block_time ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Awning owner_block_time ~/.gemini/settings.json
- Grok Awning owner_block_time .mcp.json (in your project root)
- ChatGPT Awning owner_block_time Settings → Connectors → Advanced → Developer mode
- Claude.ai Awning owner_block_time Settings → Connectors → Add custom connector
- LangChain Awning owner_block_time pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http awning https://api.awning.help/mcp
Other tools on this server
- search_businesses
- get_business
- get_availability
- create_hold
- create_booking
- get_booking
- cancel_booking
- my_bookings
- my_profile
- logout
- owner_import_source
- owner_setup
- owner_photos
- owner_preview
- owner_submit
- owner_status
- owner_list_bookings
- owner_get_schedule
- owner_decide_booking
- owner_cancel_booking
- owner_pause
- owner_update_business
- owner_set_schedule
- owner_update_offering
- owner_upsert_sessions
- op_connect_telegram
- op_applications
- op_decide_application
- op_leads
- op_decide_lead
- op_analytics
- op_businesses
- op_suspend_business
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.