zenityafor artisan teams
Your team's know-how, as tools. Callable from any agent through one gateway.
Package your team's workflows into tools once, and connect the MCP servers you already use. Everyone uses them from the agent they prefer, through one connection, granted per group, person, or channel.
Every agent, wired to every system, with one connection.
20 connections, and tools that live as files with whoever wrote them.
One connection per agent. Every tool in one project, in the cloud.
All your tools behind one code mode call. Fewer tokens, lower bills.
Your tools and the MCP servers you connect live in one pool, so the agent can write a short script that pipes one call into the next. Intermediate results stay in the script instead of passing back through the model on every step.
- connection for any agent
- 1
- fewer tokens
- 31%
- fewer agent turns
- 25%
- lower cost
- 23%
- fewer failed calls
- 55%
Measured across a set of real team workflows, each run with code mode and with the same tools called one by one. Every figure is the median of multiple runs per workflow.
Your workflows, shared as tools.
Everyone gets it, in the agent they like. 
Claude, 
ChatGPT, 
Cursor, a cloud agent, your own backend: each connects to one URL and gets every tool it is allowed to use.
Finance gets finance tools. Create a group for each team, then grant specific tools to a group, a single person, or a 
Slack channel.
The channel is the boundary. Your Slack bot passes the channel with every call, so in #marketing it simply has no invoice tools to reach for.
See what gets done. Track which tools people use, how often, and from which project, so you know which workflows earn their keep and which to build next.
Hand it to your devs. Or to Claude.
Projects live in git. Every tool is plain TypeScript in your repo. Review it in a pull request, merge it, and ship it with one command. LGTM 🚀
Bring the tool you keep rewriting.
A small private beta. Bring one tool and the agents that should call it; we build the rest with you.