Setup guides
One URL. The client signs in. Claude, ChatGPT, Cursor, Codex, and any other MCP client land in the same inbox.
The server is streamable HTTP at https://invokehumantool.com/mcp.
The tools are send_handoff, send_ui_handoff, send_html_handoff, validate_ui, share_handoff, delegate_handoff, get_handoff_status, get_handoff_result, and wait_for_handoff. 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.
The OAuth scope is handoffs. Each guide is the install for that client. Claude, ChatGPT, Cursor, Codex, and a generic remote client are also on the setup hub. The short version is on Support.
You answer on iPhone, iPad, or Mac. The iPhone and iPad app is in TestFlight for iOS 17 and later. Join from the home page. A signed web page opens one handoff. It is not a second inbox.
- Codex MCP setup: connect Invoke Human
Add Invoke Human to Codex as a streamable HTTP MCP server, sign in with OAuth, and give tool calls long enough for a person to answer.
- ChatGPT MCP setup: connect Invoke Human
Connect ChatGPT on the web to the Invoke Human MCP server as a custom plugin, with OAuth rather than an API key.
- Claude MCP setup: connect Invoke Human
Add Invoke Human as a Claude custom connector, or to Claude Code with claude mcp add. OAuth uses dynamic client registration.
- Cursor MCP setup: connect Invoke Human
Put the Invoke Human URL in Cursor mcp.json. OAuth runs in the client through dynamic client registration, with no API key in the file.
- Remote MCP server setup: connect Invoke Human
A remote MCP server is an HTTP endpoint any client can call. This walks the OAuth 2.1 discovery flow using the live Invoke Human metadata.