Connect tkana to your AI tools
A team member can ask Claude or Claude Code about their work in tkana. For example: “Which customers are waiting for a person?” or “What bookings are there today?” Each person signs in with their own tkana login. No one pastes a key.
The connection only reads. The AI tool cannot change a record, send a message, or create anything in tkana.
What you need
Section titled “What you need”- An owner turns AI tools on for the business. Until they do, no one can connect.
- Each person signs in with their own tkana login. The AI tool sees what that person’s role sees in the portal, and nothing more.
- The connector address:
https://mcp-dev.tkana.sa/api/mcp/work/mcpTurn AI tools on
Section titled “Turn AI tools on”Only an owner can do this. The switch is off by default.
- In the portal, open Account settings, then AI tools.
- Read the warning beside the switch.
- Turn on Let your team connect AI tools.
The page then shows the address and the steps for each tool, and lists everyone who has connected. Every role can open this page. A member sees the steps when the switch is on, and a line telling them to ask an owner when it is off.
Connect Claude
Section titled “Connect Claude”- In Claude, open Settings, then Connectors.
- Choose Add custom connector, and paste the address.
- Sign in to tkana.
- Pick the business, check what the connector can read, and click Allow.
If you belong to more than one business, the connector reads the one you pick.
Connect Claude Code
Section titled “Connect Claude Code”Run this in your terminal:
claude mcp add --transport http tkana https://mcp-dev.tkana.sa/api/mcp/work/mcpThen run /mcp in Claude Code and sign in to tkana. Pick the business and click
Allow. There is no key to paste.
What the AI tool can read
Section titled “What the AI tool can read”It can answer questions about the data your role can open in the portal:
- Customers. A customer’s record and tags, a summary of their conversations, tickets and bookings, and the items still open for them.
- Tickets. The ticket list, one ticket with its history, and who tickets can be assigned to.
- Bookings. The booking list, one booking, the free slots for a day, and the services and staff you can book.
- Conversations. The conversation list, the messages of one conversation, which conversations are waiting for a person, and the state of one conversation.
- Sales. Follow-ups (what is due, overdue or coming up, and whose they are), a contact’s history and the team’s notes, the customer pipelines with their cards, and Sales › Insights: follow-up figures, leads and where they came from, how fast a person answered, the funnel, wins and why leads were lost. The pipelines need access to customers; the insights need access to the dashboard.
- Team and results. The team roster, workload and performance, the AI resolution rate over time, and customer satisfaction (CSAT): how customers rated the chats that ended. Owners can read the team answers. Other roles with access to the dashboard can read the resolution rate, and CSAT for the conversations they can open, with their own row as the only teammate row. A business whose plan has no CSAT gets no ratings.
A member whose role hides a part of the portal gets nothing from that part. A member who is limited to their own bookings, or to the conversations assigned to them, gets only those. When a result is narrowed this way, an empty answer does not mean there is nothing: the AI tool is told to say so.
What it cannot do
Section titled “What it cannot do”- Change a customer, ticket, booking or conversation.
- Send a message to a customer.
- Read anything your role cannot open in the portal.
- Read a business you did not pick when you allowed it.
A role change reaches an open connection within 15 minutes.
If the AI tool says it cannot read
Section titled “If the AI tool says it cannot read”The AI tool repeats the message tkana gives it. It never reports a refusal as “nothing found”.
| Message | What it means |
|---|---|
| An owner turned AI tools off for the business. | The switch is off. An owner turns it on in Account settings, then AI tools. Connections work again with no new sign-in. |
| An owner disconnected you from AI tools for the business. | An owner blocked you. Ask them to click Allow again. |
| Your role in the business doesn’t include anything an AI tool can read. | Your role opens no part of the portal that the tool can read. Ask an owner to change your role. |
Disconnect
Section titled “Disconnect”To disconnect your own tool, open Account settings, then AI tools, and click Disconnect beside it. The tool stops at its next request. You can connect it again later from the tool. Removing the connector in the AI tool also works, but it does not remove the connection from this list, so use Disconnect here too.
To disconnect someone else, an owner opens the same page and clicks Disconnect beside the person. That person is cut off on every AI tool, and stays out until an owner clicks Allow again.
To stop everyone, an owner turns off Let your team connect AI tools. Every connection stops. Turning it back on restores them with no new sign-in. A connection not used for 90 days, including while the switch was off, needs a new sign-in.
A connection also ends when:
- the person is removed from the business, or
- no one uses it for 90 days. The person signs in again the next time they use the tool.