> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/tellius-mcp-server/tellius-as-an-mcp-client.md).
# Tellius as an MCP client
Connect Kaiya to systems such as Microsoft 365, Google Workspace, Slack, Notion, Salesforce, Snowflake and your own MCP servers, so it can read from them and, with your approval, write back to them.
The [Tellius MCP server](https://help.tellius.com/kaiya/tellius-mcp-server) lets an outside client, such as *Claude Desktop* or *Cursor*, call into Tellius. Tellius also works the other way round: it is an MCP client. Kaiya can call the MCP servers your organization has connected and bring their data into an answer, a Deep Insight, a Mission or an App.
Use this when the data you need lives outside your Business Views. For example, Kaiya can read your calendar, search Slack for a discussion, or pull open opportunities from Salesforce and use them next to your Business View data. Kaiya can also make changes in a connected system, such as drafting an email or adding rows to a Snowflake table. You approve each change before it happens.
{% hint style="info" %}
The **MCP Connectors** page under **Settings → Account** is for the opposite direction. It creates the credentials an outside MCP client uses to sign in to Tellius. See [Tellius MCP server](https://help.tellius.com/kaiya/tellius-mcp-server).
{% endhint %}
### **How connected systems work**
Two things must be true before you can use a system with Kaiya:
1. **An administrator has turned the system on** for your Tellius deployment, and set up its sign-in where the system needs one. See [Set up connected systems](#set-up-connected-systems-administrators).
2. **You have connected your own account.** See [Connect your account](#connect-your-account).
Kaiya always works through your own account, never a shared one. It can see and change only what your account in that system allows. If you connect a system while Kaiya is answering, the system is ready from your next message.
### **Set up connected systems (administrators)**
Administrators manage connected systems under **Settings → System → Administration → Integrations**, on the **MCPs** tab. The tab lists the built-in systems first, then any custom MCP servers your organization has added under **Custom MCPs**.
#### **The built-in systems**
| System | What Kaiya can work with | What the administrator sets up |
| -------------------- | ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Microsoft 365** | Outlook mail and calendar, Teams chats and channels, SharePoint and OneDrive files, and the people directory. | An app registration in Microsoft Entra, then its Client ID and Client Secret in Tellius. |
| **Slack** | Channel history and search. With writes allowed, posting messages, adding reactions and creating canvases. | A Slack app made from the manifest Tellius provides, then its Client ID and Client Secret. |
| **Notion** | Pages, blocks, databases and comments in the user's Notion workspace. | Nothing beyond turning it on. Notion handles sign-in itself. |
| **Salesforce** | Salesforce objects, flows and Apex, and data queries. Needs Salesforce Enterprise Edition or higher. | The Tellius managed package installed in the Salesforce org, and an MCP server activated there. |
| **Google Workspace** | Gmail, Google Drive, Calendar, Docs, Sheets, Slides and Meet, for the signed-in user. | An OAuth client in Google Cloud Console, then its Client ID and Client Secret in Tellius. |
{% hint style="info" %}
**Microsoft 365 in Tellius 6.4.** The Microsoft 365 connector runs as part of your Tellius deployment, so your users don't need a Microsoft 365 Copilot licence. One **Microsoft 365** card, with one **Enabled** switch, covers Mail, Calendar, Teams, SharePoint, OneDrive, People and Search. Your Microsoft administrator must grant admin consent for the app registration before users can connect. Once it is set up, each user connects Microsoft 365 from **Connectors** in a Kaiya chat.
{% endhint %}
**Google Workspace** has one parent card and a card for each Google product under it: Gmail, Google Drive, Google Calendar, Google Docs, Google Sheets, Google Slides and Google Meet. You set up one OAuth app, on the parent card, for all of them. Each product card has its own **Enabled** and **Allow writes** switches, so you can turn on only the products your teams need and allow writes for some products but not others. Users see a separate switch for each Google product when they connect their accounts.
#### **The controls on each system**
* **Enabled** makes the system available to users. Users can connect only the systems that are turned on.
* **Allow writes** lets Kaiya make changes in the system, such as sending, posting or creating. With it off, users can still read from the system, but Kaiya can't change anything there. **Allow writes** can be turned on only while **Enabled** is on.
* **OAuth app configured** or **OAuth app not configured** shows whether the system's sign-in is set up. Select **Configure OAuth app** to set it up, or **Edit OAuth app** to change it. See [Set up a system's sign-in](#set-up-a-systems-sign-in).
* **Setup instructions** appears instead for systems that need no OAuth app of your own, such as Notion.
* **Callback URL** is the address to register with the provider. It appears once a system is turned on. Select the copy icon beside it to copy it.
{% hint style="warning" %}
**Enabled** and **Allow writes** take effect as soon as you select them. You don't need to save the page.
{% endhint %}
When a system is turned on but its OAuth app isn't set up yet, the card warns you. Users can't connect that system until you set up its sign-in.
#### **Set up a system's sign-in**
Microsoft 365, Slack and Google Workspace sign users in through an OAuth app that your organization creates with the provider. You create the app once, and Tellius uses it for every user who connects.
1. On the system's card, select **Configure OAuth app**.
2. Copy the redirect URL shown at the top of the dialog. It is the same address as the card's **Callback URL**.
3. Select **Show setup instructions** for the steps to follow with that provider. In short:
* **Microsoft 365:** register a new app in the Microsoft Entra admin center with the redirect URL as a Web platform, add the Microsoft Graph delegated permissions Kaiya uses and grant admin consent, then create a client secret. Copy the secret's value straight away, because Microsoft hides it once you leave the page.
* **Slack:** select **Download Slack app manifest (.yaml)** in the dialog and use the file to create an app in your Slack workspace. The manifest already holds the scopes Kaiya needs and the redirect URL. Install the app to your workspace, copy its Client ID and Client Secret, and turn on **Slack MCP server access** under **App Assistant** in the Slack app settings. The app must be an internal app in that workspace. If Slack MCP server access is off, Slack returns the error "App is not enabled for Slack MCP server access."
* **Google Workspace:** in Google Cloud Console, set up the OAuth consent screen as **Internal**, enable the Google APIs Kaiya uses, add the scopes for those services, then create an OAuth client ID of type Web application with the redirect URL.
4. Paste the provider's **Client ID** and **Client Secret** into the dialog.
5. Select **Save**. To leave without saving, select **Cancel**.
Tellius stores the credentials encrypted. To change them later, select **Edit OAuth app**, enter the new values and select **Save**. To clear them, select **Remove**.
{% hint style="info" %}
Contact Tellius support before you create a new OAuth app. Support can confirm the app type and the exact scopes for your provider.
{% endhint %}
Two systems sign in differently:
* **Salesforce** needs no Client ID or Client Secret. Select **Install package** on the Salesforce card to install the Tellius managed package in your Salesforce org. Then, in Salesforce Setup, activate an MCP server, for example **sobject-all**, under **API Catalog → MCP Servers**. This second step is done in Salesforce only.
* **Notion** connects through Notion's own sign-in. Turn it on, and each user chooses their workspace and the pages Kaiya may use when they connect.
#### **Add a custom MCP server**
You can connect your organization's own MCP server, or a third-party one, alongside the built-in systems.
1. On the **MCPs** tab, select **Add custom server**.
2. Enter a **Name**. Users see this name when they connect the server.
3. Enter the **Remote MCP server URL**.
4. If the server needs an OAuth client of its own, select **Advanced settings** and enter the **OAuth Client ID** and **OAuth Client Secret**. Leave them empty otherwise. Tellius detects how the server signs users in.
5. Select **Add server**. To leave without adding it, select **Cancel**.
The server appears under **Custom MCPs** with a **Custom** badge, its own **Enabled** and **Allow writes** switches and its **Callback URL**. A server that offers no way to make changes has no **Allow writes** switch.
{% hint style="warning" %}
Add only servers from developers you trust. Tellius can't check the tools a third-party server offers, or whether they change later. Kaiya treats any tool on a custom server as a change, and asks for approval, unless the server marks that tool as read-only.
{% endhint %}
To remove a custom server, select **Remove this custom server** (the trash can) on its card.
To know how connected systems work, check out [this page](/tellius-6.4/kaiya/tellius-mcp-server/using-connected-systems-in-kaiya.md).
### **Related pages**
* [Tellius MCP server](https://help.tellius.com/kaiya/tellius-mcp-server)
* [How to create a Kaiya Mission](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission)
* [Kaiya Apps](https://help.tellius.com/kaiya/kaiya-apps)
* [Deep Insight](https://help.tellius.com/kaiya/understanding-ai-agents-and-agentic-flows/automated-workflows/deep-insight)
* [Slack Integration](https://help.tellius.com/settings/administration/slack-integration)
* [Teams Integration](https://help.tellius.com/settings/administration/teams-integration)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.tellius.com/tellius-6.4/kaiya/tellius-mcp-server/tellius-as-an-mcp-client.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
