Book meetings on each user's own calendar from inside your app. Also email and Slack posts; undo.
Scored across 1 tool
With a single tool there is no possibility of misselection; provision_app's purpose (create an app plus its key, mirroring POST /v1/auth/provision) is unambiguous. An agent cannot confuse it with anything else because nothing else is offered.
provision_app follows a clear verb_noun snake_case convention. A single name cannot violate consistency, and it is descriptive of the action performed.
A server named 'Harny Actions' exposing exactly one provisioning tool is far too thin for the apparent scope, which the description itself says spans memory, connected accounts, actions, and action records. Agents can only bootstrap an app and then hit a wall.
The surface covers only creation/provisioning; there is no way to retrieve an existing app/key, rotate or revoke a key, list connected accounts, or invoke actions. This is a one-way entry point with no lifecycle operations, which will cause agent dead ends after provisioning.
Set up Harny for an app with no account: memory, connected accounts, actions and the action record behind one key; makes a new app and its key, as POST /v1/auth/provision does. The answer carries the app key once, and the assistant is told to put it in the owner's secret store and nowhere else. Needs no key.
Inputs: app_name (required), customers, objective, model_preset, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Calendars, tasks, contacts, bookings and agent inboxes for your assistant. EU-hosted, OAuth.
Check availability, book meetings and find group times — without sharing your calendar.
Booking pages for your assistant: find slots, book, reschedule, cancel, time off and leads.
AI-native scheduling and booking: check availability, book meetings, share links.
Add one secure layer between your agents and this server.
