# LiveChat setup for PopMCP

You end up pasting the Account ID and the Personal Access Token that the Text Developer Console shows you once, right after you create the token.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.livechatinc.com/v3.6
- Credentials screen: https://platform.text.com/console/settings/authorization
- Provider docs: https://platform.text.com/docs/authorization/personal-access-tokens

## Before you begin

- A LiveChat account on any plan, including the trial
- An agent seat with the Owner or Administrator role. A Personal Access Token can never exceed the permissions of the agent who created it
- Every scope picked at creation time. The Console does not let you edit a token's scopes afterwards

## Get your credentials

### 1. Sign in to the Developer Console

Open platform.text.com/console and sign in with the same email you use for the LiveChat agent app.

Screen: https://platform.text.com/console/

### 2. Open Personal Access Tokens

In the left sidebar go to Settings → Authorization → Personal Access Tokens. On older Console layouts the same screen sits under Tools → Personal Access Tokens.

Screen: https://platform.text.com/console/settings/authorization

### 3. Create the token and select every scope

Click Create new token +, enter `PopMCP` as the name, and tick every scope in the list. Click Create token +.

Screen: https://platform.text.com/console/settings/authorization

### 4. Copy the Account ID and the Personal Access Token

Copy Account ID and Personal Access Token into the matching PopMCP fields. If only the Base64 encoded token is visible, paste that into the Personal Access Token field and leave Account ID blank.

Screen: https://platform.text.com/console/settings/authorization

## Fields PopMCP asks for

- Account ID (accountId) [required]: Developer Console → Tools → Personal Access Tokens → create a token. Copy the "Account ID" shown on that screen. (If you only have the single "Base64 encoded token", paste it into the Personal Access Token field and leave this blank; we'll split it.)
- Personal Access Token (pat) [required]: From the same screen, copy the "Personal Access Token". Select all scopes when creating it so no operation is blocked. Sent as HTTP Basic auth (account ID : token) and stored encrypted; used server-side only.

## Verify

PopMCP shows the LiveChat connector as Connected and can list your recent chats and the agents on the licence without a 401.

## Troubleshooting

### 401 authentication_error

Cause: The Account ID and token are mismatched, or a stray space was copied along with the token.

Fix: Re-copy both values. LiveChat authenticates with HTTP Basic using account_id:personal_access_token, so if either half is wrong the whole pair fails.

### Some tools work but others return 403 with a missing-scope message

Cause: The token was created with a narrow scope set, and scopes are immutable once the token exists.

Fix: Create a new Personal Access Token with all scopes selected, paste it into PopMCP, then delete the old token in the Console.

### You closed the screen before copying the token

Cause: The token value is displayed exactly once.

Fix: Delete the token in the Console and create a replacement. There is no way to reveal an existing one.

### Agent-scoped calls fail even though the token is valid

Cause: A Personal Access Token can never exceed the permissions of the agent who created it, so a token made by a normal agent cannot see other agents' chats.

Fix: Recreate the token while signed in as the account Owner or an Administrator.

### The Authorization screen is not in the sidebar

Cause: Older Console layouts put Personal Access Tokens under Tools rather than Settings.

Fix: Open Tools → Personal Access Tokens, or go straight to platform.text.com/console/tools/personal-access-tokens.

---

Source: https://www.docs.popmcp.com/docs/integrations/livechat/