MCP servers and catalog

A catalog MCP connector and a server added by URL follow the same authorization path. The catalog saves you from entering an address Persyst already knows.

Available servicesCopy section link

The catalog includes Agorapulse, Sentry, Stripe, RevenueCat and Supabase, plus Notion for personal use. Availability depends on connectors allowed for your organization.

The account authorizing the service must have the necessary provider permissions. Available tools come from the connected server; they can evolve independently of Persyst.

Add from the catalogCopy section link

1. In Data sources → Add a source, choose the service.
2. Start the connection and authorize the appropriate provider account.
3. Return to Persyst and review discovered tools.
4. In Access management, choose tools and recipients.

Check the connected account before opening its tools. An administration service such as Supabase can expose operations beyond reading a database’s business data.

Add a server by URLCopy section link

Choose MCP server, enter a name and its remote HTTP address, then click Add and connect. Follow the offered authorization flow.

This form does not import local stdio configuration and has no field for arbitrary authentication headers or API keys. Check compatibility if your server requires that access mode.

Shared or personal connectionCopy section link

A shared server’s tools are subject to Persyst grants and their read/write classification. Tools without a read-only classification are not opened by default. Some write uses still require a personal account.

In My connectors, members can authorize a server with their own account where the provider is offered. See personal connections.

Verify toolsCopy section link

Ask your assistant to list its Persyst connectors and accessible tools for the service. Choose a simple read to verify authorization. After the server changes, refresh its tools in Persyst and review grants before opening new uses.