Skip to main content
Any AI tool that supports the Model Context Protocol can connect to Trilo. Here’s what you need.

​
Connection Details

SettingValue
Endpointhttps://api.trilo.chat/mcp
TransportHTTP (Streamable HTTP)
AuthenticationAuthorization: Bearer trilo_pat_...

​
Setup

1

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

Configure your client

Most MCP clients use a JSON config format. The standard config looks like:
{
  "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).
3

Verify the connection

Ask your AI tool:
List my Trilo workspaces
If it returns your workspace data, you’re connected.

​
Options

Append query parameters to the MCP URL for additional control:
ParameterDescriptionExample
workspace_idRestrict to a specific workspacehttps://api.trilo.chat/mcp?workspace_id=abc-123
read_onlyForce read-only modehttps://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
Create separate tokens for each AI tool or machine. If one is compromised, you can revoke it without affecting your other tools.

​
Troubleshooting

  • 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
Your token was created without MCP scopes. Create a new token and select at least mcp:read.
MCP sessions expire after 30 minutes of inactivity. Most clients reconnect automatically. If not, restart the MCP connection in your client.
You’re making too many requests. Wait for the duration specified in the Retry-After header. Rate limits are per-user, not per-token.
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.