BotStar integration
BotStar is a chatbot builder for websites and Facebook Messenger. An agent can list and create bots, publish a bot, manage bot attributes, read and update a chat user's attributes, manage the bot's CMS (entities, their fields and their items) and send a message to a Facebook audience. Authentication is a BotStar API access token sent as a Bearer token.
Say what should happen.
The workflow builds itself.
What you can do with BotStar
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Cms entity, 5 operations
create_cms_entityCreate cms entityPOSTCreate a CMS entity (a content table) with a name and optional fields.delete_cms_entityDelete cms entityDELETEDelete a CMS entity of the bot.get_cms_entityGet cms entityGETGet one CMS entity with its fields.list_cms_entitiesList cms entitiesGETList the bot's CMS entities (content tables such as products) with their fields.update_cms_entityUpdate cms entityPATCHRename a CMS entity. To change its fields use update_cms_entity_fields.
Cms item, 5 operations
create_cms_entity_itemCreate cms entity itemPOSTCreate an item in a CMS entity: a name, a status and one value per entity field.delete_cms_entity_itemDelete cms entity itemDELETEDelete one item of a CMS entity by id.get_cms_entity_itemGet cms entity itemGETGet one item of a CMS entity. Each item also carries one key per entity field (its unique_name) with the field's value.list_cms_entity_itemsList cms entity itemsGETList the items of a CMS entity, paged (default 100 per page), optionally filtered by name or status. Each item also carries one key per entity field (its unique_name) with the field's value.update_cms_entity_itemUpdate cms entity itemPATCHChange an item of a CMS entity: name, status or field values. Keys left out keep their current value.
Bot, 4 operations
create_botCreate botPOSTCreate a new, empty bot with the given name (at most 250 characters). Returns its id.get_botGet botGETGet one bot by id: its id, name and team name.list_botsList botsGETList the bots of the account with their id, name and team. Pass a bot id to the other tools.publish_botPublish botPOSTPublish the bot's draft changes to the live bot that users talk to.
Bot attribute, 4 operations
create_bot_attributeCreate bot attributePOSTCreate a bot attribute (a bot-wide variable) of type string, number or date with a value.delete_bot_attributeDelete bot attributeDELETEDelete a bot attribute (a bot-wide variable) by id.list_bot_attributesList bot attributesGETList the bot attributes (bot-wide variables) with their name, description, value and data type.update_bot_attributeUpdate bot attributePATCHChange a bot attribute's description or value. Leave a field out to keep its current value.
Cms field, 3 operations
create_cms_entity_fieldsCreate cms entity fieldsPOSTAdd one or more fields (columns) to a CMS entity, each with a unique_name, a display name and a data type.delete_cms_entity_fieldsDelete cms entity fieldsDELETEDelete fields from a CMS entity, picked by unique_name.update_cms_entity_fieldsUpdate cms entity fieldsPATCHRename fields of a CMS entity or change their options, each field picked by unique_name.
User, 2 operations
get_userGet userGETGet a chat user of the bot: name, email, channel, locale, timezone, tags and attributes. Custom user attributes come back as extra keys.update_user_attributesUpdate user attributesPATCHSet attributes of a chat user (first_name, last_name, email, gender, birthday, or custom user attributes by name). Attributes left out keep their value.
Message, 1 operation
send_messageSend messagePOSTSend a message to a Facebook Messenger user of a bot, in BotStar's message JSON format. Returns the recipient and message ids.
User attribute, 1 operation
create_user_attributeCreate user attributePOSTCreate a custom user attribute on the bot, with a name and a type (string, number, date or boolean).
Use BotStar from Claude Code, Cursor or Codex
Connect BotStar in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its BotStar operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect BotStar
- Create your workspace
Sign up free. Nothing to install.
- Connect BotStar once
Add your BotStar connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
BotStar integration FAQ
What can you do with the BotStar integration?
LiveContext exposes 25 operations on BotStar, covering cms entity, cms item, bot and bot attribute.
