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

# Endpoints

> Tyms MCP URLs for read-only and read + write access.

Tyms exposes two MCP endpoints so you can choose the right access level.

| Endpoint | Access | Use when |
| - | - | - |
| `https://mcp.usetyms.com` | **Read-only** | You want the assistant to look up data and run reports, but not change anything |
| `https://mcp.usetyms.com/full` | **Read + write** | You want the assistant to create, update, delete, and post transactions |

## URL notes

* Pasting `https://mcp.usetyms.com` is enough for read-only access (it routes to the MCP transport).
* You can also use `https://mcp.usetyms.com/mcp` for the same read-only server.
* Use `https://mcp.usetyms.com/full` only when you intentionally want write access.

<Warning>
  The **/full** endpoint can create, update, and delete real business data. Prefer read-only unless you need write access, and keep confirmation prompts enabled in your MCP client.
</Warning>

## Connection details

Use these values when configuring any MCP client:

| Field | Value |
| - | - |
| **Server URL (read-only)** | `https://mcp.usetyms.com` |
| **Server URL (read + write)** | `https://mcp.usetyms.com/full` |
| **Auth** | OAuth |
| **Client ID (Claude)** | `usetyms-mcp-claude` |
| **Client ID (ChatGPT)** | `usetyms-mcp-chatgpt` |
| **Client ID (Perplexity)** | `usetyms-mcp-perplexity` |
| **Client ID (other clients)** | `usetyms-mcp-client` |

<Important>
  When a client asks for a **Client ID**, use the ID for that platform. Full list: [Authentication](/mcp/authentication).
</Important>

## Read-only vs full at a glance

| Need | Use |
| - | - |
| Ask questions, analyze books, pull reports | `https://mcp.usetyms.com` |
| Bookkeep, create invoices/bills, post payments, manage inventory | `https://mcp.usetyms.com/full` |

Recommended pattern for teams:

1. Start everyone on **read-only**.
2. Enable **/full** only for trusted workflows.
3. Keep tool confirmation / human approval on for destructive actions (delete, payment posting, conversions).

See [Read-only vs full](/mcp/read-vs-full) for more guidance, and [Capabilities](/mcp/capabilities) for which tools appear on each endpoint.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.