How to integrate Esputnik MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Esputnik logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Esputnik to Mastra AI using the Composio tool router. By the end, you'll have a working Esputnik agent that can bulk add 500 new email contacts, delete sms message template with id 123, get status of yesterday's contact import through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Esputnik account through Composio's Esputnik MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Esputnik with

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 Esputnik tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Esputnik 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 Esputnik 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 Esputnik MCP server, and what's possible with it?

The Esputnik MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Esputnik account. It provides structured and secure access to your marketing automation tools, so your agent can perform actions like sending broadcasts, managing contacts, importing data, and handling push notifications on your behalf.

  • Bulk contact import and management: Quickly add or update thousands of contacts at once, check import status, and keep your lists up to date with minimal effort.
  • Broadcast and message control: Retrieve, review, and manage your marketing broadcasts and app inbox messages, ensuring your campaigns run smoothly.
  • Order and transactional data automation: Import and synchronize large batches of order data, keeping your marketing segmentation and triggers accurate and relevant.
  • Push and SMS notification management: Activate or deactivate push tokens, delete outdated SMS templates, and fine-tune your notification workflows directly through your agent.
  • Domain and integration setup: Register domains for web tracking or widgets, helping you expand and customize your communication reach seamlessly.

Supported Tools & Triggers

Tools
Add ContactTool to create or update a single contact in eSputnik in real-time.
Add DomainRegister a domain with eSputnik for web tracking, widgets, or web push notifications.
Add Orders BulkTool to transfer orders in bulk to eSputnik.
Add Unsubscribed EmailsTool to add email addresses to the list of unsubscribed contacts.
Add Web Push DomainTool to add a domain for web push notifications in eSputnik.
Attach Contacts to SegmentTool to attach contacts to a static segment (group) by contact IDs or external customer IDs.
Bulk Add or Update ContactsBulk add or update up to 3000 contacts in eSputnik asynchronously.
Change Mobile Push Token ActivityActivate or deactivate a mobile push notification token in eSputnik.
Create API TokenGenerate a new API token for authentication.
Create App Inbox MessageTool to create a basic App Inbox message in eSputnik.
Create Contacts from FileImport or update contacts from an external file in eSputnik.
Create Email MessageTool to create or update an email message in eSputnik.
Create Mobile Push MessageTool to create a new mobile push notification message in eSputnik.
Create SMS MessageTool to create a basic SMS message template in eSputnik.
Create Telegram MessageCreate a basic Telegram bot message in eSputnik.
Delete App Inbox MessageTool to delete an App Inbox message by its ID from eSputnik.
Delete App Inbox TranslationDelete a language translation of an App Inbox message from eSputnik.
Delete BroadcastTool to cancel a scheduled broadcast campaign.
Delete ContactTool to delete a contact by its Yespo ID.
Delete Contact by External IDDelete a contact from eSputnik using their external customer ID.
Delete Email MessageDelete a basic email message by its ID from eSputnik.
Delete Email TranslationDelete a translation of a base email message from eSputnik.
Delete Mobile Push MessageDelete a base Mobile Push message by its ID from eSputnik.
Delete Mobile Push TranslationDelete a language version of a base Mobile Push message from eSputnik.
Delete OrdersTool to schedule asynchronous deletion of orders in eSputnik.
Delete SMS MessageDelete a base SMS message template by its ID from eSputnik.
Delete SMS TranslationDelete a language version of a base SMS message from eSputnik.
Delete Telegram MessageDelete a base Telegram bot message by its ID from eSputnik.
Delete Telegram TranslationDelete a language version of a Telegram bot message from eSputnik.
Detach Contacts from SegmentTool to delete contacts from a static segment by contact IDs or external customer IDs.
Generate Event V2Tool to send backend events from websites and mobile apps to eSputnik.
Generate Event V3Tool to generate events in eSputnik v3 API.
Generate Past Events V2Tool to transfer past event data from your CRM or data store to eSputnik using v2 API.
Generate Past Events V3Tool to generate past events in eSputnik v3 API.
Get Account InfoRetrieve basic eSputnik account information.
Get App Inbox MessageRetrieves an App Inbox message by its unique identifier from eSputnik.
Get BroadcastsRetrieve a paginated list of broadcast campaigns from eSputnik.
Get ContactRetrieve complete information about a contact by their ID.
Get Contact EmailsTool to retrieve email addresses of contacts by their contact IDs.
Get Contact Import StatusRetrieve the status of a contact import session in eSputnik.
Get Contact Message HistoryRetrieve a contact's message history across multiple channels from eSputnik.
Get ContactsSearch for contacts in eSputnik using various filter criteria.
Get Contact SubscriptionsRetrieve all subscription categories a contact is enrolled in.
Get Email InterfacesTool to retrieve all configured email interfaces (sender names) from eSputnik.
Get Email MessageRetrieves an email message by its unique identifier from eSputnik.
Get Email View LinkGet a link to view an email message in browser from eSputnik.
Get Message StatusRetrieve delivery status for sent messages across all channels (email, SMS, Viber, push).
Get Mobile Push MessageRetrieves a mobile push message by its unique identifier from eSputnik.
Get Organization BalanceRetrieve the current eSputnik organization balance.
Get Organization Billing HistoryRetrieve the organization's billing history from eSputnik, broken down by day and media channel.
Get Preprocessor File StatusRetrieve the status of a preprocessor file upload session.
Get Product Feeds ConfigurationTool to retrieve product feeds configuration from eSputnik.
Get Promocodes CountGet the number of available promotional codes in eSputnik.
Get Site DomainRetrieve the organization's domain configuration from eSputnik.
Get Site Tracking ScriptRetrieve the site tracking script for your eSputnik account.
Get SMS InterfacesRetrieve all SMS interfaces (alpha names) configured for the organization.
Get Subscription CategoriesRetrieve all subscription categories for the organization.
Get Telegram MessageRetrieve a Telegram bot message by its unique identifier from eSputnik.
List Promotional CodesRetrieve a list of promotional codes from eSputnik.
List Web Push DomainsRetrieve the list of domains registered for web push notifications.
Remove From UnsubscribedTool to remove email addresses from the unsubscribed contacts list in eSputnik.
Search App Inbox MessagesSearch for mobile App Inbox messages using a part of the name or a tag.
Search ContactsSearch for all contacts in a segment (group).
Search Email MessagesSearch for email messages using a part of their name or a tag.
Search Mobile Push MessagesSearch for mobile push messages using part of the name or a tag.
Search SegmentsSearch for and retrieve available segments (groups) in eSputnik.
Search SMS MessagesSearch for SMS messages using part of their names or tags in eSputnik.
Search Telegram MessagesSearch for Telegram bot messages using a part of name or a tag.
Search Viber MessagesSearch for Viber messages using part of the name or a tag.
Search WorkflowsSearch for and retrieve available workflows from eSputnik.
Send EmailSend an email message to one or more contacts via eSputnik API.
Send Prepared MessageTool to send a prepared message to one or many contacts.
Subscribe ContactTool to subscribe a contact for double opt-in implementation.
Update App Inbox MessageTool to update the base App Inbox message in eSputnik.
Update App Inbox TranslationTool to update or add a language version for an App Inbox message in eSputnik.
Update ContactTool to update contact information by contact ID.
Update Contact SubscriptionsTool to update the subscription categories a contact is enrolled in.
Update Email MessageTool to update an existing email message in eSputnik.
Update Email TranslationTool to update or add a language version for a base email message in eSputnik.
Update Interaction StatusTool to update the status of a message interaction using interaction_id.
Update Mobile Push MessageTool to update an existing mobile push notification message in eSputnik.
Update Mobile Push TranslationTool to update or add a language version for a mobile push message in eSputnik.
Update Preprocessor File By IDTool to update a preprocessor file's data by providing a new external link.
Update SMS MessageTool to update an existing base SMS message template in eSputnik.
Update SMS TranslationTool to update a language version of an SMS message in eSputnik.
Update Telegram MessageUpdate a base Telegram bot message in eSputnik.
Update Telegram TranslationUpdate a translated telegram bot message in eSputnik.
Upload Preprocessor FileTool to upload a file for the preprocessor from an external repository.
Upload Promotional CodesTool to upload promotional codes to eSputnik in bulk.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

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

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Esputnik through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

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

Import libraries and validate environment

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,
});
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

Create a Tool Router session for Esputnik

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

  const composioMCPUrl = session.mcp.url;
  console.log("Esputnik MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "esputnik" for Esputnik access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

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);
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 Esputnik toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "esputnik-mastra-agent",
    instructions: "You are an AI agent with Esputnik tools via Composio.",
    model: "openai/gpt-5",
  });
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

Set up interactive chat interface

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: {
        esputnik: 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);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Esputnik 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

Complete Code

Here's the complete code to get you started with Esputnik and Mastra AI:

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: ["esputnik"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

FAQ

What are the differences in Tool Router MCP and Esputnik MCP?

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

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.