# Any MCP client

> Connect MCP Bond from an MCP client that doesn't have its own guide.

MCP Bond is a remote MCP server over streamable HTTP with OAuth. Any client that supports both can connect to it. The platform guides just spell out the same details in each client's own vocabulary.

## Connection details

| Setting | Value |
|---------|-------|
| Server URL | `https://mcp.valency.io/` |
| Transport | Streamable HTTP (not SSE, not stdio) |
| Authentication | OAuth 2.0 |
| Client registration | Dynamic, with no client ID or secret to paste |
| Client secret / bearer token | Not used. See [Direct API](https://docs.valency.io/guides/api.md) for token-based access. |

:::caution[Keep the trailing slash]
Some clients build their sign-in callback address from the server URL, so enter it exactly as `https://mcp.valency.io/`, including the trailing slash. This is what bit the Codex CLI.
:::

## Setup

1. Add the server in whatever way your client supports: a UI for adding a remote or custom MCP server, a CLI command, or its configuration file. Most JSON-configured clients want something close to this:

   ```json title="MCP configuration"
   {
     "mcpServers": {
       "valency": {
         "type": "http",
         "url": "https://mcp.valency.io/"
       }
     }
   }
   ```

   The exact key names vary by client. Some use `httpUrl` instead of `url`, and some nest servers under a different top-level key. Match your client's documented schema; only the URL and the HTTP transport are fixed.

2. Complete the sign-in flow. Bond supports dynamic client registration, so your client registers itself on first connect. You should never be asked for a client ID, client secret, bearer token, or a fixed callback URL.

   :::note
   A Valency account is created automatically the first time you sign in. The email you use does **not** have to match the email on your AI provider account.
   :::

3. Ask your client to call Valency's `list_sources` tool. A returned source list confirms it can use the connection. Seeing the server as connected or its tools listed does not confirm that a tool call works.

4. Ask [(more prompt ideas)](https://docs.valency.io/reference/examples.md):

   > Use Valency to search for papers about quantum computing

:::tip[You're connected]
You see Valency's source list. You can now ask your client to search or compare papers.
:::

## Troubleshooting

**Client asks for a client ID, secret, or token?**
It probably isn't using dynamic client registration for this server. Check whether it has a separate "remote" or "OAuth" server type. A client's default MCP entry is often stdio, which can't reach a hosted server.

**Sign-in opens but never completes?**
The callback address your client submitted may not be one Valency accepts. [Report the issue](https://docs.valency.io/help/reporting-issues.md) and include the client name, version, and the callback URL it used (leave off the query string, which carries the authorization code).

**Connects but no tools appear?**
Restart the client so it picks up the new server connection. If tools still don't appear, confirm the transport is streamable HTTP rather than SSE.

**Client doesn't support OAuth at all?**
Use the [Direct API](https://docs.valency.io/guides/api.md) with a bearer token instead.

---

## Need help?

If something isn't working, check [Troubleshooting](https://docs.valency.io/help/troubleshooting.md) for common fixes. See the [FAQ](https://docs.valency.io/help/faq.md) for general questions, or [report an issue](https://docs.valency.io/help/reporting-issues.md) if you're still stuck. Tell us which client you're using and we'll look at adding a guide for it.