Add Tracy at Qode to Codex

Codex connects to Tracy at Qode as a remote MCP server, so you can set up an interview and read its results by asking for them in a session. You add the server once, then sign in from a terminal.

Server address

The commands below use this address. Codex files the server under tracy-at-qode, a name without spaces, because the name goes on a command line. It is the same Tracy at Qode server.

https://tracyinterview.ai/mcp

Add the server

In a terminal, run:

codex mcp add tracy-at-qode --url https://tracyinterview.ai/mcp

This saves the server in ~/.codex/config.toml, the file Codex reads in every project.

Or edit the config file

If you would rather write the entry yourself, add this table to ~/.codex/config.toml. Keep the other settings that are already there.

[mcp_servers.tracy-at-qode]
url = "https://tracyinterview.ai/mcp"

The only key it needs is url. The sign-in below gives Codex its access, so there is no token to paste in.

Sign in and approve

In a terminal, run:
```
codex mcp login tracy-at-qode
```
Codex takes you to Tracy at Qode. Sign in and approve access. Codex keeps the sign-in, so you do this once.

Tracy at Qode asks for one permission, named tracy, and acts only on your own account. What that covers is on the privacy page.

A first prompt to try

Once you are signed in, send this in a Codex session:

Set up a customer discovery interview for people who cancelled in the last month, then give me the public link.

Check it worked

Open your Tracy at Qode account and find Connected AI apps. The app is listed, with the time you connected it under Connected.
In a Codex session, run /mcp. tracy-at-qode is listed among the active MCP servers. Outside a session, codex mcp list lists the servers Codex has stored.
Send the first prompt above.
Tracy at Qode answers with a draft: the title, the questions and the result fields. Nothing is created until you approve the draft, so read it, ask for changes and say yes when it is right.

If it does not work

tracy-at-qode is not listed by /mcp. Run codex mcp list in a terminal to see the servers Codex has stored. If tracy-at-qode is there, start Codex again so it reads the list afresh. If you put the entry in a project's .codex/config.toml, Codex reads that file for trusted projects only. To start over, remove it with the command under Remove access and add it again.
The sign-in did not open or was not finished. Run codex mcp login tracy-at-qode again, on the computer where you have a browser. If no new app shows under Connected AI apps in your account afterwards, the sign-in was not finished. OpenAI's docs describe mcp_oauth_callback_port and mcp_oauth_callback_url in ~/.codex/config.toml for changing where the sign-in returns to, for example when you reach Codex remotely.
tracy-at-qode is listed but does not connect. Run codex mcp get tracy-at-qode and check that the address is the one at the top of this page. If it is not, remove the server with the command under Remove access and add it again.
Access was removed. If you revoked the app under Connected AI apps, it stopped at once. Clear the sign-in Codex stored with codex mcp logout tracy-at-qode, then sign in again with codex mcp login tracy-at-qode.

Still stuck? Write to support.

Remove access

To clear the sign-in Codex stored, run codex mcp logout tracy-at-qode. To take the server out of Codex, run codex mcp remove tracy-at-qode. To cut it off from Tracy at Qode as well, open your account, find Connected AI apps and revoke it. It stops at once, and you can connect it again later. Stuck? Write to support.

Or edit the config file

If you would rather write the entry yourself, add this table to ~/.codex/config.toml. Keep the other settings that are already there.

[mcp_servers.tracy-at-qode] url = "https://tracyinterview.ai/mcp"

The only key it needs is url. The sign-in below gives Codex its access, so there is no token to paste in.

Check it worked

Open your Tracy at Qode account and find Connected AI apps. The app is listed, with the time you connected it under Connected.

In a Codex session, run /mcp. tracy-at-qode is listed among the active MCP servers. Outside a session, codex mcp list lists the servers Codex has stored.

Send the first prompt above.

Tracy at Qode answers with a draft: the title, the questions and the result fields. Nothing is created until you approve the draft, so read it, ask for changes and say yes when it is right.

If it does not work

tracy-at-qode is not listed by /mcp. Run codex mcp list in a terminal to see the servers Codex has stored. If tracy-at-qode is there, start Codex again so it reads the list afresh. If you put the entry in a project's .codex/config.toml, Codex reads that file for trusted projects only. To start over, remove it with the command under Remove access and add it again.

The sign-in did not open or was not finished. Run codex mcp login tracy-at-qode again, on the computer where you have a browser. If no new app shows under Connected AI apps in your account afterwards, the sign-in was not finished. OpenAI's docs describe mcp_oauth_callback_port and mcp_oauth_callback_url in ~/.codex/config.toml for changing where the sign-in returns to, for example when you reach Codex remotely.

tracy-at-qode is listed but does not connect. Run codex mcp get tracy-at-qode and check that the address is the one at the top of this page. If it is not, remove the server with the command under Remove access and add it again.

Access was removed. If you revoked the app under Connected AI apps, it stopped at once. Clear the sign-in Codex stored with codex mcp logout tracy-at-qode, then sign in again with codex mcp login tracy-at-qode.

Remove access