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

# Other MCP Clients

> Connect any MCP-compatible AI tool to your Trilo workspace using the HTTP Streamable transport

Any AI tool that supports the [Model Context Protocol](https://modelcontextprotocol.io) can connect to Trilo. Here's what you need.

## Connection Details

| Setting            | Value                                                                                                               |
| ------------------ | ------------------------------------------------------------------------------------------------------------------- |
| **Endpoint**       | `https://api.trilo.chat/mcp`                                                                                        |
| **Transport**      | HTTP ([Streamable HTTP](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http)) |
| **Authentication** | `Authorization: Bearer trilo_pat_...`                                                                               |

## Setup

<Steps>
  <Step title="Create a Personal Access Token">
    In Trilo, go to **Profile Settings** > **API** > **Create Token**. Select the scopes you need (`mcp:read`, `mcp:write`) and copy the token.
  </Step>

  <Step title="Configure your client">
    Most MCP clients use a JSON config format. The standard config looks like:

    ```json theme={null}
    {
      "mcpServers": {
        "trilo": {
          "url": "https://api.trilo.chat/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN_HERE"
          }
        }
      }
    }
    ```

    Replace `YOUR_TOKEN_HERE` with the PAT you copied. Refer to your client's documentation for the exact config file location, format, and field names (some clients use `serverUrl` instead of `url`).
  </Step>

  <Step title="Verify the connection">
    Ask your AI tool:

    ```
    List my Trilo workspaces
    ```

    If it returns your workspace data, you're connected.
  </Step>
</Steps>

## Options

Append query parameters to the MCP URL for additional control:

| Parameter      | Description                      | Example                                           |
| -------------- | -------------------------------- | ------------------------------------------------- |
| `workspace_id` | Restrict to a specific workspace | `https://api.trilo.chat/mcp?workspace_id=abc-123` |
| `read_only`    | Force read-only mode             | `https://api.trilo.chat/mcp?read_only=true`       |

## Token Management

* **View tokens:** Profile Settings > API shows all your active tokens with last-used dates
* **Revoke a token:** Click the revoke button next to any token to immediately disable it
* **Multiple tokens:** Create separate tokens per client or machine for easy revocation

<Tip>
  Create separate tokens for each AI tool or machine. If one is compromised, you can revoke it without affecting your other tools.
</Tip>

## Troubleshooting

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    * Verify your token starts with `trilo_pat_` and is copied correctly
    * Check that the `Authorization` header uses the `Bearer` prefix
    * Confirm the token hasn't been revoked in **Profile Settings** > **API**
  </Accordion>

  <Accordion title="Token doesn't have MCP access">
    Your token was created without MCP scopes. Create a new token and select at least `mcp:read`.
  </Accordion>

  <Accordion title="Session expired (error -32002)">
    MCP sessions expire after 30 minutes of inactivity. Most clients reconnect automatically. If not, restart the MCP connection in your client.
  </Accordion>

  <Accordion title="Rate limited (429)">
    You're making too many requests. Wait for the duration specified in the `Retry-After` header. Rate limits are per-user, not per-token.
  </Accordion>

  <Accordion title="Read-only mode — can't create or update">
    Either your token only has `mcp:read` scope, or the `read_only=true` query parameter is set. Create a new token with `mcp:write` scope or remove the query parameter.
  </Accordion>
</AccordionGroup>