Set up Turn Zero for your AI tool #

View this page as Markdown

Connect the Turn Zero MCP server to the AI tool you already use. Choose the steps for your tool, sign in, and check the connection.

Connect your MCP server #

You need an AI tool that supports custom MCP servers like Claude or ChatGPT. A free Turn Zero account is created the first time you sign in.

Connect the turnzero HTTP MCP server at https://turnzero.ai/mcp?products=tztrack,tzmesh in your AI tool, then sign in. This connection includes tzTrack and tzMesh.

Detailed setup steps #

Choose the steps for your AI tool below.

Already connected to Turn Zero? #

If your signed-in turnzero connection already provides tzTrack tools, reuse it. Do not add a second connection with the same name. If tzTrack is turned off, follow Turn on another product later.

Claude Code CLI (including the desktop Code tab) #

Run this in a terminal to add Turn Zero for every project folder:

claude mcp add --transport http --scope user turnzero "https://turnzero.ai/mcp?products=tztrack,tzmesh"

After adding the server, start a new Claude Code session, type /mcp, choose turnzero, and complete the browser sign-in. These steps also apply to the Claude desktop app's Code tab. Use the Claude connector steps below for Claude Code on the web.

Claude chat or Claude Code on the web #

  1. Open Settings → Connectors (under Customize), then Add → Add custom connector.
  2. Enter turnzero as the name and https://turnzero.ai/mcp?products=tztrack,tzmesh as the URL, then choose Continue.
  3. Keep Sign in now, choose Register automatically under OAuth client, and leave Request headers empty.
  4. Choose Add, sign in with your Turn Zero account in the browser, and choose Allow.
  5. You may need to open a new chat to see the connector, or you may need to open + → Connectors and enable turnzero.

On a Team or Enterprise plan, an owner adds the connector under Organization settings → Connectors, then each member chooses Connect.

Claude's desktop chat and claude.ai share the connector. If it was added with the wrong authentication choice, remove it and add it again with the settings above.

ChatGPT or Codex desktop #

  1. Open Settings → Plugins → Add → Add MCP server.
  2. Enter turnzero as the name and select Streamable HTTP as the type.
  3. Enter https://turnzero.ai/mcp?products=tztrack,tzmesh as the server URL, add the server, and complete the browser sign-in when prompted.
  4. Start a new chat to load the connection.

Codex CLI or editor extension #

Run this in a terminal:

codex mcp add turnzero --url "https://turnzero.ai/mcp?products=tztrack,tzmesh"

Complete the browser sign-in while the command waits. If it finishes without signing you in, run codex mcp login turnzero. Start a new Codex conversation to load the tools.

ChatGPT or Codex on the web #

If your plan and workspace settings allow custom MCP servers:

  1. Open Settings → Plugins → Browse directory → Add (+) → Add custom MCP server.
  2. Enter turnzero as the name and https://turnzero.ai/mcp?products=tztrack,tzmesh as the server URL.
  3. Use OAuth sign-in. Check the server address in the warning, choose I understand and want to continue, and select Create as a plugin. Complete the browser sign-in and choose Allow when prompted.
  4. Install the resulting plugin. Start a new chat/session and ask to use tzTrack. You can also type @ and select turnzero explicitly.

Another AI tool #

Add https://turnzero.ai/mcp?products=tztrack,tzmesh as an HTTP MCP server with OAuth sign-in. Complete the browser sign-in, then load or enable its tools as your app requires.

Turn on another product later #

Ask your AI to use choose_products to enable the product. Include every product you want to keep enabled: the call replaces the connection's current selection. Keep using the same turnzero connection.

Then load the changed tool list:

  • On claude.ai, open the connector's ... menu and choose Refresh tools list.
  • In ChatGPT, use the connector's Refresh, then start a new chat.
  • In another AI tool, start a new session.

If switching products fails, use the fallback in Troubleshooting.

Tips for your AI #

  • Check the tools available to your session, including tools your host discovers on demand, before adding a connection. Reuse a working Turn Zero connection. A Codex desktop connection may not appear in codex mcp list.
  • Ask once before changing setup. In one message, ask the person to approve the specific changes to their connection and the browser sign-in, then wait. Keep any earlier approval of these specific changes; ask again only if a later step goes beyond it.
  • An instruction to work unattended does not approve adding an MCP server or changing its settings. Without approval, leave those changes pending and continue work that needs no approval. If your host blocks a settings change, report the block rather than bypassing it.
  • Configure the host that supplies your tools. In a chat or managed cloud workspace, give the person the connector steps and wait for sign-in. Running a local MCP install command in that workspace does not configure the host's connection.
  • Confirm access with a read-only call before reporting that setup succeeded. An enabled server does not prove sign-in is complete. A space_needed refusal, "You don't have an issue space yet", means sign-in works and no space exists yet: a project-setup step, not an authentication failure.
  • While a Codex sign-in command waits for the browser, keep it running and poll its session handle. Allow at least five minutes; do not start another sign-in because the command has produced no new output. If the browser cannot open, give the person the authorization link. Never ask them to paste tokens or callback URLs into chat.
  • For Claude Code sign-in, direct the person to /mcp in an interactive Claude Code session. Do not try to complete that interactive flow through a noninteractive command tool.

Once connected, follow Use tzTrack to choose the project's space and start using it. Follow the server's issue-management instructions as you work; Use one space across sessions covers project configuration.

Troubleshooting #

Check the connection #

Ask:

Check my tzTrack connection and list the spaces I can use.

Your AI lists the spaces you can use, your default first, or reports "You don't have an issue space yet". Either result confirms the connection; having no space means project setup is still needed.

Problem What to do
Your AI cannot find tzTrack's tools. Enable Turn Zero in the chat if required, then start a new conversation.
Sign-in is incomplete or expired. Finish the browser sign-in, or sign in again when authentication is required.
Sign-in or a product switch fails. Change the server URL in your existing turnzero connection to https://turnzero.ai/mcp, then try again. Do not add a second connection.
The tools changed after an update. Follow the refresh steps in Turn on another product later.
You have no issue space. Use the first-use prompt in Use tzTrack to have your AI set one up.

Refusals #

Refusal Cause Remedy
credential_required Sign-in has not completed. Finish browser sign-in through the app or CLI, then retry.
credential_refused The credential expired, was revoked, or access was withdrawn. Read the detail and sign in again with the appropriate account.
space_mismatch Your account cannot use the named space. Select a space you own or have been invited to.

Refusals covers other errors.

For a script or CI job, see the REST API setup steps.