SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Enigma MCP with Mastra AI

Connect Mastra AI to Enigma MCP. Verify the legitimacy of acme corp in delaware, check if a business is on any u.s. sanctions list, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Enigma logoEnigma
Api Key

Enigma provides trusted data on U.S. businesses, including identity, firmographics, and financial health. It helps sales, marketing, and risk teams make smarter, faster decisions.

19 Tools

Introduction

This guide walks you through connecting Enigma to Mastra AI using the Composio tool router. By the end, you'll have a working Enigma agent that can verify businesses with KYB, screen against sanctions and watchlists, match business profiles, search entities with GraphQL, and manage lists through natural language commands.

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

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

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Enigma with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKLlamaIndexCrewAIPydantic AIAutoGen

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

The Enigma MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Enigma account. It provides structured and secure access to comprehensive U.S. business data, so your agent can perform actions like verifying company identities, screening for compliance, and assessing financial health automatically.

  • Automated KYB business verification: Rapidly verify the legitimacy of U.S. businesses by checking official state records, brands, and legal entities through your agent.
  • Sanctions and watchlist screening: Instantly screen businesses and transactions against up-to-date sanctions and watchlists for enhanced compliance and risk mitigation.
  • Retrieve detailed business intelligence: Access comprehensive profiles on businesses, including best match results, affiliated brands, and entity structures.
  • Compliance automation: Let your agent independently run verification checks and screenings to streamline onboarding, due diligence, and regulatory workflows.

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

Step by step09 STEPS
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
2

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 Enigma through MCP.
3

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
4

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
5

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
6

Create a Tool Router session for Enigma

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

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

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 Enigma toolkit
8

Create the Mastra agent

typescript
const agent = new Agent({
    name: "enigma-mastra-agent",
    instructions: "You are an AI agent with Enigma 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
9

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "enigma-mastra-agent",
    instructions: "You are an AI agent with Enigma 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: { enigma: 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 Enigma 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
TOOLS

Supported Tools

Every Enigma action and event your agent gets out of the box.

Create List

Tool to create a new list to organize and group entities in Enigma.

Create Suggestion

Tool to create a suggestion for data correction, enhancement, or analysis feedback in Enigma.

Delete List

Tool to delete an existing list permanently from the system.

Get Account Information

Tool to retrieve information about the current API account via GraphQL.

Get Aggregate Counts

Get aggregate counts of operating locations and their associated brands or legal entities.

Get Attribute Groups

Tool to retrieve attribute groups for Enigma entity types.

Get Background Task Status

Tool to get the status and results of a background task by ID.

Get Business by Enigma ID

Tool to retrieve detailed business information using an Enigma ID.

Get Screening Decision

Tool to retrieve a screening decision by its request ID.

Get Extended GraphQL Schema

Tool to retrieve extended schema information for Enigma's GraphQL API.

Get List Materialization

Retrieve a list materialization by ID, including its status, progress, and results location when available.

Get Sanctioned Entity Details

Retrieve information about a specific OFAC sanctioned entity by collection and record ID.

KYB Business Verification

Perform a Know Your Business (KYB) check on a US business using Enigma's legal entity data.

List Screening Decisions

Tool to retrieve multiple screening decisions with pagination and filtering options.

Match Business Profile

Tool to match business records against Enigma's SMB data asset using fuzzy matching on business name and location.

Screen Against Sanctions and Watchlists

A tool to screen customers and transactions against sanctions and other watchlists.

Search Enigma Entities via GraphQL

Search Enigma for brands, operating locations, or legal entities by name, phone, website, or TIN, optionally narrowed by address.

Search User-Created Lists

Tool to search and retrieve user-created lists via GraphQL.

Verify Business Identity (KYB v2)

Verify business identity using Enigma's KYB v2 endpoint for compliance or risk assessment.

FRAMEWORKS

How to build Enigma MCP Agent with another framework

Claude Code logo

Claude Code

Use Enigma MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Enigma MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Enigma MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Enigma MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Enigma MCP with Grok Bot

Codex logo

Codex

Use Enigma MCP with Codex

OpenClaw logo

OpenClaw

Use Enigma MCP with OpenClaw

Hermes logo

Hermes

Use Enigma MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Enigma MCP with Atomic Agent

Google ADK logo

Google ADK

Use Enigma MCP with Google ADK

LangChain logo

LangChain

Use Enigma MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Enigma MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Enigma MCP with LlamaIndex

CrewAI logo

CrewAI

Use Enigma MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Enigma MCP with Pydantic AI

AutoGen logo

AutoGen

Use Enigma MCP with AutoGen

FAQ

Frequently asked questions

Start with Enigma.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Enigma tool your agent needs.Free to start.

Start building