Check your Otovo solar system and book, move or cancel visits, with your approval.
Scored across 4 tools
Each tool has a distinct role in a clear workflow: get_my_otovo reads portal data, find_inspection_times discovers appointment slots and creates a customer record, preview_change prepares a change, and confirm_change applies a prepared change. Overlaps around inspections or appointments are separated by phase and by account/no-account context.
All names use snake_case and are verb-first: confirm_change, find_inspection_times, get_my_otovo, preview_change. The only slight deviation is get_my_otovo, whose possessive object is less precise than the other action-oriented names, but overall consistency is strong.
Four tools is a compact, well-scoped surface for a broad customer portal: one read tool, one scheduling lookup tool, and a preview/confirm pair for mutations. Each tool earns its place and the count avoids exposing dozens of view-specific or action-specific endpoints.
The surface covers reading portal views and preparing/confirming a very wide range of booking, subscription, monitoring, billing, document, and lease actions. Some actions such as payments, document signing, lease bank setup, and subscribing are intentionally delegated to portal links rather than executed, which is a documented minor gap but not a major failure.
Carries out exactly the change one preview described, using its preview_id, with confirmed=true meaning the customer approved that preview. Each preview_id stands for one change. An appointment receipt with status reconciliation_required means the outcome is not yet known. A change can update the customer's visit, calendar, account, subscription or monitoring and sends them the notices the portal would. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.
Inputs: confirmed (required), preview_id (required).
Finds real inspection or panel-cleaning appointment times at a street address, for a person with no Otovo account or scheduling link. The times come from the dispatch planner, so a crew can reach the address in each one. Creates the person's customer record (name, contact details, address) so the planner can route to it; books nothing. Each returned slot is a selected_slot value for a request_inspection change. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.
Inputs: address (required), contact (required), notes, service_type, +1 more.
Reads what a customer can see in their Otovo portal, one view at a time. Changes nothing. With a scheduling code and no account, three views: booking_status (the address, services offered, the visit already scheduled and whether it can be moved or cancelled, open access questions, the support line), booking_options (code and service_type, optional week_start and location_id: bookable times for a new visit, best first) and reschedule_options (code, optional week_start: times the scheduled visit can move to). With a connected account, site_id selects one of the customer's sites when they have several: sites, profile, home, summary; monitoring (production now, equipment status, alerts and when each reading was taken; a missing or stale reading is not zero production), monitoring_page, monitoring_history (node_id, query range day|week|month|year and date), monitoring_devices (node_id), monitoring_device (node_id, device_id), monitoring_energy_rate; connect_system (the monitoring providers Otovo connects, the fields each connection needs and the portal's setup steps; id = one provider); energy, energy_usage (query start_date, end_date, granularity), energy_bills, energy_plans; service (visits, work orders, bookable services), appointment (id), appointment_tracking (id: where the crew is on the day), scheduling (what can be booked or moved, open access questions), booking_options (service_type, optional week_start) and reschedule_options (optional week_start); work_order (id), repair (id), site_report (id; photos stay in the portal); quotes, quote (id); billing, billing_records (query limit, cursor), billing_record (id; the invoice PDF is a portal link), payment_methods, subscription, subscription_plans, subscription_terms (query tier, billing_interval); documents (pending, signed, project and historical); leases, lease (id); hour_bank; notification_settings. Reading booking times for a connected customer can create their own Otovo scheduler link; nothing is sent to them. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.
Inputs: view (required), id, code, query, +6 more.
Prepares one change and returns a plain summary of exactly what it would do, with a preview_id. Changes nothing: the change happens only when that preview_id is confirmed. Without an account: book_appointment (code; body service_type, selected_slot exactly as booking_options returned it, location_id, property_details {someone_home_during_service, ok_to_proceed_without_customer, pets_on_property, gated_community, gate_code, dog_access_considerations, access_instructions}, expected_total_cents), reschedule_appointment (code; body selected_slot from reschedule_options), cancel_appointment (code; body reason), request_quote (body contact {first_name, last_name, email, phone, sms_consent: true when the customer agreed to texts, consent_label}, address {line1, line2, city, state, zip, country}, service_title in the customer's words, panel_count, notes, source) and request_inspection (body: the contact and address the times were found for, service_type, selected_slot, notes). A connected customer passes site_id instead of code for the three appointment changes, and also has: save_access_details (body property_details), reject_quote (id; body reason, lost_reason), connect_system (provider; body fields: the fields the connect_system view lists for that provider), disconnect_system (provider), set_energy_rate (body currency, importRatePerKwh, exportRatePerKwh as decimal strings), change_subscription_tier (body targetTier, billingInterval), cancel_subscription (body cancelAtPeriodEnd), resume_subscription, withdraw_document (id), update_notification_settings (body: the settings to change, as notification_settings names them), request_lease_offer (id; body language), accept_lease_offer (id; body quote_id). payment_method, payment, sign_document, lease_bank_account and subscribe are not carried out by this connector: previewing one returns the portal link where the customer does it themselves. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.
Inputs: change (required), id, body, code, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Read Appointo bookings, availability and subscriptions; create, reschedule and cancel bookings.
Read AgendaPro bookings, slots, clients, services and sales; create, update and cancel bookings.
Rooftop solar potential, RGE installer search and quote requests. France only, no API key.
Appointment scheduling: check availability, book, reschedule and cancel meetings, manage events.
Add one secure layer between your agents and this server.