owner_get_schedule — Awning MCP Tool
owner_get_schedule
(owner get schedule) 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_get_schedule from your client
- Claude Code Awning owner_get_schedule run in your project directory
- Claude Desktop Awning owner_get_schedule ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Awning owner_get_schedule ~/.cursor/mcp.json
- VS Code Awning owner_get_schedule .vscode/mcp.json
- Zed Awning owner_get_schedule ~/.config/zed/settings.json
- Windsurf Awning owner_get_schedule ~/.codeium/windsurf/mcp_config.json
- Cline Awning owner_get_schedule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Awning owner_get_schedule ~/.gemini/settings.json
- Grok Awning owner_get_schedule .mcp.json (in your project root)
- ChatGPT Awning owner_get_schedule Settings → Connectors → Advanced → Developer mode
- Claude.ai Awning owner_get_schedule Settings → Connectors → Add custom connector
- LangChain Awning owner_get_schedule pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http awning https://api.awning.help/mcpOther 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_decide_booking
- owner_cancel_booking
- owner_block_time
- 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.