Skip to content
Turbo Notify

Turbo Notify in Codex

In Codex, the turbo-notify plugin brings the MCP server and the virtual attendant skill. Codex is one of the two agents where the attendant answers on its own.

What you need

Section titled “What you need”
  • A Turbo Notify account with a connected number (quickstart).
  • Codex installed and signed in.
  • Python 3.9 or newer.

Connect

Section titled “Connect”
codex plugin marketplace add turbo-notify/agent-skills --ref v1
codex plugin add turbo-notify@turbo-notify

The plugin already declares the MCP server. --ref v1 keeps you on 1.x: a change that breaks compatibility never arrives by itself.

Sign in

Section titled “Sign in”

  • With your account: check the server with codex mcp list and sign in with the command below. Codex opens a page that names Codex and says you return to your own computer (127.0.0.1): that is expected, because Codex receives the answer on a local port. Approve access for the organization you want.

    codex mcp login turbo-notify

  • With an API key: this is the route for an attendant that runs on its own. Create the key with the AI agent (MCP) template in API Keys (opens in a new tab) and keep it in the TURBO_NOTIFY_API_KEY variable of the terminal where the runner will run. Treat the key like a password.

Scopes and keys are in MCP server.

Test

Section titled “Test”

Run codex mcp list: turbo-notify should appear. Then ask Codex: “List my WhatsApp numbers on Turbo Notify.” It calls list_numbers, which only reads. Nothing is sent.

For the skill, ask: “Set up the Turbo Notify virtual attendant.”

Update

Section titled “Update”

Codex does not update plugins by itself.

codex plugin marketplace upgrade
codex plugin add turbo-notify@turbo-notify

The skill checks its own version and messages the administrators with these two commands when a newer one exists.

Limits

Section titled “Limits”
  • The attendant’s runner needs the computer on and online, with Codex signed in on it.
  • The tools follow the API limits: 600 requests per minute per key or sign-in, plus the plan’s quota and sending pace. See MCP server limits and Limits.
  • A message that arrives while the runner is stopped is read when it returns, if it is still within the plan’s retention.

What is not verified

Section titled “What is not verified”
  • Using the MCP server in Codex without the plugin. This page covers the plugin only.