olark
Server Details
Manage Olark live-chat operators and groups (teams): list, create, update, and assign to teams.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
8 toolsadd_operator_to_groupAdd operator to groupDestructiveInspect
MUTATES Olark data: adds an operator to a group (team). Olark API: POST /groups/{group_id}/operators (JSON body { operator_id }). Reversible via remove_operator_from_group. Adding to a nonexistent group returns 404.
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | The group (team) id to add the operator to (path only; required). | |
| operator_id | Yes | The operator id to add (sent in the JSON body; required). |
create_operatorCreate an operatorDestructiveInspect
MUTATES Olark data: creates a new operator (chat agent). Olark API: POST /operators (JSON). Required: email and password; nickname (display name) optional. NOTE: creating an operator CONSUMES A PAID SEAT (billing side effect). Returns the created operator.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The operator's login email (required). | ||
| fields | No | Additional documented Olark fields to send in the JSON write body — merged OVER the typed fields above. | |
| nickname | No | The operator's display name shown in chat. | |
| password | Yes | The operator's initial password (required). |
get_operatorGet an operatorRead-onlyInspect
Fetch a single operator (chat agent) by id. Olark API: GET /operators/{id}. Returns id, email, nickname, available.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The operator id. |
list_groupsList groupsRead-onlyInspect
List all groups (teams) on the Olark account. Olark API: GET /groups. Returns groups (each with id, name, and operator_ids — the members).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Olark pagination page number, 1-based (offset-based paging; ~100 records/page). | |
| params | No | Additional documented query-string filters to send verbatim (merged with the typed params above). |
list_operatorsList operatorsRead-onlyInspect
List all operators (chat agents) on the Olark account. Olark API: GET /operators. Returns operators (each with id, email, nickname, available). Only operators under the authenticated account are returned (sub-accounts are not).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Olark pagination page number, 1-based (offset-based paging; ~100 records/page). | |
| params | No | Additional documented query-string filters to send verbatim (merged with the typed params above). |
olark_requestRaw read requestRead-onlyInspect
Power-user escape hatch: GET any Olark API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the base, starting with a slash, INCLUDING any query string, e.g. "/operators?page=2" or "/groups". Returns the parsed JSON.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Full API path after the base, starting with "/", e.g. "/operators?page=2". |
remove_operator_from_groupRemove operator from groupDestructiveInspect
MUTATES Olark data: removes an operator from a group (team). Olark API: DELETE /groups/{group_id}/operators/{operator_id}. Reversible via add_operator_to_group. Does NOT delete the operator, only their group membership.
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | The group (team) id (path; required). | |
| operator_id | Yes | The operator id to remove from the group (path; required). |
update_operatorUpdate an operatorDestructiveInspect
MUTATES Olark data: updates an existing operator. Olark API: PUT /operators/{id} (JSON). Set nickname (display name) and/or available (online/offline status); use the fields passthrough for any other documented field. NOTE: Olark uses full PUT semantics — omitting a field may reset it to its default. The path id is never sent in the body.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The operator id to update (path only; required). | |
| fields | No | Additional documented Olark fields to send in the JSON write body — merged OVER the typed fields above. | |
| nickname | No | New display name. | |
| available | No | New online/offline (availability) status. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!