PRIVATE MCP CATALOGUE
Private MCP catalogue. Manage and document the servers your team uses.
Without a catalogue, people connect whatever they find. Servers go undocumented, unowned and hard to audit. Joyst is a private MCP catalogue where you connect servers, document their tools and approve what your team and agents can use. It is your organisation’s approved list, not a public marketplace.
PRIVATE BY DESIGN
Private MCP catalogue vs public marketplace
- Two different jobs
Public directories and marketplaces help people find servers. Deciding what your organisation is allowed to connect is a separate job.
- Your approved list
Joyst is a private MCP catalogue. It records each server, adds your team’s notes, assigns an owner and tracks approval for what your team may use.
- Independent
Joyst is an independent private catalogue for your team. It is not the official Model Context Protocol registry or a public MCP marketplace.
MCP SERVER MANAGEMENT
MCP server management for organisations
- Every server has an owner
Connect the servers your team uses and give each one an owner, so onboarding no longer starts from a Slack screenshot.
- Know what is live
See which MCP servers are connected before an agent depends on them.
- One shared view
One private catalogue lists the servers your organisation allows, so platform and security teams work from the same information.
DOCUMENTATION
Document and annotate MCP tools
- Explain every tool
Undocumented tools slow onboarding. Add notes on what each tool does, so people and agents understand it the same way.
- Docs in the catalogue
Keep tool documentation in the private catalogue, rather than in a Slack channel or a one-off Notion page.
- One understanding
When agents and people read the same notes, approved tools are used consistently across skills and AI tools.
APPROVAL
Approve what the team can use
- You decide
Platform and security teams decide which servers are approved, without blocking useful AI work.
- No more one-off installs
Replace unmanaged one-off connections with a single organisation decision about what the team and agents may use.
- Permissions and audit
AI governance controls who can connect and who can approve, with the same permissions across the private catalogue.
NOT A GATEWAY
Joyst is not an MCP gateway.
- Only the tools you allow
A gateway would let you choose which tools from a remote MCP server an AI can call, instead of giving every tool to every agent.
- Start with the catalogue today
Joyst does not offer an MCP gateway. The private catalogue and approved list are available now.
- Talk to us
Joyst does not offer an MCP gateway.
BESIDE THE CATALOGUE
MCPs inside agents and skills
- Approved MCPs in packages
Skills and agents use approved MCP servers from the catalogue instead of one-off connections.
- Approved parts only
The skills registry and agents sit alongside the MCP catalogue, so every package uses approved parts.
- Credentials in the vault
Credentials for MCP tools belong in the secrets vault, never pasted into chat.
Connect, document, approve
Record the servers your team uses, document each tool for people and agents, then approve what your organisation may use.
Document MCP toolsChecklist
- Connect MCP servers and assign owners
- Document tools so people and agents understand them
- Approve what the team and agents may use
Inventory
Know what is connected
See which MCP servers are live before an agent depends on them.
Approval
Control first, then scale
Platform and security teams make one shared decision in the private catalogue.
Private catalogue
Your organisation decides.
Joyst records and approves the tools your team uses. Agents still connect to third-party MCP servers directly.
EXPLORE
Keep exploring.
- Skills registry
Pair MCP servers with the skills that use them.
Open - Agents
Package approved servers into reusable agent setups.
Open - Secrets vault
Store MCP tool credentials and refer to them by name.
Open - AI governance
Permissions and an audit trail for what the team can use.
Open - Private vs public MCP registry
How a private approved list differs from a public marketplace.
Open - Connect a remote MCP server
Connect a remote server to Claude, Cursor and VS Code.
Open - Connect MCP servers with OAuth
How MCP OAuth sign-in works, step by step.
Open - MCP security
The risks worth knowing, and the controls that help.
Open - AI inventory
Record the skills, prompts, MCP servers and agents your teams use.
Open
MCP catalogue FAQ
A private MCP catalogue is your organisation’s approved list of servers, an allow-list. You connect the servers your team uses, document their tools and approve what people and agents may use. It is not a public marketplace.
Marketplaces and public registries help people find servers. Joyst adds a private layer that records what your organisation is allowed to connect. It is not the official Model Context Protocol registry.
An organisation admin creates the connection. Joyst lists the tools when that connection is created. People with use and annotate access can add notes, including examples. A note is not a separate intended-use field. There is no approval queue.
An organisation admin creates the connection. There is no approval queue. Other access is set through user groups: view, use and annotate, or manage. Use and annotate is what you need to add notes on a tool.
No. Joyst keeps the connection and your notes. It does not carry live calls to those servers. Your tools still connect to the MCP themselves. Joyst can make its own outbound HTTP call and put a vault secret in that request. That is not a stand-in for your MCP.
Catalogue the MCP servers your organisation allows
Create an organisation account, then connect, document and approve the servers your team and agents may use.
- Your approved list
- Connect, document, approve
- Not a public marketplace