Prerequisites for using connected apps

Before you begin, make sure you have the following:

  • A deployed MCP server with a secure HTTPS endpoint

    Your MCP server must be publicly reachable over HTTPS using the Streamable HTTP transport (for example, https://api.yourdomain.com/v1/mcp).

    Refer to the Connected Apps Platform MCP server developer guide for implementation details.

  • Ensure your server can receive requests from Google

    If your server restricts external access by source IP, allowlist the following IP addresses:

    • 108.177.64.0/20
    • 142.250.88.0/22
    • 172.217.80.0/20
    • 192.178.20.0/22
    • 192.179.0.0/20
    • 74.125.232.0/24
    • 136.121.40.0/21

    Google's outbound IP ranges can change over time, so we recommend reading them from Google's published lists and refreshing your allowlist regularly:

  • Access to a registered developer account in Google Connected Console

    After you sign in, ensure you have one of the following Connected Apps permissions in Google Connected Console:

    • View Connected Apps
    • Create and manage Connected Apps

    The Connected Apps Terms of Service must also be accepted by an account owner or administrator. The first time your organization accesses connected apps in Google Connected Console, an account owner or administrator must sign in and accept the program agreement before invited team members can proceed.

    If you think you have access but can't create connected apps, ask your account owner or administrator to grant your user account the 'View connected apps' or 'Create and manage connected apps' permission on the Users and permissions page.

  • Ability to host a .well-known verification file on your MCP server domain

    To verify domain ownership, you must be able to serve a JSON challenge token file directly (with HTTP 200 OK and no redirects) at https://<your-domain>/.well-known/google-connected-apps.

  • Review the available connected app categories

    The category of your connected app is associated with specific capabilities that it should support to ensure a high-quality user experience. Once a category for a connected app has been selected, it cannot be changed. Learn more.

  • A deployed MCP server with a valid endpoint URL

    Refer to the Connected apps MCP server developer guide for more details.

  • Public-facing metadata and brand assets for your connected app

    • Connected app name: The display name for your connected app shown to users across Google products, and used when users mention your app with @.
    • Description: A concise, single-sentence summary (under 30 words) of what your connected app can do for users, such as "Track your recent purchases, check delivery status, and view your order history.".
    • Icon: A 512 px × 512 px app icon in JPEG or PNG format, with a maximum file size of 1 MB (1,024 KB).
    • Capabilities: At least 3 high-value tasks that your connected app can perform, such as "Search your order history" or "Check live delivery status", beyond the default capabilities defined by your app's category. These are shown to users to help them decide whether to connect. Don't include numbers at the beginning of your capabilities.
    • Example prompts: At least 3 sample queries that help users to understand what they can ask. Start at least 2 example prompts with the name of your connected app. Mention your app name naturally in at least 1 prompt (i.e. without starting with your app name). Don't include numbers at the beginning of your example prompts.
    • Terms of Service URL: A publicly accessible URL for your connected app's Terms of Service.
    • Privacy Policy URL: A publicly accessible URL for your connected app's Privacy Policy.
    • Website URL (optional): A website for your connected app.