MCP integrations
MCP (Model Context Protocol) is an open standard that lets AI assistants work inside other apps. Tato uses it in two ways:
- Tato works in your apps. Tato can read and update your work in apps like Jira and Confluence, right from Tato chat.
- Your AI assistant works with Tato. Claude, ChatGPT, or Microsoft Copilot can look up your Tato projects and meetings without you opening Tato.
Tato works in your apps
- Connect your apps to Tato (for admins): add an app once for your organization and choose which projects can use it.
- Available apps: every app you can connect, what Tato can do in each, and what setup it needs.
- Use connected apps in chat (for everyone): connect your own account and start asking Tato to work in your apps.
Your AI assistant works with Tato
- Use Tato from Claude, ChatGPT, or Copilot (for admins): turn on access for your organization and choose who can connect.
For technical readers: when Tato works in your apps, Tato is the MCP client and the app is the MCP server. When your AI assistant works with Tato, Tato is the MCP server.
Frequently asked questions
Do I need to share an API key with Tato?
No. Every connection uses OAuth, the same sign-in flow you use to let any other app access your account. You never copy or store an API key or secret for Tato.
Who needs to set this up?
An organization admin sets up each app once in Tato. Some apps, like Jira and Confluence, also need an admin of that app to approve Tato. After that, each person connects their own account from Tato chat.
Can a connection see more than I can?
No. Tato only reaches what your account in the other app can already see, and an AI assistant connected to Tato only reaches what you can already see in Tato.
What if an app I use isn't listed?
We're adding apps regularly. Reach out to support@tato.co and we'll let you know the status.
Questions? Reach out at support@tato.co.