Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
LiveChat Configuration (BYOK) icon

LiveChat Configuration (BYOK)

Read LiveChat greeting campaigns, auto-access rules, group routing status, license properties and webhook registrations with your own personal access token

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderLiveChat Configurationunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which greeting campaigns do we have configured in LiveChat?
Tools called
list_greetings
Show LiveChat greeting 123
Tools called
get_greeting
How does LiveChat route visitors to groups by domain or country?
Tools called
list_auto_accesses
Is LiveChat group 19 online right now?
Tools called
get_group_routing_status
What custom properties are stored on our LiveChat license?
Tools called
list_license_properties
Are webhooks enabled for my LiveChat app?
Tools called
get_license_webhooks_state

About

LiveChat Configuration (BYOK) lets an AI assistant read your own LiveChat Configuration data through the LiveChat Configuration API with a key you supply (LiveChat Account ID). Read-only: 7 tools (list_greetings, get_greeting, list_auto_accesses, get_group_routing_status, list_license_properties, get_license_webhooks_state, list_webhooks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.livechatinc.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Configuration. LiveChat Configuration and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the LiveChat Configuration API (api.livechatinc.com) with a BYOK key; documentation: https://platform.text.com/docs/management/configuration-api. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • List greetingsList the greeting campaigns (targeted messages shown to website visitors): name, type, active flag, group, trigger rules and message text.
  • Get greetingGet one greeting campaign by id: name, type, active flag and schedule, group, trigger rules and message text.
  • List auto accessesList the auto-access rules in order: which chat groups receive visitors matching domain, page URL or country conditions.
  • Get group routing statusGet a group (team) with its language and current routing status (online, offline or online for incoming chats), without listing members.
  • List license propertiesList the key-value properties stored on the LiveChat license, grouped by namespace; optionally limit by namespace or name prefix.
  • Get license webhooks stateCheck whether the webhooks of one application are enabled on the LiveChat license.
  • List webhooksList the webhooks registered for one application: target URL, description, event action and type.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-livechat-configuration.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 7 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-livechat-configuration.connectorbay.com/mcp
RESTPOST https://byok-livechat-configuration.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-livechat-configuration.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your LiveChat Account ID in the X-Upstream-Key header (get one at platform.text.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

LiveChat Configuration connector: questions and answers

What is the LiveChat Configuration connector?

LiveChat Configuration (BYOK) lets an AI assistant read your own LiveChat Configuration data through the LiveChat Configuration API with a key you… It is a hosted MCP server with 7 tools such as List greetings, Get greeting, List auto accesses, Get group routing status, List license properties, Get license webhooks state, published by Unify Dynamics LLC. It is independent and not affiliated with LiveChat Configuration.

How do I connect LiveChat Configuration to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-livechat-configuration.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-livechat-configuration.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-livechat-configuration.json.

Do I need a LiveChat Configuration account or API key?

Yes: this is a bring-your-own-key connector. Create a LiveChat Account ID at https://platform.text.com/docs/authorization/personal-access-tokens and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is LiveChat Configuration read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the LiveChat Configuration connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Kaggle (BYOK)

Browse Kaggle datasets, competitions, leaderboards, notebooks and models, and see your own competition submissions, with your own username and API key

Live · MCP + REST11 tools

Katalon Test Ops (BYOK)

Read your Katalon TestOps projects, test runs, test cases, test suites, test results and agents with your own API key

Live · MCP + REST7 tools

Katalon Test Ops Execution (BYOK)

Read your Katalon TestOps v2 schedules, test runs, test results and run jobs from your tenant host with your own API key and project id

Live · MCP + REST7 tools

Kentik (BYOK)

Read your Kentik network observability inventory: devices, interfaces, sites, plans, flow tags, custom dimensions, labels and saved filters (US region)

Live · MCP + REST10 tools

Kernel (BYOK)

Read your Kernel cloud browser sessions, pools, profiles, extensions, deployed apps, deployments, invocations and organization limits with your own API key

Live · MCP + REST10 tools

Kevel (BYOK)

Read your Kevel ad server advertisers, campaigns, flights, ads, creatives, sites, zones and channels with your own API key

Live · MCP + REST11 tools

Documentation

Back to top

LiveChat Configuration (BYOK) — connector documentation

  • MCP endpoint: https://byok-livechat-configuration.connectorbay.com/mcp
  • REST API: POST https://byok-livechat-configuration.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-livechat-configuration.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own LiveChat Configuration LiveChat Account ID, sent in the X-Upstream-Key header and the LiveChat personal access token in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-livechat-configuration.connectorbay.com/health · Tool schemas: https://byok-livechat-configuration.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-livechat-configuration · agent@connectorbay.com

What LiveChat Configuration (BYOK) is for

LiveChat Configuration (BYOK) lets an AI assistant read your own LiveChat Configuration data through the LiveChat Configuration API with a key you supply (LiveChat Account ID). Read-only: 7 tools (list_greetings, get_greeting, list_auto_accesses, get_group_routing_status, list_license_properties, get_license_webhooks_state, list_webhooks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.livechatinc.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Configuration. LiveChat Configuration and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which greeting campaigns do we have configured in LiveChat?"
  • "Show LiveChat greeting 123"
  • "How does LiveChat route visitors to groups by domain or country?"
  • "Is LiveChat group 19 online right now?"
  • "What custom properties are stored on our LiveChat license?"
  • "Are webhooks enabled for my LiveChat app?"

What it does

  • list_greetings: List the greeting campaigns (targeted messages shown to website visitors): name, type, active flag, group, trigger rules and message text. Up to 100 per page.
  • get_greeting: Get one greeting campaign by id: name, type, active flag and schedule, group, trigger rules and message text.
  • list_auto_accesses: List the auto-access rules in order: which chat groups receive visitors matching domain, page URL or country conditions.
  • get_group_routing_status: Get a group (team) with its language and current routing status (online, offline or online for incoming chats), without listing members.
  • list_license_properties: List the key-value properties stored on the LiveChat license, grouped by namespace; optionally limit by namespace or name prefix.
  • get_license_webhooks_state: Check whether the webhooks of one application are enabled on the LiveChat license.
  • list_webhooks: List the webhooks registered for one application: target URL, description, event action and type.

BYOK key

You bring your own LiveChat Configuration LiveChat Account ID (https://platform.text.com/docs/authorization/personal-access-tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.livechatinc.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Create the token in the Text Developer Console (Settings > Authorization > Personal Access Tokens) with read scopes only, for example greetings:ro, access_rules:ro, groups--all:ro, properties.license.value--all:ro and webhooks.state:ro. The first value is the Account ID, the second the token.

Data sources

Live from the LiveChat Configuration API (api.livechatinc.com) with a BYOK key; documentation: https://platform.text.com/docs/management/configuration-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Configuration. LiveChat Configuration and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your LiveChat Configuration account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

LiveChat Configuration (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What LiveChat Configuration (BYOK) is. LiveChat Configuration (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own LiveChat Configuration data: Read LiveChat greeting campaigns, auto-access rules, group routing status, license properties and webhook registrations with your own personal access token. You bring your own LiveChat Configuration LiveChat Account ID; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one LiveChat Configuration call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.livechatinc.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If LiveChat Configuration rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What LiveChat Configuration receives. The request we make on your behalf, including the key and the arguments, under LiveChat Configuration's own terms and privacy policy. LiveChat Configuration acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer LiveChat Configuration gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your LiveChat Configuration data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. LiveChat Configuration (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at LiveChat Configuration at any time to end all access.

Children. LiveChat Configuration (BYOK) is a general-audience service operated by the adult using the assistant, under LiveChat Configuration's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

LiveChat Configuration (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the LiveChat Configuration (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. LiveChat Configuration (BYOK) provides: Read LiveChat greeting campaigns, auto-access rules, group routing status, license properties and webhook registrations with your own personal access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own LiveChat Configuration credentials and only access data you are allowed to access. LiveChat Configuration's terms apply to your use of LiveChat Configuration; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Configuration. LiveChat Configuration and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data LiveChat Configuration returns, lightly trimmed; it may be incomplete, delayed or changed by LiveChat Configuration. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your LiveChat Configuration account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent LiveChat Configuration's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; LiveChat Configuration may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your LiveChat Configuration key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action LiveChat Configuration takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-livechat-configuration

LiveChat Configuration (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. LiveChat Configuration (BYOK) never asks for them.

Get LiveChat Configuration (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own LiveChat Configuration LiveChat Account ID. Create one at https://platform.text.com/docs/authorization/personal-access-tokens, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to LiveChat Configuration. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with LiveChat Configuration.