Integration

Aidbase integration

Aidbase is an AI customer support platform: a chatbot, a ticket form and an email inbox that answer from your own knowledge. Add websites, YouTube videos and FAQs as knowledge, train them and connect them to a chatbot, ticket form or email inbox; get AI replies from a chatbot; read chats, tickets and emails with their conversations (personal data), reply to tickets and emails, change their status or priority, and block a chat, ticket or email from further interaction. Left out: document upload (a signed upload URL plus a finalize step) and the API key check. Authentication is an API key created under Settings, API Keys in Aidbase with the permissions you choose, sent as a Bearer token. The vendor marks the API as beta.

Connect Aidbase How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Aidbase.Built from the 40 Aidbase tools below, on the connection you add once.

What you can do with Aidbase

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.

Knowledge, 12 operations

add_chatbot_knowledgeAdd chatbot knowledgePUTConnects a knowledge item to a chatbot so its answers draw on it. The item must have been trained first (train_knowledge_item).
add_email_inbox_knowledgeAdd email inbox knowledgePUTConnects a knowledge item to an email inbox. The item must have been trained first (train_knowledge_item).
add_ticket_form_knowledgeAdd ticket form knowledgePUTConnects a knowledge item to a ticket form. The item must have been trained first (train_knowledge_item).
delete_knowledge_itemDelete knowledge itemDELETEDeletes a knowledge item and returns the deleted item.
get_knowledge_itemGet knowledge itemGETReturns one knowledge item with its type and training state (trained_at, is_training, training_failed_at), for example to check whether a training session has finished.
list_chatbot_knowledgeList chatbot knowledgeGETLists the knowledge items connected to a chatbot, with their training state.
list_email_inbox_knowledgeList email inbox knowledgeGETLists the knowledge items connected to an email inbox, with their training state.
list_knowledge_itemsList knowledge itemsGETLists the knowledge sources of the account (websites, videos, documents and FAQs) with their training state, 25 per page by default. Page on with next_cursor.
list_ticket_form_knowledgeList ticket form knowledgeGETLists the knowledge items connected to a ticket form, with their training state.
remove_chatbot_knowledgeRemove chatbot knowledgeDELETEDisconnects a knowledge item from a chatbot. The knowledge item itself is kept.
remove_email_inbox_knowledgeRemove email inbox knowledgeDELETEDisconnects a knowledge item from an email inbox. The knowledge item itself is kept.
remove_ticket_form_knowledgeRemove ticket form knowledgeDELETEDisconnects a knowledge item from a ticket form. The knowledge item itself is kept.

Block, 3 operations

block_chatbot_chatBlock chatbot chatPUTBlocks a chat, so the visitor of that chat session can no longer interact with the chatbot. The API has no way to lift a block. Needs an API key with the CHATBOTS_WRITE permission.
block_emailBlock emailPUTBlocks an email, so its sender can no longer interact through it. The API has no way to lift a block. Needs an API key with the EMAILINBOXES_WRITE permission.
block_ticketBlock ticketPUTBlocks a ticket, so the person who submitted it can no longer interact through it. The API has no way to lift a block. Needs an API key with the TICKETFORMS_WRITE permission.

Email, 3 operations

get_emailGet emailGETReturns one email with its subject, sender address, status and full conversation, so it holds personal data.
list_emailsList emailsGETLists the emails received by an inbox, optionally filtered by status and creation date. Returns subject, sender address, status and timestamps, so it holds personal data.
update_emailUpdate emailPUTChanges the status and/or priority of an email as the Aidbase app does, with its history and any side effects. Send at least one of the two. Needs an API key with the EMAILS_WRITE permission.

Faq item, 3 operations

create_faq_itemCreate faq itemPOSTAdds a question and its answer to an FAQ knowledge item, with an optional source URL and categories (unknown categories are created). Only for items of type faq.
delete_faq_itemDelete faq itemDELETEDeletes one question from an FAQ knowledge item and returns the deleted item.
list_faq_itemsList faq itemsGETLists the questions and answers of an FAQ knowledge item, with their source URL and categories. Only for items of type faq.

Reply, 3 operations

ask_chatbotAsk chatbotPOSTSends a message to a chatbot and returns its AI reply. Pass the session_id of the previous reply to continue the same conversation.
reply_to_emailReply to emailPOSTSends a reply to an email on behalf of the email inbox owner; the person who wrote the email receives it. Needs an API key with the EMAILS_WRITE permission.
reply_to_ticketReply to ticketPOSTSends a reply on a ticket on behalf of the ticket form owner, optionally as one of the account's personas; the customer who submitted the ticket receives it. Needs an API key with the TICKETS_WRITE permission.

Ticket, 3 operations

get_ticketGet ticketGETReturns one ticket with its status and full conversation. It is a customer's request, so it can hold personal data such as email addresses.
list_ticketsList ticketsGETLists the tickets submitted through a ticket form, optionally filtered by status and creation date. Returns ticket ids, status and timestamps; the conversation is read with get_ticket.
update_ticketUpdate ticketPUTChanges the status and/or priority of a ticket as the Aidbase app does, with its history and any side effects. Send at least one of the two. Needs an API key with the TICKETS_WRITE permission.

Chat, 2 operations

get_chatbot_chatGet chatbot chatGETReturns one chat of a chatbot with its full conversation (user and assistant messages). It is a visitor's transcript, so it can hold personal data.
list_chatbot_chatsList chatbot chatsGETLists the chats (visitor conversations) of a chatbot, optionally within a creation date range. Returns chat ids and timestamps; the messages are read with get_chatbot_chat.

Chatbot, 2 operations

get_chatbotGet chatbotGETReturns one chatbot with its public_id, title and allowed domains.
list_chatbotsList chatbotsGETLists the chatbots of the account with their public_id, title and allowed domains.

Email inbox, 2 operations

get_email_inboxGet email inboxGETReturns one email inbox with its id, alias and title.
list_email_inboxesList email inboxesGETLists the email inboxes of the account with their id, alias and title.

Ticket form, 2 operations

get_ticket_formGet ticket formGETReturns one ticket form with its public_id, title, allowed domains and input fields.
list_ticket_formsList ticket formsGETLists the ticket forms of the account with their public_id, title, allowed domains and input fields.

Faq, 1 operation

create_faq_knowledgeCreate faq knowledgePOSTCreates an FAQ knowledge item; add questions to it with create_faq_item. A knowledge item must be trained (train_knowledge_item) before it can be connected.

Sub page, 1 operation

list_knowledge_sub_pagesList knowledge sub pagesGETLists the pages found under a website knowledge item, each with its training state. Only for items of type website.

Train, 1 operation

train_knowledge_itemTrain knowledge itemPUTStarts a training session for a knowledge item and returns it with is_training true. Training takes a while; check it with get_knowledge_item. An item must be trained before it can be connected.

Video, 1 operation

create_video_knowledgeCreate video knowledgePOSTAdds a YouTube video as a knowledge source (only YouTube links are accepted). A knowledge item must be trained (train_knowledge_item) before it can be connected.

Website, 1 operation

create_website_knowledgeCreate website knowledgePOSTAdds a website as a knowledge source. A knowledge item must be trained (train_knowledge_item) before it can be connected to a chatbot, ticket form or email inbox.

Use Aidbase from Claude Code, Cursor or Codex

Connect Aidbase in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Aidbase operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Aidbase

Create your workspace
Sign up free. Nothing to install.
Connect Aidbase once
Add your Aidbase 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.