@awesomate/hosting-mcp 0.70.0 → 0.71.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@awesomate/hosting-mcp",
3
- "version": "0.70.0",
3
+ "version": "0.71.0",
4
4
  "description": "Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
5
5
  "license": "UNLICENSED",
6
6
  "type": "module",
@@ -1,5 +1,17 @@
1
1
  {
2
2
  "versions": [
3
+ {
4
+ "version": "0.71.0",
5
+ "highlights": [
6
+ "Bookings can now be connected to your Google Calendar from the hub: times you are busy in Google are never offered to customers, and every booking goes into an Awesomate bookings calendar in your Google account, moved and removed with it"
7
+ ]
8
+ },
9
+ {
10
+ "version": "0.70.1",
11
+ "highlights": [
12
+ "Portals Claude builds for you now load the current Awesomate SDK, so file uploads in your app work, and a page showing who is on a job in two places keeps both up to date"
13
+ ]
14
+ },
3
15
  {
4
16
  "version": "0.70.0",
5
17
  "highlights": [
@@ -79,5 +79,9 @@ themselves cannot be written through `awesomate_crm_write`; only these actions c
79
79
  Essentials, the tool answers `upgrade_required`: say the owner can do the same in the hub under
80
80
  Contacts, Bookings, and do not retry.
81
81
  - Payments and deposits are not part of bookings yet. Do not promise them; the price is shown only.
82
- - Two-way sync with the owner's own Google or Outlook calendar is not available yet: the notice
83
- email's invite is how a booking reaches their calendar. Do not promise automatic sync.
82
+ - **Google Calendar** is connected per calendar in the hub (Contacts, Bookings, Set up, Connect
83
+ Google Calendar), by the person whose calendar it is: Claude cannot connect it, so send them
84
+ there. Once connected, times they are busy in Google are never offered, and every booking is
85
+ written to an "Awesomate bookings" calendar in their Google account, moved and removed with it.
86
+ `setup` lists the connected calendars under `links`. Outlook is not available yet; there the
87
+ notice email's invite is how a booking reaches their calendar.
@@ -114,7 +114,7 @@ loads from a CDN, or from npm in a Vite app:
114
114
 
115
115
  ```html
116
116
  <script type="module">
117
- import { createAppClient, AwesomateError } from 'https://cdn.jsdelivr.net/npm/@awesomate/sdk@0.13/+esm';
117
+ import { createAppClient, AwesomateError } from 'https://cdn.jsdelivr.net/npm/@awesomate/sdk@0.18/+esm';
118
118
  const app = createAppClient({ publishableKey: 'pk_...' });
119
119
 
120
120
  // The email link signs them in by itself (also when it opens in a tab already on this page).