MCP with tkana
The AI assistant you already use works on your organization in tkana.
Your organization's operations in tkana are available as MCP tools. Connect any MCP client, such as Claude, with your organization key, and your assistant can read and edit your agent, its skills and tools, your knowledge, your customers and your conversations. The key itself pins access to your organization.
How you use it
Real moments from your working day, and what the agent does in each.
Ask your assistant about today's conversations
Instead of opening the portal, ask your assistant and it reads from tkana.
Update the agent's knowledge from your assistant
Opening hours changed? Tell your assistant to update them in the agent's knowledge.
What the agent can do in it
The tools the agent uses inside the system, mid-conversation.
How it's connected
Who does what, from the first step until the agent is working.
We issue your organization key
The same key as the API.
Add the tkana server in your assistant
In the settings of the MCP client you use.
Your assistant sees tkana's tools
And works on your organization directly.
Which team it serves
The integration works inside the package that fits your team.
Questions
How is this different from the API?
The API is for your system, built on by your technical team. MCP is for the AI assistant you talk to yourself.
Can it reach other organizations?
No. The key is bound to your organization, and the tools are limited to it.
Related integrations
All integrations
Put your agent to work inside MCP
Book a demo and we'll show you the integration on your business, not a generic example.