Add resources

Your agents reach a service's tools only after you add that service to the gateway as a resource. Once added, a resource's tools are ready to reference in a policy. Resources are the MCP servers that expose those tools to your agents through the gateway.

From the catalogCopy Anchor Link

The catalog includes pre-configured resources that work out of the box:

1. Navigate to Tools & Services in the dashboard
2. Click Add Resource to open the catalog
3. Find a resource by search or by browsing a category, then click it to open its page
4. If it supports more than one way to authenticate, pick Use SecureAuth's app (the quickest option) or Bring your own app (paste your own OAuth client ID and secret; the form shows a redirect URI to register with the provider, then click Add). See Credential modes for the differences.
5. Resources with a single one-click mode show one card. Click it to install. Resources that only support bring-your-own credentials skip the picker entirely and open the credentials form directly, with the same fields as step 4

Many connectors need one-time work in the provider's own admin console: approving the app, granting scopes. For those, the resource's detail page opens with an Admin setup required dialog right after you install; its Setup guide button links to the steps. The resource is already added, but users can't connect their accounts until you've finished them.

Available tools are discovered automatically. Users will be prompted to connect their accounts via OAuth when they first use the resource.

Custom resourcesCopy Anchor Link

You can add any MCP server not in the catalog:

1. Navigate to Tools & Services, click Add Resource, then + Custom server
2. Enter a display name, a slug, and the server URL for the MCP server. The slug is the short identifier used in policies (mcp.slug == "…")
3. Under Authentication, choose whose access the agent's tool calls run with (what each option asks for):
   • Users sign in themselves – each user signs in to the server once with their own account
   • OAuth app – the gateway signs in as its own app, and every user shares that access
   • API key – headers that carry the key, sent with every request and shared by every user
   • No authentication – the server needs no credentials
4. Add any headers the server needs, such as a tenant ID
5. Click Add

The gateway connects to the server and discovers available tools automatically.

Resource detailsCopy Anchor Link

Click any resource in the list to see its detail page:

• Available tools – every tool the MCP server exposes, with descriptions
• MCP Info – origin (catalog or custom) and its slug; custom servers also show the server URL and authentication option
• Settings – for OAuth resources, how users authorize and which OAuth clients the gateway uses, including rotating a bring-your-own client ID and secret (details)
• Recent activity – audit events related to this resource

Next stepsCopy Anchor Link

Continue to Create a policy to control which agents can use these tools.

See the full Resources guide for custom-resource details, and Credential modes for how the gateway authenticates to each catalog resource.