ToolsConnector
Planity
Read and manage salon appointments, clients and revenue stats, from Claude or ChatGPT, through Tulina's own MCP server on Planity's own login screen.
Official site: planity-mcp.oto.zone
What it can do
1 read/1 write
- 01Write
Read and manage appointments and clients
- 02Read
Read revenue and activity stats
Credentials sit in the vault behind a federated connection, not in a prompt. A federated connection like this puts the vendor's own consent screen between the model and the account, on top of whatever a workspace sets.
How do you connect Planity to Claude and ChatGPT?
Through Tulina's own MCP server, layered on top of Planity's own login screen — credentials sit in the vault, not in a prompt. Read and manage appointments and clients, and read revenue and activity stats — from the same chat as Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Planity once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Planity at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Planity returns something usable instead of something generic.
Processes that run on Planity
None published yet.