Summary
Two tools, and the reason it stays at two is that the warehouse already did the hard part.
The connector has already landed the data; the only thing missing was a way to ask about it in the place you are working. Listing then fetching is the whole surface, which makes this cheap to leave connected and easy to reason about. It is worth nothing at all without the Snowflake side already running, so check that first.
What it is
A reader for Fresha's data connector as it lands in Snowflake — so salon and clinic business data is queryable where the rest of your warehouse is.
What you get
- list_fresha_reports — what is available
- get_fresha_report — the contents of one
Requirements
Npm, and a Fresha data connector already delivering into Snowflake. MIT licensed.
Setup effort
One command plus a key — npm install -g mcp-fresha, then supply credentials