USE CASES
Use cases. How teams use a private AI catalogue.
Joyst is the private team catalogue where you write, manage, version and share skills, prompts, MCP servers, secrets and agents across AI tools. See how platform teams and agencies put it to work.
WHO JOYST IS FOR
Teams running AI across tools
- Platform teams
Govern approved skills and a private list of approved MCP servers beside your developer portal, not instead of it.
- Agencies and multi-client teams
Share skills and prompts across the agency without pasting client secrets into chat.
- Any team with scattered AI tools
If prompts, skills and MCP connections live in five places, a private catalogue gives you one set that you own.
USE CASE
Platform teams
- Approved skills and MCP servers
Publish the skills and MCP servers engineering may use, so installs stop living in personal configs and Slack threads.
- Beside your developer portal
Keep Backstage, Port or your IDP for software services. Joyst catalogues your AI tools and content next to it.
- Permissions and audit
View, use and manage rights, and an audit trail, for skills, prompts, MCP servers, secrets and agents.
- Govern across tools
One private catalogue across Claude, Cursor, agents and the MCP servers your platform already allows.
USE CASE
Agencies and multi-client teams
- Shared skills and prompts
Reuse agency playbooks across clients from one private library, without copying every prompt into chat.
- Client-safe secrets
Keep client keys in the secrets vault. Agents and packages refer to them by name, which is designed to keep credentials out of the model’s context.
- Multi-client separation
Folders and permissions keep client work separate, while the agency still shares common skills and prompts.
- Agents as packages
Package skills, prompts, MCP servers and secrets for each engagement, so delivery teams start from approved parts.
EXPLORE
Pick a path
- Platform teams guide
Approved skills, approved MCP servers and permissions for engineering. See below.
- Agencies guide
Shared libraries and client-safe secrets. See below.
- The product
Prompt management, skills registry, MCP catalogue, AI governance, secrets vault and agents.
- Pricing
Start free during the beta. See pricing for details on seats.
EXPLORE
Keep exploring.
- Platform teams
Govern skills and MCP servers beside your developer portal.
Open - Agencies and multi-client
Shared libraries with client-safe secrets.
Open - Prompt management
A team library, with versioning and sharing.
Open - Skills registry
Manage, version and move skills.
Open - MCP catalogue
Connect, document and approve servers.
Open - AI governance
Permissions and an audit trail across the catalogue.
Open - Secrets vault
Keys kept out of model context.
Open - Agents
Package skills, prompts, MCP servers and secrets.
Open - Pricing
Free for up to 20 users during the open beta.
Open - AI enablement for teams
Roll out approved AI with owners, permissions and an audit trail.
Open
Use cases FAQ
Teams that need a private catalogue for skills, prompts, MCP servers, secrets and agents across AI tools, especially platform teams and agencies.
No. The catalogue is private to your organisation.
No. It sits beside your developer portal and catalogues your AI tools and content.
Pick the use case that matches your team, or start with prompt management or the skills registry.
Start free, or pick your use case.
Create an organisation account and put skills, prompts, MCP servers, secrets and agents in one private catalogue.
- Private to your organisation
- Platform teams and agencies
- Not a marketplace or IDP