Connect your AI tool #

View this page as Markdown

Turn Zero Track (tzTrack) connects to your AI tool as an MCP server at https://tztrack.ai/mcp. This page adds it to Claude or ChatGPT, to Claude Code or Codex, or to any other AI tool that connects to an MCP server over HTTP with OAuth sign-in.

Every tool raises, finds, and closes issues the same way. Two features use files on your computer: the setting file and the local cache. Only a tool that runs commands, such as Claude Code or Codex, can use them. In Claude and ChatGPT, your AI reads the space live and passes it in its calls.

What you need #

• Claude (the desktop app or claude.ai), ChatGPT, Claude Code, Codex, or another AI tool that connects to an MCP server over HTTP with OAuth sign-in.
• A web browser for signing in.
• Your Turn Zero account.

Your Setup Steps #

1. Claude #

Add tzTrack as a custom connector, where your plan or organization allows custom connectors. The desktop app and claude.ai share one list of connectors, so adding it in one adds it to both.

1. Open Settings, then Connectors. On claude.ai the list is under Customize, then Connectors. On a Team or Enterprise plan, an owner adds it under Organization settings, then Connectors, and each member chooses Connect beside it.
2. Choose Add custom connector.
3. Enter tztrack as the name and https://tztrack.ai/mcp as the URL, then choose Continue.
4. Keep Sign in now under Authentication. Under OAuth client, choose Register automatically. Leave Request headers empty.
5. Choose Add. Your browser opens the Turn Zero sign-in page. Sign in with your Turn Zero account, then return to the app.
6. In a chat, open the + menu, choose Connectors, and turn tztrack on.

2. ChatGPT #

In ChatGPT's settings, with developer mode on, where your plan offers it, add a custom connector with the same address, https://tztrack.ai/mcp. ChatGPT opens the Turn Zero sign-in in your browser. Sign in with your Turn Zero account. Then turn the connector on in each chat where you want it.

3. Claude Code or Codex #

Using Claude Code or Codex? Each adds the server with one command in a terminal. In Claude Code, run this command:

claude mcp add --transport http tztrack https://tztrack.ai/mcp

Next, type /mcp in Claude Code, choose tztrack, and finish the sign-in with your Turn Zero account in the browser.

In Codex, run this command:

codex mcp add tztrack --url https://tztrack.ai/mcp

Codex then opens the browser for the sign-in. Where the browser does not open, run codex mcp login tztrack.

4. Another AI tool #

Other tools that take an MCP server by its address take the same one, https://tztrack.ai/mcp, usually as a custom connector. Your tool opens the Turn Zero sign-in in the browser. Sign in with your Turn Zero account. Your tool keeps the sign-in as it keeps its other MCP sign-ins.

5. Check the connection #

Ask your AI: "Find my open issues in tzTrack." Your AI calls find and lists the open issues of your space, or says the space holds none yet.

Where your account holds no space yet, your AI asks you whether to make one. Once you agree, it makes the space with create_issue_space. To have every session of a project use that space, follow Name your space in a setting file. That page needs a tool that writes files, such as Claude Code or Codex.

If you sign in with a Turn Zero account that does not hold tzTrack, the sign-in fails at once, refused invalid_grant. Sign in again with the account that holds tzTrack.

When your sign-in ends, or after a change on our side, your tool asks you to sign in again. Your space and its issues are unchanged.

To remove the connection in Claude or ChatGPT, remove tzTrack from the connectors in the app's settings. In Claude Code, run claude mcp remove tztrack. In Codex, run codex mcp logout tztrack and then codex mcp remove tztrack.

Before your AI starts #

This section is for your AI coding tool: what it checks and gathers before it begins. You don't need to do these steps yourself.

• Your person at a browser for the sign-in. In Claude Code or Codex, the tool adds the server itself; in a chat app, your person adds the connector. Your person always does the sign-in.
• The sign-in stays with the tool or app that holds it. The tool never copies it into a project, a file, or an issue.
• A call made before the sign-in completes is refused credential_required. Nothing was done; ask your person to sign in, then repeat the call. A call refused credential_refused after a working connection means the sign-in ended: ask your person to sign in again.
• Making a space is your person's choice. Where raise refuses because the account holds no space, ask first, then call create_issue_space.

Expected result #

In Claude or ChatGPT, once you turn the connector on in a chat, that chat can call tzTrack's tools, and the check in step 5 lists your open issues. In Claude Code, /mcp lists tztrack as connected, and its tools appear with names such as mcp__tztrack__find. In Codex, codex mcp list shows tztrack, and a new task can call its tools. A find answers the open issues of your space.

Refusals #

This table lists the refusals these steps most often meet; Refusals lists every refusal with its cause and remedy.

What your tool does #

• Works through the connector you add in Claude or ChatGPT. In Claude Code or Codex, it adds the server with the command in step 3, and asks you to finish the sign-in when the browser opens.
• Reads your open issues with find at the start of its work: urgent ones, ones waiting for you, and ones near their due date.
• Asks you before it makes a space with create_issue_space, and writes no file into your project during the connection.

Related #

• Quick start gives each tool's line on one page, and a script's steps.
• Name your space in a setting file makes every session of a project use the same space.
• What happens without asking says what your AI does in the space on its own and what it asks you first.
• The tools lists every tool the server serves.