Joyst

HOW-TO

How to connect and document an MCP server

Register the MCP servers your organisation uses, import their tools and annotate them in plain language. The result is an allow-list your team can trust.

dash.joyst.app
MCP catalogue in Joyst

STEPS

Connect and document an MCP server

  • Connect

    Register the MCP server with the authentication your organisation uses, either static or OAuth where supported.

  • Import tools

    Joyst lists the server’s tools and imports them with their schemas.

  • Add notes

    Add notes on when to use each tool, common pitfalls and examples, so the schemas become useful to people.

  • Approve

    Keep the approved list current. Re-sync on demand or on a schedule.

  • Use in agents

    Agent packages refer to catalogue endpoints. Joyst does not route live calls to third-party servers.

WHAT YOU GET

Private MCP catalogue

  • A full list

    Know which servers and tools your organisation has.

  • Notes that stay current

    Notes stay with the tools rather than in an out-of-date wiki.

  • Private to you

    The catalogue holds your organisation’s servers, not a public directory.

  • No gateway today

    Joyst catalogues and governs servers. Agents still connect to third-party MCP servers directly.

RELATED

Keep exploring.

  • Resources hub

    Practical guides to setting up and using Joyst.

    Open
  • MCP catalogue

    Connect, document and approve MCP servers.

    Open
  • Document MCP tools

    Add notes so people and agents understand each tool.

    Open
  • Private vs public MCP registry

    How a private approved list differs from a public marketplace.

    Open
  • Agents

    Package skills, prompts, MCP servers and secrets into reusable setups.

    Open
  • AI governance

    Permissions and an audit trail across the private catalogue.

    Open
  • Secrets vault

    Keys kept out of model context.

    Open
  • Private MCP catalogue or marketplace

    Why an approved list suits organisations better than a marketplace.

    Open
  • Remote MCP servers

    Connect a remote server to Claude, Cursor and VS Code.

    Open
  • MCP OAuth

    How MCP OAuth sign-in works, step by step.

    Open
  • Secure your MCP servers

    The risks worth knowing, and the controls that help.

    Open

MCP catalogue how-to FAQ

No. Joyst catalogues and governs servers, and agents connect to them directly. Controlled substitution for secrets is the one exception.

Public registries help people find servers. Joyst holds your organisation’s private approved list and its documentation.

Not today. Joyst catalogues and approves servers. Agents still connect to them directly.

Connect your first MCP server to the private 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
Start free beta