> ## Documentation Index
> Fetch the complete documentation index at: https://developer.usetyms.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Other clients

> Use Tyms MCP from Cursor and other remote MCP + OAuth clients.

Dedicated Client IDs exist for:

* **Claude** → `usetyms-mcp-claude` ([Claude.ai](/mcp/clients/claude-ai), [Desktop](/mcp/clients/claude-desktop), [Code](/mcp/clients/claude-code))
* **ChatGPT** → `usetyms-mcp-chatgpt` ([setup](/mcp/clients/chatgpt))
* **Perplexity** → `usetyms-mcp-perplexity` ([setup](/mcp/clients/perplexity))

For **any other** MCP-compatible client (for example **Cursor**), use the generic Client ID below — if the client supports **remote MCP** (Streamable HTTP) and **OAuth**. Client UI labels vary.

## Values to enter

| Field                         | Value                          |
| ----------------------------- | ------------------------------ |
| **Server URL (read-only)**    | `https://mcp.usetyms.com`      |
| **Server URL (read + write)** | `https://mcp.usetyms.com/full` |
| **Client ID** (when asked)    | `usetyms-mcp-client`           |
| **Auth**                      | OAuth                          |

## Typical flow

1. Add a remote / custom MCP server in your client.
2. Paste the Tyms URL for the access level you want.
3. If asked for a Client ID, enter `usetyms-mcp-client`.
4. Complete Tyms OAuth and approve a business.
5. Enable the server / tools for the session, then ask questions.

<Note>
  If a client only supports local stdio MCP servers (and not remote HTTPS + OAuth), it will not work with Tyms MCP as documented here. Tyms MCP is a **hosted remote** server — there is no local package to install.
</Note>

## If something looks wrong

* You only see list/get tools → you are on the read-only URL; switch to `/full` for write tools. See [FAQ](/mcp/faq).
* Auth fails on Client ID → confirm you used `usetyms-mcp-client` for unknown clients (or the platform-specific ID if you are on Claude, ChatGPT, or Perplexity).
* Wrong business data → reconnect and approve the correct business during OAuth.