Booking System (Fixed)

Created By
Konstrexa year ago
Fixed booking system with Google Calendar integration, email confirmations, and MCP Server integration
Overview

What is the Booking System (Fixed)?

The Booking System (Fixed) is a cloud-based booking solution that integrates with Google Calendar and MCP Servers, designed to streamline the booking process for users and businesses.

How to use the Booking System (Fixed)?

To use the system, clone the repository, install dependencies, configure environment variables for Google Calendar and email settings, and deploy it to Cloudflare Workers.

Key features of the Booking System (Fixed)?

  • Multi-step booking process for enhanced user experience
  • Real-time availability checking against Google Calendar
  • Automated email confirmations sent to customers
  • Integration with Google Calendar for event creation
  • MCP Server integration for improved backend processing
  • Comprehensive error handling and responsive design

Use cases of the Booking System (Fixed)?

  1. Scheduling appointments for service-based businesses
  2. Managing bookings for events and workshops
  3. Automating email notifications for confirmations and reminders

FAQ from the Booking System (Fixed)?

  • Can I customize the email templates?

Yes! You can modify the email settings in the configuration to suit your business needs.

  • Is the system scalable?

Yes! The system is designed to handle multiple bookings simultaneously and can be scaled as needed.

  • What technologies are used in this project?

The project is built using JavaScript and runs on Cloudflare Workers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Konstrex
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago