# How to integrate Basin MCP with Mastra AI

```json
{
  "title": "How to integrate Basin MCP with Mastra AI",
  "toolkit": "Basin",
  "toolkit_slug": "basin",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/basin/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/basin/framework/mastra-ai.md",
  "updated_at": "2026-05-06T08:02:11.959Z"
}
```

## Introduction

This guide walks you through connecting Basin to Mastra AI using the Composio tool router. By the end, you'll have a working Basin agent that can create a new form for event signups, delete an old feedback form from project, get details of your contact form through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Basin account through Composio's Basin MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Basin with

- [OpenAI Agents SDK](https://composio.dev/toolkits/basin/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/basin/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/basin/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/basin/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/basin/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/basin/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/basin/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/basin/framework/cli)
- [Google ADK](https://composio.dev/toolkits/basin/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/basin/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/basin/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/basin/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/basin/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 Basin tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Basin 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 Basin 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 Basin MCP server, and what's possible with it?

The Basin MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Basin account. It provides structured and secure access to your forms and projects, so your agent can perform actions like creating forms, managing webhooks, organizing projects, and retrieving domain or form details on your behalf.
- Instant form creation and management: Ask your agent to set up new forms with custom settings, associate them with projects, or delete forms you no longer need—all without manual coding.
- Seamless project organization: Let your agent create new Basin projects to group related forms or delete obsolete projects, keeping your workspace tidy and efficient.
- Automated webhook and integration setup: Have your agent add or remove webhooks for specific forms, so submissions are instantly routed to the right endpoints or external services.
- Detailed form and account insights: Retrieve rich metadata about any form or get a full list of domains linked to your Basin account, helping you monitor and audit your form infrastructure.
- Effortless notification management: Empower your agent to configure notification webhooks, ensuring critical submissions reach your team or external tools in real time.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `BASIN_CREATE_FORM` | Create Form | Tool to create a new form in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection. |
| `BASIN_CREATE_FORM_WEBHOOK` | Create Form Webhook | Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed. |
| `BASIN_CREATE_NOTIFICATION` | Create Notification | Tool to create a new notification webhook. use when you need to forward form submissions to an external service. |
| `BASIN_CREATE_PROJECT` | Create Project | Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads." |
| `BASIN_DELETE_FORM` | Delete Form | Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible. |
| `BASIN_DELETE_INTEGRATION` | Delete Integration | Tool to delete a form webhook integration. use when removing an obsolete integration by id. |
| `BASIN_DELETE_PROJECT` | Delete Project | Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details. |
| `BASIN_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id. |
| `BASIN_GET_DOMAINS` | Get Domains | Tool to retrieve a list of all domains associated with the account. use after authentication when you need to display or verify your configured domains in basin. |
| `BASIN_GET_FORM_DETAILS` | Get Form Details | Tool to retrieve detailed information about a specific form. use when you have a form id and need its metadata. |
| `BASIN_GET_FORMS` | Get Forms | Tool to retrieve a list of all forms. use after authentication to fetch all your forms. |
| `BASIN_GET_PROJECT_DETAILS` | Get Project Details | Tool to retrieve detailed information about a specific project. use when you have a project id and need its metadata (name, created at, updated at). |
| `BASIN_GET_PROJECTS` | Get Projects | Tool to retrieve a list of all projects. use after authentication to fetch your project inventory. |
| `BASIN_GET_SUBMISSIONS` | Get Submissions | Tool to retrieve all submissions for a specific form. use when you need to list entries after obtaining the form id. |
| `BASIN_GET_WEBHOOKS` | Get Webhooks | Tool to retrieve all webhooks associated with a specific form. use after obtaining the form id. |
| `BASIN_UPDATE_INTEGRATION` | Update Integration | Tool to update a form webhook integration. use to modify settings of an existing integration. |
| `BASIN_UPDATE_PROJECT` | Update Project | Tool to update details of an existing project. use when you need to change a project's name after confirming the project id. example: "update project 123 to 'rebrand launch'". |
| `BASIN_UPDATE_WEBHOOK` | Update Webhook | Tool to update settings of an existing webhook for a form. use after obtaining the webhook's id. |

## Supported Triggers

None listed.

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

The Basin MCP server is an implementation of the Model Context Protocol that connects your AI agent to Basin. It provides structured and secure access so your agent can perform Basin 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 Basin 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 Basin

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "basin" for Basin 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: ["basin"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Basin 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 Basin 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: "basin-mastra-agent",
    instructions: "You are an AI agent with Basin 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 Basin 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: {
        basin: 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: ["basin"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "basin-mastra-agent",
    instructions: "You are an AI agent with Basin 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: { basin: 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 Basin 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 Basin MCP Agent with another framework

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

## Related Toolkits

- [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations.
- [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications.
- [Conveyor](https://composio.dev/toolkits/conveyor) - Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.
- [Crowdin](https://composio.dev/toolkits/crowdin) - Crowdin is a localization management platform that streamlines translation workflows and collaboration. It helps teams centralize multilingual content, boost productivity, and automate translation processes.
- [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights.
- [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way.
- [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease.
- [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration.
- [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease.
- [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease.
- [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services.
- [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows.
- [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses.
- [Hyperbrowser](https://composio.dev/toolkits/hyperbrowser) - Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale.
- [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals.
- [Leverly](https://composio.dev/toolkits/leverly) - Leverly is a workflow automation platform that connects and coordinates actions across your apps. It streamlines repetitive processes so your business runs smoother, faster, and with fewer manual steps.
- [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination.
- [Make](https://composio.dev/toolkits/make) - Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code.
- [Ntfy](https://composio.dev/toolkits/ntfy) - Ntfy is a notification service to send push messages to phones or desktops. Instantly deliver alerts and updates to users, devices, or teams.
- [Persona](https://composio.dev/toolkits/persona) - Persona offers identity infrastructure to automate user verification and compliance. It helps organizations securely verify users and reduce fraud risk.

## Frequently Asked Questions

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

With a standalone Basin MCP server, the agents and LLMs can only access a fixed set of Basin tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Basin 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 Basin tools.

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

Yes, absolutely. You can configure which Basin 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 Basin data and credentials are handled as safely as possible.

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