Add Tracy at Qode to Gemini CLI

Gemini CLI 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 inside the CLI.

Server address

The commands below use this address. Gemini CLI 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:

gemini mcp add --transport http tracy-at-qode https://tracyinterview.ai/mcp

This saves the server in your project's .gemini/settings.json. Add --scope user to save it in ~/.gemini/settings.json instead, so it is there in every project.

Or edit the settings file

If you would rather write the entry yourself, add this to mcpServers in the same file. Keep the other settings that are already there.

{
  "mcpServers": {
    "tracy-at-qode": {
      "httpUrl": "https://tracyinterview.ai/mcp"
    }
  }
}

The key is httpUrl because Tracy at Qode speaks streamable HTTP, not the older SSE.

Sign in and approve

Start Gemini CLI and run:
```
/mcp auth tracy-at-qode
```
Your browser opens on Tracy at Qode. Sign in and approve access. The CLI keeps the sign-in, so you do this once.

Sign-in needs a browser on the same computer as the CLI, so it will not work over SSH or inside a container without one. 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 Gemini CLI 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 Gemini CLI session, run /mcp. tracy-at-qode is listed with its tools, and its status should read CONNECTED.
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. Added without --scope user, the server is saved for one project only, so start Gemini CLI from that project's folder. Run gemini mcp list to see the servers the CLI knows about, with their status. 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 /mcp auth tracy-at-qode again. Sign-in needs a browser on the same computer as the CLI, so over SSH or inside a container without one it cannot finish. Run /mcp auth on its own to list the servers that need signing in. If no new app shows under Connected AI apps in your account afterwards, the sign-in was not finished.
/mcp shows tracy-at-qode as DISCONNECTED. Google's docs read DISCONNECTED as not connected or with errors. Check that the address in the settings entry is the one at the top of this page, then start Gemini CLI with --debug to see the errors, which the CLI keeps quiet by default.
Access was removed. If you revoked the app under Connected AI apps, it stopped at once. Sign in again with /mcp auth tracy-at-qode, or remove the server with the command under Remove access and add it again.

Still stuck? Write to support.

Remove access

To take the server out of Gemini CLI, run gemini mcp remove tracy-at-qode, adding --scope user if you added it that way. 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 settings file

If you would rather write the entry yourself, add this to mcpServers in the same file. Keep the other settings that are already there.

{ "mcpServers": { "tracy-at-qode": { "httpUrl": "https://tracyinterview.ai/mcp" } } }

The key is httpUrl because Tracy at Qode speaks streamable HTTP, not the older SSE.

Start Gemini CLI and run:

/mcp auth tracy-at-qode

Your browser opens on Tracy at Qode. Sign in and approve access. The CLI keeps the sign-in, so you do this once.

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 Gemini CLI session, run /mcp. tracy-at-qode is listed with its tools, and its status should read CONNECTED.

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. Added without --scope user, the server is saved for one project only, so start Gemini CLI from that project's folder. Run gemini mcp list to see the servers the CLI knows about, with their status. 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 /mcp auth tracy-at-qode again. Sign-in needs a browser on the same computer as the CLI, so over SSH or inside a container without one it cannot finish. Run /mcp auth on its own to list the servers that need signing in. If no new app shows under Connected AI apps in your account afterwards, the sign-in was not finished.

/mcp shows tracy-at-qode as DISCONNECTED. Google's docs read DISCONNECTED as not connected or with errors. Check that the address in the settings entry is the one at the top of this page, then start Gemini CLI with --debug to see the errors, which the CLI keeps quiet by default.

Access was removed. If you revoked the app under Connected AI apps, it stopped at once. Sign in again with /mcp auth tracy-at-qode, or remove the server with the command under Remove access and add it again.