ChatGPT MCP setup: connect Invoke Human

ChatGPT on the web does not read your Codex config. Add Invoke Human as a custom MCP plugin and sign in with OAuth.

Updated October 17, 2026

1. Open custom MCP plugins. In ChatGPT, go to Plugins, choose the plus button, then Add custom MCP server.
2. Paste the server URL. Enter a name and the server URL https://invokehumantool.com/mcp. Leave the tunnel option alone.
3. Choose OAuth. Pick OAuth, not no authentication. The server returns 401 until a bearer token is present.
4. Install and mention it. Create the plugin, install it, then mention it with @ in a conversation when you want a handoff.

This page is ChatGPT on the web. The desktop app shares its MCP list with Codex. If that is what you have open, use the Codex guide instead of creating a second config.

OpenAI documents the web path in Add a custom MCP server. Workspace admins can restrict custom MCP servers, including with Lockdown. If the plus button is missing, that restriction is the first thing to check, not the URL.

Add the plugin

1. Open ChatGPT plugins.
2. Choose the plus button, then Add custom MCP server.
3. Name it Invoke Human. A description is optional. Something dull and accurate works: “Ask the account owner. The answer comes back to this chat.”
4. Under Connection, paste the server URL. Do not pick Tunnel. Tunnel is for a server that is not on the public internet. This one is.

https://invokehumantool.com/mcp

5. Set authentication to OAuth. OpenAI lists OAuth, no authentication, and a mixed mode. No authentication fails here: the server returns 401 and protected-resource metadata until a bearer token is sent. The remote MCP guide is the trace of that exchange.
6. Leave client id and client secret empty. The authorization server’s metadata includes registration_endpoint and token_endpoint_auth_methods_supported of none (a public client, PKCE S256). It does not advertise Client ID Metadata Documents. OpenAI’s docs say static credentials win if you provide them, CIMD is used when the server advertises it, and DCR is used when configured. Empty fields are the DCR path.
7. Read the risk warning. A custom MCP server can act with the tools it exposes. Invoke Human’s tools ask you. They do not grant the model a new account on some other product, but you should still know which server you added.
8. Create the plugin, then install it in the workspace where you want it.

Use it in a chat

In the composer, type @ and choose the plugin you installed. OpenAI notes that custom MCP plugins do not need search and fetch tools. Any tool the server exposes can be called, and write actions ask you to confirm inside ChatGPT before they run.

That ChatGPT confirmation is not the handoff. It is ChatGPT checking that it may call the tool. The handoff is the tool call itself: a question, an approval, or a form that shows up in the Invoke Human app. Name the tool when the chat has a lot of apps installed.

• send_handoff sends a handoff to the signed-in person, or to other people.
• send_ui_handoff sends a structured form the person answers on a device or a signed link.
• send_html_handoff sends an HTML handoff the person answers by tapping or typing.
• validate_ui checks a UI document before it is sent.
• share_handoff invites more people to a handoff, or forwards it.
• delegate_handoff forwards a handoff to new recipients.
• get_handoff_status reads the type, title, and status of one handoff.
• get_handoff_result fetches the answer, or the current status if it is not finished.
• wait_for_handoff waits until the person finishes that handoff.

Parameter names come from the tool list the server returns after OAuth. You answer on iPhone, iPad, or Mac. The answer returns to the ChatGPT conversation, with attribution. TestFlight for iPhone and iPad is on the home page. What the inbox is for is on agent approvals. The short install is on Support.

When it fails

If create-plugin fails before any tool list appears, the usual causes are the URL (it must be the MCP endpoint, not the marketing site root) and an auth mode of “no authentication”. If the plugin exists but every call is unauthorized, finish the OAuth consent. The scope the server publishes is handoffs.

Same server, other clients: Codex, Claude, Cursor.