> ## 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.

# Security & privacy

> How Tyms MCP keeps access scoped to your business and what you should do to stay safe.

## How access is scoped

* OAuth connects a **specific Tyms business**; the assistant only sees that business’s data.
* Your Tyms credentials are **not** shared with Claude, ChatGPT, or Perplexity as raw API keys. The client receives a bridge token; Tyms keeps upstream business tokens server-side.

## Practical guidelines

* Use **[read-only](/mcp/endpoints)** unless write access is required.
* Review tool calls before approving writes in your MCP client.
* Revoke access from your Tyms / integration settings if a client should no longer be connected.
* Do **not** paste API secrets into chat; MCP OAuth is the supported path.

<Warning>
  On `https://mcp.usetyms.com/full`, approved tool calls can create, update, and delete real records — including payments and conversions. Keep confirmation prompts enabled.
</Warning>

## Client ID

When asked for a Client ID, use the one for your platform:

| Platform      | Client ID                |
| ------------- | ------------------------ |
| Claude        | `usetyms-mcp-claude`     |
| ChatGPT       | `usetyms-mcp-chatgpt`    |
| Perplexity    | `usetyms-mcp-perplexity` |
| Other clients | `usetyms-mcp-client`     |

See [Authentication](/mcp/authentication).