Reconnecting to Valency

Did Valency stop working for you recently? You're in the right place. This is a known issue with a quick fix.

What happened

We recently upgraded how Valency signs you in. Connectors you set up before this change were configured the old way, and what you see depends on your platform:

• ChatGPT shows a screen titled "Add Valency again" when it tries to sign in. The old connector can't be revived; removing and re-adding is the only fix. Jump to the ChatGPT steps.
• Claude or a CLI asked you to sign in to Valency again out of the blue. That's expected, once. Complete the sign-in and you should be back, with no need to remove anything. Only if sign-in loops or keeps failing, use the steps below for your platform.
• Claude says "Authorization with Valency failed. You can check your credentials and permissions…" First check which email you signed in with. It may not be the one your Valency account is under. Sign in again with the right email, or check your account at app.valency.io (opens in new tab). If you're confident the email is right, remove and re-add the connector using the steps below. Details in Troubleshooting.

For a connector that's genuinely stuck, the fix is the same everywhere: remove the Valency connector completely, then add it back. A fresh connector registers the new way and just works: no ID to paste, no port to configure. During sign-in you'll see a Valency authorization screen that wasn't there before; approve it and you're done.

This is quick

Removing and re-adding takes about two minutes. You won't lose anything: your Valency account, history, and settings live on our side, not in the connector.

Find your platform

Jump to the steps for the app you use:

Claude.ai (browser)

Claude Desktop

Claude Code CLI

ChatGPT

Codex CLI

Let your agent do it

Using a CLI agent like Claude Code or Codex? You can also simply ask it to "remove the Valency connector" and let it run the removal for you. Then add it back by following the setup guide for your platform.

---

Claude.ai

Remove it:

1. Open your Claude connector settings (opens in new tab).
2. Find Valency in the list and click it.
3. Click Remove (the trash / delete option) and confirm.

Add it back: follow the Claude.ai setup guide from the top. It's a two-step, browser-only flow.

---

Claude Desktop

Remove it:

1. Open Claude Desktop → Settings → Connectors.
2. Find Valency, click it, and choose Remove / Delete. Confirm.
3. Restart Claude Desktop so the change takes effect.

Add it back: follow the Claude Desktop setup guide.

---

Claude Code

Remove it from your terminal:

claude mcp remove valency-mcp

Not sure what it's named? List your servers first with claude mcp list and use the matching name.

Add it back: follow the Claude Code setup guide. Setup now installs the Valency plugin, which brings the MCP connection and the research skills together, so you no longer add the server by hand. If your old add command included --callback-port, leave it off this time; it's no longer needed.

Note

Claude Code caches its sign-in per server. If re-adding under the same name still fails, run /mcp inside Claude Code, select the Valency server, and choose Clear authentication before signing in again.

---

ChatGPT

Remove it:

1. In ChatGPT, open Plugin Settings (opens in new tab).
2. Click the three dots next to the Valency plugin title, then Delete.

Don't see Plugins at all? Make sure Developer mode is on under Settings → Security and login (opens in new tab).

Add it back: follow the ChatGPT.com setup guide to create a fresh connector.

---

Codex CLI

Remove it from your terminal:

codex mcp remove valency-mcp

Not sure what it's named? List your servers first with codex mcp list and use the matching name.

Add it back: follow the Codex CLI setup guide. Setup now installs the Valency plugin, which brings the MCP connection and the research skills together, so you no longer add the server or type its URL by hand, and the old trailing-slash and callback-port advice no longer applies.

Note

Codex stores its sign-in per server. If signing in still fails, clear the old credentials first with codex mcp logout valency-mcp, then sign in again.

---

Gemini CLI (no longer supported)

Google retired the Gemini CLI, and Valency no longer supports it. There's nothing to reconnect to, but if you still have Valency installed there, here's how to clean it up.

1. Remove the connector:

   gemini extensions uninstall valency

   If you added Valency manually instead, open your settings file (~/.gemini/settings.json, or %USERPROFILE%\.gemini\settings.json on Windows) and delete the valency block under mcpServers.

2. Clear the cached sign-in. Open ~/.gemini/mcp-oauth-tokens.json (%USERPROFILE%\.gemini\mcp-oauth-tokens.json on Windows), a JSON array of sign-in records, and delete the one whose "serverName" is "valency", leaving the others in place.

   Caution

   This file holds the cached sign-in for every MCP server in the Gemini CLI, so remove only the valency record. Don't delete the whole file, or you'll sign yourself out of all of them.

Instead of adding it back: set Valency up in the Antigravity CLI, which is where Google moved Gemini CLI users.

---

Still not working?

If it still fails after a clean remove-and-re-add, it's probably something else. Check Troubleshooting or report an issue. Tell us which platform you're on and which step failed, and we'll help.