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 with a fixed sign-in ID that is no longer valid. Most AI assistants can't detect this on their own and won't re-register automatically, so the old connector keeps failing.

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, nothing to configure.

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

Gemini CLI

---

Claude.ai

Remove it:

1. Open your Claude connector settings.
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, including the /mcp authentication step.

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 Plugins (make sure Developer mode is on under Settings → Security and login).
2. Find the Valency app, open it, and Delete it.

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, including the codex mcp login step. Keep the trailing slash on the server URL — Codex builds its sign-in callback address from it, so …/mcp and …/mcp/ are not interchangeable.

Note

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

---

Gemini CLI

Remove it in two parts — the connector, then its cached sign-in.

1. Remove the connector. If you installed the extension:

   gemini extensions uninstall valency

   Not sure of the name? Run gemini extensions list to see what's installed and use the matching one. 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 stale Valency sign-in. Open ~/.gemini/mcp-oauth-tokens.json (%USERPROFILE%\.gemini\mcp-oauth-tokens.json on Windows) — it's a JSON array of sign-in records — and delete the one whose "serverName" is "valency", leaving the other entries 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.

   As a last resort — only if you'd rather not hand-edit JSON and don't mind re-authenticating your other MCP servers on next use — you can delete the whole file instead (rm -f ~/.gemini/mcp-oauth-tokens.json, or Remove-Item "$env:USERPROFILE\.gemini\mcp-oauth-tokens.json" -ErrorAction SilentlyContinue in PowerShell).

Add it back: follow the Gemini CLI setup guide.

---

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.