# How to integrate Slite MCP with Mastra AI

```json
{
  "title": "How to integrate Slite MCP with Mastra AI",
  "toolkit": "Slite",
  "toolkit_slug": "slite",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/slite/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/slite/framework/mastra-ai.md",
  "updated_at": "2026-03-29T06:50:56.164Z"
}
```

## Introduction

This guide walks you through connecting Slite to Mastra AI using the Composio tool router. By the end, you'll have a working Slite agent that can search all notes about onboarding process, create a new note in project channel, summarize recent updates from team docs through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Slite account through Composio's Slite MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Slite with

- [OpenAI Agents SDK](https://composio.dev/toolkits/slite/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/slite/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/slite/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/slite/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/slite/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/slite/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/slite/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/slite/framework/cli)
- [Google ADK](https://composio.dev/toolkits/slite/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/slite/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/slite/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/slite/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/slite/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Set up your environment so Mastra, OpenAI, and Composio work together
- Create a Tool Router session in Composio that exposes Slite tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Slite tool definitions and attach them as a toolset
- Build a Mastra agent that can reason, call tools, and return structured results
- Run an interactive CLI where you can chat with your Slite agent

## What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.
Key features include:
- MCP Client: Built-in support for Model Context Protocol servers
- Toolsets: Organize tools into logical groups
- Step Callbacks: Monitor and debug agent execution
- OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

## What is the Slite MCP server, and what's possible with it?

The Slite MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Slite account. It provides structured and secure access so your agent can perform Slite operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `SLITE_ASK_QUESTION` | Ask Question | Tool to ask a question to your Slite notes in natural language. Use when you need to query or search information across your notes. Supports optional filters to narrow results by parent note or specific assistant. |
| `SLITE_CREATE_NOTE` | Create Note | Tool to create a note from markdown or HTML content with optional template. Use when you need to create a new note in Slite with specified content and title. |
| `SLITE_DELETE_NOTE_BY_ID` | Delete Note By ID | Tool to permanently delete a note and all its children by ID. Use when you need to remove a note irreversibly. This operation cannot be undone. |
| `SLITE_FLAG_NOTE_AS_OUTDATED` | Flag Note as Outdated | Tool to set Outdated status on a note with a reason. Use when you need to flag a note as containing outdated information. |
| `SLITE_GET_AUTHENTICATED_USER` | Get authenticated user | Retrieves information about the currently authenticated user. Use this to get user details including email, display name, and organization information. |
| `SLITE_GET_NOTE_BY_ID` | Get Note By ID | Tool to retrieve a complete note by its ID including content in Markdown or HTML format. Use when you need to fetch the full details and content of a specific note. |
| `SLITE_GET_NOTE_CHILDREN` | Get Note Children | Tool to retrieve note children by parent note ID. Use when you need to fetch child notes beneath a specified parent note. Supports pagination for notes with more than 50 children using cursor-based navigation. |
| `SLITE_LIST_NOTES` | List Notes | Tool to list notes from Slite with optional filtering by owner. Use when you need to retrieve notes, optionally filtered by a specific user. Supports cursor-based pagination via the cursor parameter. |
| `SLITE_SEARCH_GROUPS` | Search Groups | Tool to search for groups by name in Slite. Use when you need to find groups matching a search query. Supports cursor-based pagination via the cursor parameter. |
| `SLITE_SEARCH_NOTES` | Search Notes | Tool to search notes based on a query with optional filters. Use when you need to find notes by search term, parent note, review state, or other criteria. Supports pagination and archived note inclusion. |
| `SLITE_SEARCH_USERS` | Search Users | Tool to search for users in Slite by email, name, or username. Use when you need to find users in the organization. |
| `SLITE_UPDATE_NOTE` | Update Note | Tool to update a note's content with markdown and/or title. Use when you need to modify an existing note's content or metadata. |
| `SLITE_UPDATE_NOTE_ARCHIVED_STATE` | Update Note Archived State | Tool to update the archived state of a note in Slite. Use when you need to archive or unarchive a note. |
| `SLITE_UPDATE_NOTE_OWNER` | Update Note Owner | Tool to update the owner of a note. Use when you need to transfer note ownership to a user or group. Either userId or groupId must be provided. |
| `SLITE_UPDATE_TILE_IN_NOTE` | Update Tile in Note | Tool to update or create a tile within a Slite note with structured header and markdown content. Use when you need to update tile information including title, status, content, icon, or external URL. |
| `SLITE_VERIFY_NOTE` | Verify Note | Tool to set a note's verification status to Verified with optional expiration. Use when you need to mark a note as verified or update its verification expiration date. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Slite MCP server is an implementation of the Model Context Protocol that connects your AI agent to Slite. It provides structured and secure access so your agent can perform Slite operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Node.js 18 or higher
- A Composio account with an active API key
- An OpenAI API key
- Basic familiarity with TypeScript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key.
- You need credits or a connected billing setup to use the models.
- Store the key somewhere safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Slite through MCP.

### 2. Install dependencies

Install the required packages.
What's happening:
- @composio/core is the Composio SDK for creating MCP sessions
- @mastra/core provides the Agent class
- @mastra/mcp is Mastra's MCP client
- @ai-sdk/openai is the model wrapper for OpenAI
- dotenv loads environment variables from .env
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio
- COMPOSIO_USER_ID tells Composio which user this session belongs to
- OPENAI_API_KEY lets the Mastra agent call OpenAI models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

What's happening:
- dotenv/config auto loads your .env so process.env.* is available
- openai gives you a Mastra compatible model wrapper
- Agent is the Mastra agent that will call tools and produce answers
- MCPClient connects Mastra to your Composio MCP server
- Composio is used to create a Tool Router session
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
```

### 5. Create a Tool Router session for Slite

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "slite" for Slite access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["slite"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Slite MCP URL:", composioMCPUrl);
```

### 6. Configure Mastra MCP client and fetch tools

What's happening:
- MCPClient takes an id for this client and a list of MCP servers
- The headers property includes the x-api-key for authentication
- getTools fetches the tool definitions exposed by the Slite toolkit
```typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
```

### 7. Create the Mastra agent

What's happening:
- Agent is the core Mastra agent
- name is just an identifier for logging and debugging
- instructions guide the agent to use tools instead of only answering in natural language
- model uses openai("gpt-5") to configure the underlying LLM
```typescript
const agent = new Agent({
    name: "slite-mastra-agent",
    instructions: "You are an AI agent with Slite tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Slite toolsets
- maxSteps limits how many tool calls the agent can take in a single run
- onStepFinish is a hook that prints intermediate steps for debugging
```typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        slite: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
```

## Complete Code

```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["slite"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      slite: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "slite-mastra-agent",
    instructions: "You are an AI agent with Slite tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { slite: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();
```

## Conclusion

You've built a Mastra AI agent that can interact with Slite through Composio's Tool Router.
You can extend this further by:
- Adding other toolkits like Gmail, Slack, or GitHub
- Building a web-based chat interface around this agent
- Using multiple MCP endpoints to enable cross-app workflows

## How to build Slite MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/slite/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/slite/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/slite/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/slite/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/slite/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/slite/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/slite/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/slite/framework/cli)
- [Google ADK](https://composio.dev/toolkits/slite/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/slite/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/slite/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/slite/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/slite/framework/crew-ai)

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Slite MCP?

With a standalone Slite MCP server, the agents and LLMs can only access a fixed set of Slite tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Slite and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Slite tools.

### Can I manage the permissions and scopes for Slite while using Tool Router?

Yes, absolutely. You can configure which Slite scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Slite data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)