Envoy in ChatGPT Work

Follow the complete installation guide for all hosts.

Skill and plugin release 0.4.15, for the current Envoy tool contract (support revision envoy@2026-10). Last updated 3 November 2026.

pay-with-envoy handles commerce; check-envoy-account handles explicit account questions. Each skill carries its own instructions and follows the next step in every Envoy tool reply; there is no separate guidance tool to load. Installing package files alone does not connect an account, select a default or authorize spending. This guide adds no payment, onboarding or recovery instructions.

Connecting lets this assistant read your Envoy account and ask to buy. It does not approve a purchase. You approve card-backed purchases in the Envoy app. For a gift card, follow the returned app approval/payment step or pay the returned link yourself. The app step alone does not identify the funding source. Follow the terms shown in that flow.

Envoy is not yet listed in the ChatGPT or Claude directories, and its ChatGPT submission is in preparation. Until then, add Envoy as a custom connector. Read Data and permissions, Privacy and Terms before connecting.

Installation matrix

Downloads

Verify downloaded archives against SHA256SUMS before installation. skills-release.json records the current filenames, URLs, hashes, skill names, endpoint and guide URL. Only the current supported archives are distributed.

Connection

Use this exact public Streamable HTTP MCP endpoint, with Envoy's existing OAuth flow:

https://api.envoy.money/mcp

Configure /mcp and check the catalog for the host you connected. The default profile receives all thirteen tools: get_account, list_transactions, list_purchases, start_purchase, get_purchase_status, answer_purchase_question, submit_answer (its deprecated name), report_checkout_result, report_checkout_step, cancel_purchase, list_gift_card_merchants, get_merchants (its deprecated name) and search_products. A connection Envoy identifies as Claude receives nine and omits report_checkout_result, report_checkout_step, submit_answer and get_merchants. A connection Envoy identifies as ChatGPT receives eight: it also omits list_gift_card_merchants, and buys only from Elixir's marketplace (search_products, then start_purchase with its product_id). A different catalog is stale; refresh it as described in upgrade and refresh. Complete OAuth through the host’s supported setup path. Packages contain no credentials, personal connection IDs or account state.

Open the authorization link generated by the host for this connection attempt. Complete sign-in and review the connection approval. Return to your agent and confirm that the connection is authenticated. Then call get_account with {} for a read-only check. If sign-in expires or fails, start a fresh sign-in through the host.

Do not paste OTPs, authorization codes, callback URLs containing codes, or access tokens into the conversation.

The tool catalog lists operations, not a promise that every merchant or payment service is available. Read services from get_account for account availability. Use get_merchants and search_products only for the discovery each tool supports. Follow the purchase reply for the available payment path.

When Envoy offers a gift-card payment link, the user pays that link. The agent never opens or pays it. The link task supplies the amount due, the gift-card value and the next action. Gift cards can also use an app approval or in-app payment; follow the returned task. The app step does not identify the funding source, and the app shows the actual payable before confirmation. Unused value stays on the gift card. This path does not release a one-time payment card. Its availability depends on the merchant, account and connection; it is not a way around a host restriction.

ChatGPT

What Envoy does in ChatGPT. Envoy checks out on the merchant's website after you approve the purchase in the Envoy app. ChatGPT never receives card details or checkout codes. Provide a delivery address when the purchase requires one. Envoy checks the merchant, amount and available services for each purchase. The same connection restrictions apply in ChatGPT Work.

On eligible web accounts, enable Settings → Security and login → Developer mode, then open Plugins → +, create a connection using the endpoint above and OAuth, review discovered tools and install the personal MCP plugin. Developer mode is documented for Plus, Pro, Business, Enterprise and Education; workspace policy still applies. Official quickstart, connect and test, authentication.

The separate envoy-payments-plugin-0.4.15.zip contains envoy-payments/plugin.json, README.md and both skills. It has no embedded MCP configuration or registered app ID: imported embedded-MCP bundles are Desktop only; app references require a real registered integration. Install through a desktop local marketplace or workspace distribution; on web and mobile, personal ZIP import is not a supported install path. MCP creation alone does not install the skills. Skills by surface, import limitations.

ChatGPT Work

For web Work, connect through developer mode above, switch Chat → Work, and start a fresh task. Distribute the skills through the workspace route below, then verify both skills and the connection in Work. Local files are not hosted installation evidence; Work access does not expand developer-mode eligibility. Work quickstart, hosted/local distinction.

For desktop Work, install the skill bundle through the local marketplace below and verify its independently configured Envoy connection.

OpenAI local marketplace

1. Choose a dedicated local marketplace/repository root. Save marketplace.json as .agents/plugins/marketplace.json inside it.
2. Extract envoy-payments-plugin-0.4.15.zip into that root's plugins/ directory. The resulting manifest is plugins/envoy-payments/plugin.json; the catalog's ./plugins/envoy-payments path resolves from the marketplace root.
3. Open the root in desktop Work, restart the app, select the local source in Plugins Directory, and install Envoy Payments. Start a fresh task and verify both skills and the separately configured connection.

The marketplace is local/private and distinct from the public directory. Do not overwrite an existing personal catalog or edit an installed cache by hand. Official marketplace installation.

OpenAI workspace distribution

An authorized workspace administrator can choose either documented route:

• After local installation, open Plugins → Personal → Envoy Payments → … → Publish and choose workspace roles. This publishes within the workspace only; administrators can disable plugin sharing. Workspace publication.
• Put the marketplace tree above in a public/private GitHub repository. Open Admin → Plugins → Add → Import marketplace, enter the repository URL and optional path/ref, authorize GitHub, then review the import and role policies. GitHub import.

After role access is granted, open Plugins → your workspace tab → Envoy Payments → + to install if needed. Start a fresh ChatGPT/Work task and verify both skills and the separately connected MCP. Member installation. On personal web, use workspace distribution or the desktop local marketplace; there is no personal web skill-install path.

Upgrade and refresh

Retain the connection owner, authentication and any installation key in designated storage, plus purchase/request references and saved default. None belongs in the package.

• Verify the archive, then replace the plugin folder, do not overlay it; stale manifests/instructions must not survive. Refresh/reinstall through host controls and start a fresh task. Keep one copy of each supported skill.
• For Claude organization uploads, a ZIP with the same plugin name replaces the prior version. For GitHub-managed distribution, use the host's sync/update controls. Source changes alone do not prove the installed copy refreshed. Claude updates, OpenAI imports and sync.
• Package refresh is not tool-schema refresh. Use connector discovery/refresh controls, then inspect a fresh task's catalog for the tools expected on that host under Connection. ChatGPT developer-mode connections provide Refresh. Reconnect only for required authentication/owner/key recovery, revoked access, or an endpoint change the host cannot edit. Upgrading alone requires no reconnect. Claude connector edits require removal/re-addition. ChatGPT refresh, Claude edits.

Do not delete credentials, browser profiles, cookies, IndexedDB keys or connection records as package cleanup. Preserve unresolved purchases across updates and follow the current service recovery action; an upgrade does not start a replacement purchase.

Removal

OpenAI documents that a separately connected integration can remain after plugin uninstall. Organization-required plugins may need administrator removal. Plugin removal. Never turn removal into a new payment or authentication workflow.

For a local marketplace, uninstall in the host, remove only the Envoy entry from .agents/plugins/marketplace.json, then delete plugins/envoy-payments/. Keep unrelated entries and all separate connection/task storage. Removing a source folder alone does not uninstall a host-managed copy.

Verify your installation

On each host you use — Grok, Claude, ChatGPT and ChatGPT Work — confirm, in a fresh task: the installed version, the host's expected catalog (thirteen tools for the default profile; nine when Envoy identifies the connection as Claude; eight for ChatGPT), that the skill is selected (explicitly invoking a skill is not the same as the host selecting it on its own), that your connected account carries over, and that a saved default is recalled.