Connect aishaa to Claude or ChatGPT (MCP)

Minimum role: Viewer
Applies per: user
Last updated: 12 October 2026
aishaa version: 80c056408

Menu path: No menu in aishaa; you set up the connection in the connectors of Claude or ChatGPT

In short: aishaa has a built-in MCP connection. With it, you add aishaa as a connector to Claude, ChatGPT or another AI assistant that supports MCP, and you sign in with your normal aishaa account. You can then ask questions in your own words, such as “What were customers contacting us about last month?” or “Which tickets need attention right now?”. The assistant works in aishaa with exactly your permissions. For everyone, it is reading. Anyone with admin rights can also make proposals and prepare things through the same connection: use Tell aishaa, review proposals, propose notices, design workflows as drafts, have ticket views and action cards built, save a plugin’s own wiring, lock configuration and manage WhatsApp templates.

Where to find this

There is no screen for this connection in aishaa itself. You set it up in the connectors (sometimes called “integrations” or “MCP servers”) of your AI assistant. The address of the connection is:

https://app.aishaa.nl/api/mcp

When you add it, the aishaa sign-in screen opens. You sign in with your own aishaa account.

Who: everyone from the Viewer role. The connection is personal: the assistant only sees the organisations you have access to and only gets the tools that belong to your role. Which tools belong to which role is stated per section below.

The aishaa sign-in screen that opens after you have added the connection address in Claude or ChatGPT.

What MCP is

MCP (Model Context Protocol) is an open standard that lets an AI assistant securely request data from another application. aishaa offers such a connection. The assistant gets a fixed set of “tools” (questions and instructions it may give aishaa), and aishaa answers each question only with data you are allowed to see in aishaa yourself. You do not need to call the tools yourself; the assistant chooses them based on your question.

The names of the tools start with their subject: orgs_ (organisations), tickets_, customers_, chats_ (internal chat), knowledge_ (what aishaa knows), docs_ (this documentation), taxonomy_ (topics) and, depending on your role, config_ (configuration), workflows_, views_, plugins_, channels_ (WhatsApp templates) and setup_ (onboarding). The names below help you understand what is possible and, if needed, steer the assistant more precisely.

Add aishaa as a connector

The exact buttons differ per assistant and sometimes change. The steps are the same everywhere:

In Claude, ChatGPT or your other assistant, open the settings for connectors.
Choose the option to add your own connector (custom connector or MCP server).
Enter https://app.aishaa.nl/api/mcp as the address. Give the connector a recognisable name, for example “aishaa”, if the assistant asks for one.
The aishaa sign-in screen opens. Sign in with your aishaa account.
Back in the assistant, the connector is ready. Turn it on for the conversation in which you want to use it.
Test it with a simple question, for example “Which organisations can I see in aishaa?” or “How many tickets do we have?”.

If the connector does not work with an assistant, check that assistant’s documentation to see whether it supports custom connectors with sign-in (OAuth) and where to add them.

Choose an organisation

If you have access to one organisation, aishaa selects it automatically. You do not need to mention anything.
If you have access to several organisations, the assistant first retrieves the list (tool orgs_list) and uses the organisation you name. So say which organisation your question is about, or ask “Do this for all my organisations”: searching tickets, requesting figures and the attention list also work across all your organisations at once.

See Working with multiple organisations.

What you can ask (from Viewer)

These tools are available to everyone from the Viewer role. They only read; the assistant cannot change anything in aishaa through these tools.

Tool	What the assistant can do with it	Example question
`orgs_list`	List the organisations you have access to.	“Which organisations can I see in aishaa?”
`orgs_get_workspace`	Retrieve the name of an organisation, your own user and the total number of tickets.	“How many tickets are there in aishaa in total?”
`tickets_search`	Search tickets with filters you can combine, with a short summary per ticket and, on request, the outcome of completed conversations.	“Find this week’s open WhatsApp tickets about returns.”
`tickets_get_stats`	Volumes over a period, per topic, channel, status, day or week, with the number of closed tickets, the share handled without human intervention, the median first response time of a colleague and customer satisfaction (the last 30 days by default).	“What were customers contacting us about last month?”
`tickets_list_attention`	The list of what needs attention now: tickets with an error, urgent and important tickets, open tickets that have been waiting too long for a colleague, snoozes that end within 24 hours and unassigned tickets. An admin also sees the proposals and questions from aishaa that are waiting for a decision.	“What should I pick up first today?”
`tickets_get`	Read one ticket with its status, channel, customer, assignment, the outcome if the conversation has been completed, and the messages from the customer and colleagues. Proposals from aishaa and internal notes are not included.	“Summarise ticket 4821 for me.”
`tickets_get_actions`	List all actions on one ticket, with each action’s status (pending, executed, failed or rejected), the data used, the result, the error message, the reason for rejection and who did what and when.	“Why did the return action on ticket 4821 fail?”
`tickets_get_record_data`	Read the records retrieved from the connected systems for a ticket, per record type (for example orders or case files). This is the data as it was recorded with the ticket; the assistant does not search your system live.	“Which record belongs to ticket 4821, and has it been shipped yet?”
`customers_get_history`	The earlier conversations of the customer behind a ticket, with for each conversation what the customer needed, what was done and how it ended.	“Has this customer reported this before?”
`knowledge_get_topic_memory`	Read what aishaa knows per topic: the organisation’s rules and the facts aishaa learned from how colleagues adjusted proposals, with how often a fact has been confirmed and how many contradictions are open.	“What does aishaa know about the warranty topic?”
`knowledge_search_memory`	Search what aishaa has learned from handled conversations: question and answer pairs and scenarios, with the ticket each memory comes from.	“What has aishaa learned about delivery times to Belgium?”
`taxonomy_list`	List the organisation’s topics (support areas and query patterns).	“Which topics does aishaa distinguish for us?”
`config_list_notices`	List the account’s notices: short facts that apply for a while, with the text, for whom, for which organisations, the first and last day and the status.	“Which notices apply right now?”
`chats_list`, `chats_search`, `chats_get`, `chats_get_attachment`	Read your own internal chats: the list as the chat in aishaa shows it, search in messages, read a chat with reactions and attachments, and open an attachment. Only chats you may also read in aishaa yourself.	“What did my colleague say in the chat yesterday about the new delivery times?”
`docs_list`	List the aishaa documentation: for each article the title, summary, chapter, where it is in the app and which role you need for it.	“Where do I set the opening hours?”
`docs_read`	Read one documentation article in full, with its date, minimum role, menu path and link.	“Explain how the 24-hour window works.”

More about the terms in this table: What aishaa knows, Notices and Records from connected systems on a ticket.

View the configuration and make proposals (from Organisation admin)

Anyone who may manage AI settings (from the Organisation admin role) gets extra tools through the same connection. With them you can read how aishaa is set up, see who changed what, and give aishaa instructions just as you do with Tell aishaa on the Changes page. Everything that determines how aishaa behaves towards customers first becomes a proposal: it only applies once you have approved it.

Tool	What the assistant can do with it	Example question
`config_get`	Read an organisation’s configuration: the organisation information, the agents with their instructions and tools, the writing style per channel, the active topic rules, the knowledge documents with their status and the settings for tickets that need no reply.	“How is aishaa set up for WhatsApp for us?”
`knowledge_get_document`	Read one knowledge document in full (the text is cut off at 12,000 characters).	“What does our knowledge document on return conditions say?”
`config_list_skills`	List the skills the account’s agents can get, with the tools they bring and which agents already have them.	“Which skills does our agent have?”
`config_search_changes`	Search the change history: every change to the configuration and to the facts aishaa learned, newest first, with who (a person, the AI or the system), where and why.	“What changed in the instructions last week?”
`config_get_change`	View one change in detail, with the old and new value per field.	“Show exactly what was changed in that change.”
`tell_aishaa`	Give aishaa an instruction or question about your customer service, in your own words.	“Return labels are free from now on, please update that.”
`config_propose_organisation_instructions`	Make a proposal for an organisation’s own instructions (rules that only apply to that organisation).	“Add to this organisation’s instructions that we always address customers formally.”
`config_list_proposals`	Show the proposals still waiting for a decision, with the original instruction, the reason and every change with its old and new value.	“Which aishaa proposals are still open?”
`config_approve_proposal`	Approve a proposal, after which the changes take effect immediately. Only after you have agreed.	“Approve that proposal.”
`config_reject_proposal`	Reject a proposal. Nothing changes.	“Reject that proposal, we will keep it as it is.”
`config_list_questions`	Show the questions aishaa asked back that have not been answered yet.	“What is aishaa still waiting for us to answer?”
`config_dismiss_question`	Dismiss a question from aishaa without answering it. The original instruction is then not carried out.	“Just dismiss that question.”
`config_propose_notice`	Propose a notice, for example a delay or a closing day, with a last day. The notice only applies after approval.	“Add that we are closed on 25 December.”
`config_decide_notice`	Decide on a notice on your behalf: approve or reject it, end it now or extend it. Only after you have said so.	“Extend that notice by a week.”
`config_lock`	Lock one piece of configuration once it has been checked and is correct, so that nothing can change it any more. Unlocking is only possible in aishaa itself, by a person; there is deliberately no tool for that.	“Lock this knowledge document.”

From the Account admin role, the assistant can also make proposals about the account’s agents:

Tool	What the assistant can do with it
`config_propose_agent_skills`	Propose which skills an agent gains or loses.
`config_propose_agent_plugin_tools`	Propose what an agent may do with each tool of a plugin: a lookup on or off, an action off, propose only or execute on its own.
`config_propose_skill`	Propose a new custom skill, or a new version of an existing one.

These also become a proposal first. See Skills.

How an instruction is handled through the connection

You give the instruction in plain language. The assistant passes your words on to aishaa unchanged.
aishaa works it out and comes back with one of these outcomes:
– Applied: the change is in the configuration straight away. The assistant summarises what has changed.
– Proposal: the change is ready but does not apply yet. The assistant shows the changes with old and new values and asks whether you agree. Only after your yes does it approve the proposal. If you want it differently, say so: aishaa makes a new proposal that replaces the old one.
– Question back: aishaa needs more information. Answer the question in the conversation; the assistant passes your answer on.
– Answered: you asked a question about your settings; the answer is in the conversation.
– Nothing to do or Rejected: aishaa explains why nothing has changed.
Every change goes into the change history and can be reverted later.

Proposals and questions that arise through the connection also appear on the Organisation > Intelligence > Changes page and in the chat with aishaa. So you can review them there too, and the other way round. A proposal that nobody decides on expires by itself; see Tell aishaa for the time limit and the full explanation.

What tell_aishaa does not do

Through tell_aishaa, aishaa can change organisation information, the writing style per channel, the general instructions of an agent, rules for one topic and the settings for tickets that need no reply, and revert earlier changes. aishaa does not manage users, accounts, other settings or knowledge documents this way, and never carries out a business action such as a discount or refund. If aishaa retrieves something from the web, whatever is based on it always becomes a proposal.

Design workflows (from Organisation admin)

The assistant can design a workflow (“when this happens, do that”) for you and save it as a draft. You always publish it yourself in aishaa; there is deliberately no tool for that.

Tool	What the assistant can do with it
`workflows_get_guide`	Read the guide: what a workflow definition looks like, all events with their fields, all building blocks with their inputs and exits, and the plugin actions and colleagues of this organisation. The assistant reads it before writing anything.
`workflows_list`	List the workflows with their status (draft, active, paused), the event they start on and this week’s runs.
`workflows_get`	Read one workflow: the draft, the live version and earlier versions, what is still blocking publication, and on request the latest runs and why an event did or did not start a run.
`workflows_save_draft`	Create a new workflow or replace the draft of an existing one. Nothing changes live. The response names what is still blocking publication and gives a link to the workflow in aishaa.

See The workflow definition (for AI assistants) and Create, test and publish a workflow.

Have ticket views and action cards built (from Organisation admin)

You do not create a ticket view (an extra tab next to the ticket) or an action card (the display of a plugin action) in aishaa, but together with the assistant through this connection. You simply ask for one; the assistant uses the tools below. The full explanation is in Have Claude build a ticket view and Have Claude build an action card.

Tool	What the assistant can do with it
`views_get_guide`	Read the writing guide for a ticket view or an action card. This is the contract a view must meet; the assistant reads it before writing anything.
`views_get_data_sources`	Retrieve, per connected plugin, which types of records exist, which data can be retrieved, what it looks like and which actions exist, including the plugin’s sample responses. No customer data is used for this.
`views_list`	List which ticket views and action cards already exist, including drafts.
`views_get`	Read one view in full, to create a new version of it.
`views_save`	Save the written view as a draft and return a preview link with it that is valid for one week and can be opened without signing in.
`views_preview`	Show the draft in a chosen state and screen width, or against a real ticket or a real action.
`views_get_ticket_data`	Retrieve the data one ticket has for a view, to check the view against reality.
`views_publish`	Publish the draft, so the view appears as a tab or becomes the card for its actions. Only after you have approved.
`views_delete_draft`	Permanently discard a draft from your account.

A plugin’s own wiring (from Organisation admin)

For a plugin where you may decide yourselves which records and actions it offers, the assistant can create that own wiring for you. See Decide for yourself what a plugin offers.

Tool	What the assistant can do with it
`plugins_get_own_wiring`	Read whether you may wire the plugin yourself, which wiring is active now, the default wiring, the own wiring of the account and the organisation, the available fields and the guide.
`plugins_save_own_wiring`	Save a own wiring. aishaa checks it first and runs every lookup for a test customer; it is only saved if every lookup finds records.
`plugins_reset_own_wiring`	Remove the own wiring, so that the organisation falls back to the account’s wiring, and the account to the default.

Onboarding (only while it is open)

As long as your account’s onboarding has not been completed, an Organisation admin also gets the setup_ tools. With them the assistant can help with setting up: read the checklist, enter the website, view channels, note the programs you use, request an integration for a program that does not exist yet, record your way of working and complete or skip steps, each time after you have said so. Once the onboarding is finished, these tools disappear. See Setting up aishaa with the onboarding.

Manage WhatsApp templates (from Account admin)

Anyone who may manage users and account settings can also manage the account’s WhatsApp templates through the connection. See WhatsApp templates.

Tool	What the assistant can do with it
`channels_list_whatsapp_templates`	View the templates as they currently are at Meta: name, language, category, status with any rejection reason, the text with its variables, what is filled in automatically from the ticket, the buttons, and whether the template can be edited.
`channels_save_whatsapp_template`	Create or change a template. The template then goes to Meta for review, so go through the exact text, variables and buttons with the assistant first.
`channels_delete_whatsapp_template`	Delete one language variant of a template. Other languages with the same name remain.
`channels_restore_whatsapp_template`	Restore a template that was deleted in the last 30 days.

Security and permissions

The assistant works with your permissions. What you may not see in aishaa, the assistant cannot see either. Every tool stays within the organisations you have access to.
For the Viewer, Agent and Team lead roles, the connection is read-only. The tools that do change or propose something belong to an admin role: tell_aishaa, the config_propose_ tools, deciding on proposals, questions and notices, config_lock, saving workflow drafts, saving and publishing views, the own wiring, the setup_ tools and the WhatsApp template tools.
The assistant cannot reply to, assign, close or create tickets, cannot publish a workflow and cannot change anything in your webshop or other connected system.
Proposals from aishaa and internal notes of tickets are not given to the assistant.
The answers aishaa returns (for example the content of a ticket or a chat) are processed by the provider of your AI assistant. Check whether that fits your data processing agreements before you let colleagues use the connection.
To stop the connection, remove the connector in your assistant.

Good to know

The connection is per user. Every colleague who wants to use it adds the connector and signs in themselves.
Without an organisation name, for an account with several organisations, the assistant may ask you to choose. Name the organisation in your question to avoid this.
tickets_search returns a limited number of tickets at a time; the assistant can page through them. For large numbers, ask for figures (tickets_get_stats) rather than a list.
Records through tickets_get_record_data are the data retrieved with the ticket when it was handled. For the current state, look in the source system itself or on the record tab of the ticket.
With docs_list and docs_read, the assistant reads the aishaa documentation itself. So feel free to ask how something works in aishaa; the assistant gives the source and the date.
No separate API key or token is needed; you sign in with your aishaa account. Connections other than MCP (a public API, webhooks, Zapier) do not exist; see API, webhooks and Zapier: what is and is not available.