Claude

One Claude account connection makes Valency available on the web, in Claude Desktop, and in Claude Code. The direct MCP option below covers Claude Code sessions using an API key or proxy.

Claude setup steps

Connected before? Go straight to step 3 and check Valency in a Claude chat. The connector page may still say Connect to Claude even when the connection works.

1. Open Valency in Claude

   Open Valency's connector page in Claude ↗. If it says Connected, go to step 3.

2. Connect and sign in

   Click Connect to Claude. On Valency's consent screen, click Continue, then sign in with Google, GitHub, or Microsoft.

   Still says Connect to Claude? The directory label can lag or stay stale after sign-in. Go to step 3 and test Valency in a chat before trying to connect again.

3. Verify the connection

   Ask Claude:

   Use Valency to list the sources it can search. Copy

   If an open Claude Code session cannot see it, restart Claude Code and check /mcp. Claude Desktop may also need a new chat or a restart.

Using Claude Code with an API key, proxy, or another provider?

Paste this into Claude Code for a direct MCP connection. The assistant can install it; you will complete browser sign-in.

Using it in Claude Desktop

The same Claude account connection is available in Claude Desktop. If Claude cannot see Valency in an open conversation, start a new one. If it still cannot see the tools, quit Claude Desktop entirely and reopen it. You can see the connection under Customize → Connectors, but asking Claude to list Valency's sources is the working check.

Opening the connector directory link from Claude Desktop keeps you in the app. The sign-in itself happens in your browser, and Claude Desktop returns when it finishes.

Using it in Claude Code

Claude Code uses this connection when it is signed in to the same Claude account. Restart an open session so it loads the connector. If you were in the middle of a conversation, exit and run claude --continue from the same directory. Check /mcp, then ask Claude Code to call Valency's list_sources tool. The returned source list confirms tool access.

If Claude Code uses an API key, proxy, or another provider and cannot load the account connector, use the direct MCP connection prompt in the setup section. To configure that connection yourself instead, run claude mcp list and add valency only if it is absent:

claude mcp add --transport http --scope user valency https://mcp.valency.io/

Exit Claude Code with /exit or Ctrl+C twice. In the same terminal run claude mcp login valency and complete browser sign-in. On a machine without a browser, use claude mcp login --no-browser valency and paste the redirect URL when prompted. Run claude --continue from the same directory to resume and ask it to call list_sources. This installs the MCP connection only; no plugin or skills are needed.

Account and permissions

A Valency account is created automatically the first time you sign in. Use Google, GitHub, or Microsoft; your Valency email does not need to match your Claude email.

To avoid approving every read-only tool call, open Valency's Claude connector settings (opens in new tab) and set Read-only tools to Always allow.

Troubleshooting

The connector page still says Connect to Claude? Its status can lag after sign-in or on a return visit. Start a new Claude chat and ask it to use Valency to list the sources it can search. A returned source list confirms the connection; do not reconnect just because of the directory label.

Claude Code lists Valency but its tools are missing? Restart Claude Code or resume with claude --continue from the same directory. For a direct connection, run claude mcp get valency to check its status. If it needs authorization, exit and run claude mcp login valency in an interactive terminal, then resume.

Need to remove a direct connection? Run claude mcp remove valency --scope user. Manage an account connection in Claude's connector settings instead.

See Troubleshooting for other connection issues or report an issue.