How to integrate Dadata ru MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Dadata ru Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Dadata ru to Mastra AI using the Composio tool router. By the end, you'll have a working Dadata ru agent that can clean and standardize this russian address, validate and parse a user's full name, check if this passport number is valid, get full bank details from a bic code through natural language commands.

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

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

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

The Dadata ru MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dadata ru account. It provides structured and secure access to DaData’s powerful data validation and enrichment APIs, so your agent can perform actions like standardizing addresses, cleaning contact details, parsing names, and retrieving company or bank information on your behalf.

  • Accurate address standardization and parsing: Instantly clean and structure messy Russian addresses or retrieve address details using identifiers like cadastral numbers or FIAS IDs.
  • Email, phone, and passport validation: Let your agent validate and clean raw email addresses, phone numbers, or Russian passport numbers to ensure your data is correct and safe to use.
  • Full name parsing and gender detection: Automatically break down full names (FIO), identify gender, and get grammatical declensions to power advanced personalization or document processing.
  • Vehicle and car brand data enrichment: Extract structured vehicle details and fetch comprehensive car brand information by code for registration or verification workflows.
  • Bank information retrieval: Quickly find complete bank details by BIC, SWIFT, INN, or registration numbers, streamlining financial processes and verifications.

Supported Tools & Triggers

Tools
Clean AddressTool to clean and standardize russian postal addresses.
Clean BirthdateTool to standardize and validate birthdate strings.
Clean EmailTool to standardize and validate email addresses.
Clean Name (FIO)Tool to standardize and parse full names (fio), detect gender, and return grammatical cases.
Clean PassportTool to validate a russian passport number against the official registry.
Clean PhoneTool to standardize and validate phone numbers.
Clean VehicleTool to standardize and parse vehicle data fields.
Find AddressTool to find address by identifier.
Find BankTool to find bank by bic, swift, inn, or registration number.
Find Car BrandTool to find car brand by its identifier.
Find CountryTool to find country details by iso or numeric code.
Find CurrencyTool to find currency details by iso 4217 code.
Find Delivery City IDsTool to get delivery service city ids by kladr code.
Find FMS UnitTool to find passport authority (fms unit) by code.
Find FTS UnitTool to find customs (fts) office by code.
Find MKTUTool to find mktu classification details by code.
Find OKVED2Tool to find okved2 classifier entries by code.
Find Company or EntrepreneurTool to find company or individual entrepreneur details by inn, ogrn, or kpp.
Find Belarus Party by UNPTool to find a belarusian company or entrepreneur by unp.
Find Kazakhstan Company by BINTool to find kazakhstan company or entrepreneur details by bin or name.
Geolocate AddressTool to find nearest addresses by geographic coordinates.
Get Profile BalanceTool to retrieve current dadata account balance.
Get Profile StatisticsTool to get daily aggregated usage statistics per dadata api service.
Get Reference VersionsTool to retrieve the last update dates for dadata reference datasets (fias, egrul, banks, etc.
IP Locate AddressTool to determine russian address by ip.
Suggest AddressTool to autocomplete and suggest addresses.
Suggest BankTool to autocomplete and suggest banks by partial details.
Suggest Car BrandTool to suggest car brands.
Suggest CourtTool to suggest russian courts by name or location.
Suggest CurrencyTool to suggest currencies by iso 4217 code or name.
Suggest EmailTool to autocomplete and suggest email addresses.
Suggest FMS UnitTool to autocomplete and suggest passport issuing authorities.
Suggest FNS UnitTool to suggest russian tax inspection units by partial name or code.
Suggest FTS UnitTool to autocomplete and suggest russian customs (fts) units.
Suggest MetroTool to suggest metro stations.
Suggest MKTUTool to suggest mktu entries.
Suggest NameTool to autocomplete and suggest full names (fio).
Suggest OKPD2Tool to autocomplete and suggest russian product classification codes (okpd2).
Suggest OKTMOTool to suggest russian municipal territory codes (oktmo).
Suggest OKVED2Tool to suggest okved2 codes by text query.
Suggest PartyTool to autocomplete and suggest russian companies or entrepreneurs.
Suggest Postal UnitTool to suggest russian postal units by index or coordinates.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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 Dadata ru 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 Dadata ru

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

  const composioMCPUrl = session.mcp.url;
  console.log("Dadata ru MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "dadata_ru" for Dadata ru 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 Dadata ru toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "dadata_ru-mastra-agent",
    instructions: "You are an AI agent with Dadata ru 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: {
        dadata_ru: 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 Dadata ru 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 Dadata ru 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: ["dadata_ru"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

OpenAI Agents SDK

OpenAI Agents SDK

Use Dadata ru MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Dadata ru MCP with Claude Agent SDK

Google ADK

Google ADK

Use Dadata ru MCP with Google ADK

LangChain

LangChain

Use Dadata ru MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Dadata ru MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Dadata ru MCP with LlamaIndex

CrewAI

CrewAI

Use Dadata ru MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Dadata ru MCP?

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

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

Yes, absolutely. You can configure which Dadata ru 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 Dadata ru 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.

Book a call↗Get started for free