docs: mcp connectors images

sources/platform/account/settings/index.md

@@ -48,6 +48,8 @@ The **API & Integrations** tab provides essential tools for accessing the Apify
 
 The **MCP connectors** section lets you authorize third-party MCP servers (such as Notion, Slack, GitHub, or Supabase) once and reuse those connections across any Actor that accepts them. For an overview of the feature, see [MCP connectors](/integrations/mcp-connectors).
 
+![MCP connectors section in account settings, listing authorized connectors with edit and delete controls](../images/mcp-connectors-list.webp)
+
 #### Create a connector
 
 1. Open **Settings > API & Integrations > MCP connectors** and select **Add connector**.
@@ -63,9 +65,11 @@ The **MCP connectors** section lets you authorize third-party MCP servers (such
 
 1. Choose an authentication method:
 
-    - _API key or bearer token_ - the MCP server uses a static API key or personal access token. Enter the key. Apify verifies it by connecting to the MCP server.
+    - _API key_ - the MCP server uses a static API key, bearer token, or personal access token. Enter the key. Apify verifies it by connecting to the MCP server.
     - _OAuth_ - the server supports OAuth and Apify can either register an OAuth client automatically (Dynamic Client Registration) or use an Apify-managed OAuth client. A consent screen opens in a popup. Grant access and close the popup.
-    - _Own OAuth client_ - the server supports OAuth but you need to register your own OAuth app with the provider (see below). Enter your client ID, client secret, authorization URL, and token URL, then complete the OAuth consent flow.
+    - _Your own OAuth client_ - the server supports OAuth but you need to register your own OAuth app with the provider (see [Set up your own OAuth client](#set-up-your-own-oauth-client)). Enter your client ID, client secret, authorization URL, and token URL, then complete the OAuth consent flow.
+
+    ![Add new MCP connector dialog with the MCP server URL verified and OAuth selected as the authentication method](../images/mcp-connectors-add-connector.webp)
 
 1. Review the discovered tools. Once authorized, the platform connects to the MCP server and discovers the tools it exposes. You can see them by expanding the connector card and restrict which ones the connector permits.
 
@@ -82,7 +86,7 @@ For providers without Apify-managed OAuth client setup (GitHub, Slack, Google, M
     ```
 
 1. Copy the client ID and client secret.
-1. In the connector creation modal, select **Own OAuth client** and provide:
+1. In the connector creation modal, select **Your own OAuth client** and provide:
     - Client ID
     - Client secret
     - Authorization URL (for example, `https://github.com/login/oauth/authorize`)

sources/platform/integrations/ai/mcp-connectors/index.md

@@ -44,7 +44,9 @@ MCP connectors are designed so that the Actor never holds your credentials, and
 - You control which connectors an Actor can access. An Actor can only use connectors you explicitly provide in the input. It cannot reach your other connectors.
 - Actors are held to what they declare. The proxy enforces that an Actor can only call tools it explicitly declared in its input schema. It cannot use your connector to call anything beyond that, regardless of what the connector supports.
 - Access ends when the run ends. The proxy session expires as soon as the Actor run finishes.
-- You control which tools a connector permits. The restriction applies to every Actor using the connector, on top of each Actor's own declared tool constraints.
+- You control which tools a connector permits. When you edit the connector in [Account settings](/account/settings#mcp-connectors), you can restrict which of its tools are allowed. The restriction applies to every Actor using the connector, on top of each Actor's own declared tool constraints.
+
+![Edit connector dialog with the Allowed tools list restricting a Notion connector to two selected tools](./images/mcp-connectors-allowed-tools.webp)
 
 For the developer-side controls and tool-permission model, see [Build Actors with MCP connectors](/integrations/mcp-connectors/use-in-actors#tool-permissions).
 
@@ -54,19 +56,21 @@ When you create a connector, the platform inspects the MCP server URL you provid
 
 | Method | When to use |
 | --- | --- |
-| API key or bearer token | The MCP server uses a static API key or personal access token (PAT). |
+| API key | The MCP server uses a static API key, bearer token, or personal access token (PAT). |
 | OAuth | The server supports OAuth and either (a) supports Dynamic Client Registration (DCR), so Apify registers an OAuth client automatically, or (b) Apify provides a managed OAuth client for that service. |
-| Own OAuth client | The server uses OAuth but neither DCR nor an Apify-managed client is available. You register your own OAuth app with the provider and supply the credentials to Apify. |
+| Your own OAuth client | The server uses OAuth but neither DCR nor an Apify-managed client is available. You register your own OAuth app with the provider and supply the credentials to Apify. |
 
-Apify provides automatic OAuth client setup for Notion and Supabase. For GitHub, Slack, Google, Microsoft Entra, and other providers, register your own OAuth app and use the Own OAuth Client flow.
+Apify provides automatic OAuth client setup for Notion and Supabase. For GitHub, Slack, Google, Microsoft Entra, and other providers, register your own OAuth app and use the **Your own OAuth client** flow.
 
 Tools are discovered when you first authorize a connector. To pick up new tools added to the upstream server, re-authorize the connector.
 
 Create and manage your connectors in [Settings > API & Integrations > MCP connectors](/account/settings#mcp-connectors).
 
 ## Run an Actor with a connector
 
-When you run an Actor that accepts MCP connectors, the input form shows a connector picker filtered to those compatible with the Actor's requirements. Pick one of your authorized connectors, or create a new one inline. To set connectors up in advance, see [Account settings - MCP connectors](/account/settings#mcp-connectors).
+When you run an Actor that accepts MCP connectors, the input form shows a connector picker filtered to those compatible with the Actor's requirements. The picker's label comes from the Actor's [input schema](/integrations/mcp-connectors/use-in-actors#declare-connectors-in-the-input-schema) - for example, as an **External data sources** field. Pick one of your authorized connectors, or create a new one inline. To set connectors up in advance, see [Account settings - MCP connectors](/account/settings#mcp-connectors).
+
+![Connector picker in an Actor input form, open and listing the user's authorized Notion and Sentry connectors](./images/mcp-connectors-input-picker.webp)
 
 ## Use cases