PRIVATE VS PUBLIC MCP REGISTRY
Private MCP registry vs public marketplace. Choose an allow-list.
Public MCP registries and marketplaces help people discover servers. Deciding what your organisation will allow is a separate task. Joyst is a private MCP registry for your organisation. Document, approve and govern the servers your team can use. It is an allow-list, not a storefront.

TWO KINDS OF REGISTRY
Public discovery vs private MCP registry allow-list
- Public registries
Public lists are built for browsing and discovery. They help with research, but they cannot record what your company allows.
- A private registry
A private MCP registry records which servers your organisation may use, who owns them and what has been approved.
- Connect, document, approve
Connect servers with care, document their tools and approve what agents and people may use. Governance and the audit trail sit alongside the catalogue.
PRIVATE MCP REGISTRY
What a private MCP registry means
- Your catalogue
Your organisation’s catalogue of connected servers, notes and approvals. Ownership and permissions stay with you.
- Notes beside each server
Notes live with each MCP server, so onboarding and reviews do not depend on old Slack threads or a forgotten wiki.
- Approve what the team can use
Approved servers are available to skills and agents. Servers that are not approved stay out of wider use.
- Govern and audit
Permissions and an audit trail, under AI governance, let security see who changed what.
PUBLIC LISTS STILL HELP
When public lists still help
- Use public lists for research
Public directories can help you find servers worth considering. They do not record what your organisation has approved.
- Bring approved choices into Joyst
Once a server is approved, Joyst adds it to your private MCP registry for the team to use.
- Feed agents from the private set
Skills and agents draw on the approved private catalogue, not on whatever someone bookmarked last week.
- No gateway today
Joyst does not offer an MCP gateway today. Start with the private catalogue to document, approve and govern the servers your organisation allows.
RELATED
Keep exploring.
- Document MCP tools
Add notes so people and agents understand each tool.
Open - Skills registry
Manage, version and move skills across AI tools.
Open - Agents
Package skills, prompts, MCP servers and secrets into reusable setups.
Open - Secrets vault
Keys kept out of model context.
Open - AI governance
Permissions and an audit trail across the private catalogue.
Open - Remote MCP server
Connect a remote server to Claude, Cursor and VS Code.
Open - MCP server security
The risks worth knowing, and the controls that help.
Open
Private vs public MCP registry FAQ
Public registries help people find servers. A private MCP registry records what your organisation has approved, so you can document, approve and govern the servers your team uses.
No. The catalogue is private to your organisation.
Yes, for research. Bring the servers you approve into Joyst, so your team has one record.
Approvals, permissions and the audit trail make the private catalogue easy to review. AI governance explains more.
No. Joyst catalogues your AI tools and content and works alongside a developer portal.
Build a private MCP catalogue
Create an organisation account and bring skills, prompts, MCP servers, secrets and agents into one private catalogue.
- Private to your organisation
- Draft, then publish
- Limited open beta