LoginStart Free
Back to guides
Billing & SettingsPublic self-service coming soon

Set up AI Connections

Restricted read rollout: setup for approved MyInvy Owners, separate permissions, and connection management. Public self-service access remains unavailable.

Owner

Access for approved organizations

Approved Owners can use ChatGPT and Claude Code to read MyInvy data. Your organization and connection must be enabled by MyInvy before following this guide. Public self-service access is coming soon. AI write operations are unavailable.

Last reviewed: .

Prerequisites

  • Approved Owners can use ChatGPT and Claude Code to read MyInvy data. Your organization and connection must be enabled by MyInvy. Public self-service access is coming soon.
  • You must be an active MyInvy Owner in the enabled organization, with access to the selected location and any required plan entitlement. Manager and Employee access is outside this rollout.
  • Use an eligible ChatGPT web account with custom-connection access, or a supported Claude Code installation signed in to your provider account. This guide covers Claude Code; Claude web is not qualified for this rollout. A separate API billing key is not required for these approved account connections.
  • Provider sign-in and MyInvy authorization are separate. Sign in directly in the provider or MyInvy page; do not paste passwords, sign-in codes, cookies, or tokens into a conversation.

Setup steps

  1. Confirm organization access and get the approved settings

    Open Settings > AI Connections as an Owner in the correct organization. Read-only access means that organization is enabled; Coming soon means it is not. Use the environment URL shown there and obtain the exact client ID, callback, and provider configuration from your MyInvy administrator. The production resource is https://manage.myinvy.com/mcp. The URL and guide do not themselves enable a connection.

  2. Choose ChatGPT on the web

    Use the permitted custom-app controls to create or select the approved MyInvy app with OAuth and the administrator-supplied registration. Complete MyInvy sign-in and review the read permissions. Start a normal Chat and explicitly attach the MyInvy app from the app picker before asking a question. Available controls depend on your account and workspace policy.

  3. Or choose Claude Code

    Sign in to a supported Claude Code installation and install the supplied remote HTTP MCP configuration, including its client ID, exact callback port, and approved scope list. Open /mcp, select the production MyInvy server, and authenticate in the browser. Use the administrator-supplied configuration together; substituting another connection’s callback can prevent sign-in.

  4. Sign in to MyInvy and review read permissions

    Check the MyInvy account and organization before approving access. Inventory read and Shopping List read are separate permissions. Approved identity and refresh permissions do not authorize additional business tools. Your current Owner role, location access, and plan entitlement still apply. Write permissions and preview/apply tools are unavailable.

  5. Check the production connection with a read

    Select the actual production MyInvy app from the ChatGPT conversation app picker, or check the correct server in Claude Code /mcp. With inventory read, ask “Which MyInvy locations can I access?” With only Shopping List read, ask for existing lists at a named location. Confirm the returned organization and context. The Settings page reports eligibility; it cannot verify a provider-held token.

  6. Manage permissions and disconnect

    Additional approved permissions require a new consent review. Follow Manage access in MyInvy Identity from Settings > AI Connections to Connected Apps to revoke the grant. Revocation blocks refresh immediately; previously issued access may remain valid until expiry, at most ten minutes. Removing the provider-side app alone does not revoke the MyInvy grant or erase data already shared.

Expected result

For an enabled organization and verified host connection, a read returns the correct MyInvy context with only the permissions approved. Public self-service setup and AI writes remain unavailable.

Official provider instructions

Provider controls and account requirements can change. These references explain provider setup; they do not confirm MyInvy availability.

Troubleshooting Tips

  • Coming soon or no approved registration: the organization or connection is not enabled. Developer mode, a provider account, or changing plans does not unlock access.
  • No custom-connection control in ChatGPT: check the provider requirements and workspace policy.
  • Provider sign-in expired: sign in to that provider again. MyInvy authorization is separate.
  • Sign-in or redirect fails: compare the exact server, client, callback, and scope settings with the supplied configuration. Do not substitute a development registration or callback port.
  • Permission denied: check the approved read scope, active Owner role, organization/location access, and applicable plan entitlement.