The analytics half is what separates this from a record-CRUD wrapper: hubspot_get_pipeline_analytics, hubspot_get_sales_performance, hubspot_get_sales_analytics and hubspot_get_forecast_analytics return stage conversion, per-rep numbers, period aggregates and a forecast as data the model can reason over next to the deals that produced them. The write surface is narrower than the read surface — contacts and deals can be created and updated, while companies are read-only through hubspot_list_companies and hubspot_get_company. Analytics tools take explicit period, pipeline and owner scoping, so the answer is only as good as the scope you pass.
A HubSpot server that pairs contact, deal and company records with the aggregate sales analytics normally reached through the reporting UI
- Contact work end to end: query search, read by ID, create and update (hubspot_search_contacts, hubspot_get_contact, hubspot_create_contact, hubspot_update_contact).
- Deal work with paginated listing, read, create and update, plus the property list you want returned (hubspot_list_deals, hubspot_get_deal, hubspot_create_deal, hubspot_update_deal).
- The story around a deal: its complete change history, its notes, and every associated call, email or meeting (hubspot_get_deal_history, hubspot_get_deal_notes, hubspot_get_engagements_by_deal).
- Aggregate sales analytics for a period, scoped by pipeline, stage or deal owner (hubspot_get_sales_analytics).
- Pipeline analytics including conversion rates between stages, rep performance over a period by owner, and a forecast built from the current pipeline and past performance (hubspot_get_pipeline_analytics, hubspot_get_sales_performance, hubspot_get_forecast_analytics).
- Company records read by ID or listed with pagination (hubspot_list_companies, hubspot_get_company).
A HubSpot account and HUBSPOT_API_KEY.
One command plus a key — npx -y @scopiousdigital/server-hubspot, then supply credentials