Connect company SMS to a ChatGPT workflow
Connect the receiving tool where your ChatGPT task runs. The hosted OAuth route is awaiting account verification; terminal-backed tasks can use the CLI today.
Prepare the hosted OAuth connection
Phonekit implements remote MCP with OAuth, explicit workspace and line selection, and prompt message reads. The deployed connection still needs to be exercised in ChatGPT before we can call this route verified. Until then, use the terminal route below for a task you need to complete.
For a reachable Phonekit deployment, follow OpenAI’s connection instructions:
- Open ChatGPT Settings → Security and login and enable Developer mode, if your account and workspace allow it.
- Open Plugins, select the plus button, and name the connection Phonekit.
- Use the public endpoint
https://www.phonekit.io/api/mcpunder Connection. - Create the connection and review the discovered tools. Add it from the tools menu in a new conversation.
Authenticate through Phonekit when prompted. Select the workspace, readable lines and actions needed for this task. Phonekit supports dynamic OAuth client registration; choose that route if ChatGPT offers a client-registration choice. A Phonekit API key is not an OAuth client secret. See OpenAI’s authentication contract.
Verify the connection before assigning work
Confirm the intended number is readable and an unselected number is unavailable. Mark before requesting SMS in your application, retrieve a fresh receipt, handle an empty immediate read, and complete the application’s verification. Then revoke the connection and confirm further reads fail.
MCP reads return promptly. ChatGPT decides when to read again and when the task’s deadline has expired. Keep the receipt and code out of the completion report.
Use a terminal-backed Work or Codex task
Follow the Codex guide in the environment that will run the task. Install the skill, approve the CLI connection, and confirm it can list the assigned number. The receiving command must run in that environment.
In the connected coding environment, use Phonekit to add the receiving step to our staging sign-in test. Inspect the app and selectors, mark the assigned QA number before sending, receive the fresh code with the JS/TS SDK within 120 seconds, and assert the authenticated page. Run the test and return the change plus its outcome, without codes or tokens.
Install the SDK in the test project with npm install @phonekit/sdk.
Give a dot an ongoing SMS responsibility
Dots can connect apps and a computer; these connections are configured separately. If the task uses your computer, keep it online with the ChatGPT app open. Follow the Dots setup guide.
Confirm the exact receiving route in a dot’s own task. A working Codex login or ChatGPT connection alone does not prove the dot can call it. Record the company account, number assignment, permitted action and human owner using the agent task contract.
Help us keep the staging phone sign-in check working using the connected coding environment and its assigned Phonekit number. Start with one run: mark before send, receive within 120 seconds, finish sign-in, and confirm the authenticated state. Report the outcome or the setup stage that needs a decision. Keep codes out of reports. After this reviewed run, help me choose the schedule and when to notify me.
The dot’s host owns recurrence, memory and notifications. Phonekit supplies the receiving operations. An authorized teammate can inspect the same inbox when the task needs human attention.
Advanced: connect a private development server
When the MCP process cannot have a public endpoint, use OpenAI’s Secure MCP Tunnel. Configure the tunnel and its eligible workspace, then select Tunnel in the developer connection’s Connection settings. The MCP guide describes the private SDK-backed bridge. Verify this route in its actual host before relying on it.
Marketplace distribution is separate
Phonekit has no published ChatGPT plugin listing yet. A tested developer connection does not establish directory availability. Public installation requires a separately reviewed plugin and publication through OpenAI’s plugin directory process.
Questions you may have
Where should I enter a Phonekit API key?
For the terminal route, use the CLI browser approval flow. A private bridge holds a selected-number key in its process environment. The hosted OAuth route uses Phonekit sign-in and consent; it does not need a key pasted into chat.
Does installing a skill give ChatGPT message tools?
A skill provides instructions. The task also needs an executable CLI in its connected environment or an authenticated MCP connection. Check the receiving route before assigning the verification step.
What remains to verify for hosted chat?
The public deployment and an actual ChatGPT account run must pass the connection checks above. Dots needs its own task run. Marketplace publication is a separate distribution step.