Skip to main content

Signing In from Your Editor

When your editor connects to the TestFlair MCP server, you sign in with your normal TestFlair account in your browser, the same way you sign in to the web app. There is no API key to create, copy or rotate, and nothing secret goes into your editor's configuration.

Beta feature

The TestFlair MCP server is a Beta feature and is still rolling out. It may not be available on your account yet. Contact your workspace admin or [email protected] if you'd like access.

How Sign-in Works​

The first time your editor connects, it discovers on its own that TestFlair needs you to sign in, and opens your browser:

  1. Add the server to your editor. See Connect Your Editor for the steps for Claude Code, Cursor, VS Code and Claude Desktop. Add it without any headers, Authorization or API-key entry.
  2. Your browser opens the TestFlair sign-in page. If you are already signed in to TestFlair in that browser, this step may complete on its own.
  3. The browser hands you back to your editor, and the TestFlair tools appear. Start by asking your assistant to list your workspaces.

There is no separate "allow access" screen. Signing in is the approval.

Staying Signed In​

After you sign in, your editor stays connected. Access renews automatically in the background while you work. You are asked to sign in again when your TestFlair session ends:

  • after a period of inactivity
  • at least once a working day, even if you keep working
  • when you sign out of TestFlair in your browser (your editor loses access within a few minutes)

Signing in again uses the same browser step. Nothing in your editor needs to change.

What Your Editor Can and Cannot Do​

Your passwordEntered only on the TestFlair sign-in page in your browser. Your editor never sees it.
What your editor storesA TestFlair access token that is valid for a few minutes and renewed automatically. It works only for the TestFlair MCP server.
Your permissionsExactly your own, the same as in the web app. The assistant can see and change only what you can. See Roles & Permissions.
Your workspacesEvery tool call names its workspace explicitly. There is no default workspace in an editor.
Several editorsEach editor signs in separately. If you use two editors, you sign in once in each.

Supported Editors​

The TestFlair MCP server works with editors that support remote MCP servers over HTTP with browser sign-in (OAuth), including Claude Code, Claude Desktop, Cursor and VS Code.

API keys and pasted tokens are not accepted

Editors that can only send a fixed API key or a hand-written Authorization header cannot connect. If you added TestFlair to an editor with a token in its configuration, remove the headers / Authorization entry and connect again.

Signing Out and Switching Accounts​

To…Do this
Disconnect one editorRemove the TestFlair server from that editor's MCP settings. This deletes the sign-in it stored.
End access in every editorSign out of TestFlair in your browser. Each editor asks you to sign in again the next time it needs access.
Switch to another accountSign out of TestFlair in your browser, then remove and re-add the server in your editor, and sign in with the other account.

Staying Safe​

  • Only add the server address shown in Connect Your Editor.
  • Only complete a TestFlair sign-in that you started from your own editor. If a TestFlair sign-in page opens when you didn't just connect an editor, close it.
  • Never paste a token from the web app into an editor configuration. It isn't accepted, and it isn't needed.

Troubleshooting​

My browser doesn't open when I connect

  • Some editors print the sign-in link instead of opening it. Copy it into your browser.
  • Check that the server address ends in /mcp and that the transport is http, not sse.

The sign-in page shows an error

  • Contact [email protected] with the error text. This is not something you can fix from your editor.

I signed in, but my editor still isn't connected

  • Your browser hands the result back to your editor on your own computer. Security software that blocks local connections can interrupt this step. Disconnect and connect again, and if it keeps happening, check with your IT team.

I get "Unauthorized", and I added a token or API key to my configuration

  • Tokens and API keys in the configuration are not accepted. Remove the headers / Authorization entry and connect again so your editor can sign you in.

I'm asked to sign in again, or tools stopped working

  • Your TestFlair session ended. Complete the browser sign-in again. See Staying Signed In.

My editor can't connect at all

  • Your editor may not support browser sign-in for MCP servers. Check that it supports remote MCP servers over HTTP with OAuth.

I signed in with the wrong account

I'm signed in but see no workspaces

  • Your account isn't a member of any workspace yet, or the MCP server isn't enabled for it. Ask your workspace admin.

Next Steps​