How to integrate Dadata ru MCP with LlamaIndex

This guide walks you through connecting Dadata ru to LlamaIndex 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 through natural language commands. This guide will help you understand how to give your LlamaIndex 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.

Dadata ru logoDadata ru
Api Key

Dadata ru is a data validation and enrichment API for Russian addresses, companies, and personal data. It helps automate data entry, reduce errors, and standardize records across your workflows.

63 Tools

Introduction

This guide walks you through connecting Dadata ru to LlamaIndex 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 through natural language commands.

This guide will help you understand how to give your LlamaIndex 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.

Also integrate Dadata ru with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Dadata ru
  • Connect LlamaIndex to the Dadata ru MCP server
  • Build a Dadata ru-powered agent using LlamaIndex
  • Interact with Dadata ru through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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 step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Dadata ru account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Dadata ru

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Dadata ru access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called dadata ru_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["dadata_ru"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Dadata ru actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, dadata ru)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Dadata ru tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Dadata ru
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Dadata ru tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Dadata ru
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Dadata ru, then start asking questions.

Complete Code

Here's the complete code to get you started with Dadata ru and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["dadata_ru"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Dadata ru actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Dadata ru to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Dadata ru tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Clean Address

Clean and standardize a Russian postal address.

Clean Birthdate

Standardize and validate birthdate strings.

Clean Email

Standardize and validate an email address.

Clean Name (FIO)

Tool to standardize and parse full names (FIO), detect gender, and return grammatical cases.

Clean Passport

Tool to validate a Russian passport number against the official registry.

Clean Phone

Tool to standardize and validate phone numbers.

Clean Composite Record

Tool to standardize composite records with multiple contact data fields in a single request.

Clean Vehicle

Standardize and recognize vehicle make/model from free-form text input.

Find Address

Retrieve full Russian address details by FIAS ID, KLADR code, or cadastral number.

Find Bank

Tool to find bank by BIC, SWIFT, INN, or registration number.

Find Car Brand

Find car brand details by identifier.

Find Company By Email

Find companies by corporate email address domain.

Find Country

Tool to find country details by ISO or numeric code.

Find Court by ID

Find court by ID or code.

Find Currency

Tool to find currency details by ISO 4217 code.

Find Delivery City IDs

Retrieves delivery service city identifiers (CDEK, Boxberry, DPD) for a given Russian city by KLADR code or FIAS ID.

Find Address by FIAS ID

Find address by FIAS ID from the Federal Information Address System (FIAS/GAR).

Find FMS Unit

Look up Russian passport issuing authority (FMS unit) by subdivision code.

Find FNS Unit by Code

Find Russian tax inspection (FNS unit) by exact code or INN.

Find FTS Unit

Find a Russian Federal Customs Service (FTS) unit by its 8-digit code.

Find Medical Position By ID

Tool to find medical position by ID code.

Find MKTU

Look up MKTU (International Classification of Goods and Services/Nice Classification) items by their numeric code.

Find OKPD2 by ID

Look up OKPD2 (Russian Classification of Products by Economic Activity) entries by their exact code.

Find OKPDTR Position

Find job position by OKPDTR code.

Find OKPDTR Profession

Tool to find profession details by OKPDTR code.

Find Territory by OKTMO

Find Russian municipal territory by OKTMO code.

Find OKVED2

Look up OKVED2 (Russian Classification of Economic Activities) entries by their exact code.

Find Company or Entrepreneur

Find company or individual entrepreneur details by INN or OGRN from the Russian Federal Tax Service registry.

Find Belarus Party by UNP

Tool to find a Belarusian company or entrepreneur by UNP.

Find Kazakhstan Company by BIN

Look up Kazakhstan company or entrepreneur details by BIN (Business Identification Number).

Find Postal Office

Find Russian postal office details by postal code (index).

Find Postal Unit By ID

Find postal unit by postal code.

Geolocate Address

Tool to find nearest addresses by geographic coordinates.

Geolocate Postal Unit

Tool to find nearest postal units by geographic coordinates.

Get Profile Balance

Tool to retrieve current DaData account balance.

Get Profile Statistics

Tool to get daily aggregated usage statistics per DaData API service.

Get Reference Versions

Tool to retrieve the last update dates for DaData reference datasets (FIAS, EGRUL, banks, etc.

IP Locate Address

Geolocate a Russian IP address to determine its city/region.

Suggest Address

Tool to autocomplete and suggest addresses.

Suggest Bank

Tool to autocomplete and suggest banks by partial details.

Suggest Car Brand

Tool to suggest car brands.

Suggest Country

Tool to suggest countries based on user input.

Suggest Court

Tool to suggest Russian courts by name or location.

Suggest Currency

Tool to suggest currencies by ISO 4217 code or name.

Suggest Email

Tool to autocomplete and suggest email addresses.

Suggest FIAS Address

Tool to suggest addresses from FIAS/GAR database.

Suggest FMS Unit

Tool to autocomplete and suggest passport issuing authorities.

Suggest FNS Unit

Tool to suggest Russian tax inspection units by partial name or code.

Suggest FTS Unit

Tool to autocomplete and suggest Russian customs (FTS) units.

Suggest Medical Position

Tool to autocomplete and suggest medical positions and specialties.

Suggest Metro

Tool to suggest metro stations.

Suggest MKTU

Autocomplete and search for MKTU (Nice Classification) codes used for trademark registration.

Suggest Name

Tool to autocomplete and suggest full names (FIO).

Suggest OKPD2

Tool to autocomplete and suggest Russian product classification codes (OKPD2).

Suggest OKPDTR Position

Tool to autocomplete and suggest Russian job positions from OKPDTR classifier.

Suggest OKPDTR Profession

Tool to autocomplete and suggest professions from OKPDTR classifier.

Suggest OKTMO

Suggest Russian municipal territory codes (OKTMO) by code prefix or partial name.

Suggest OKVED2

Tool to suggest OKVED2 codes by text query.

Suggest Party

Tool to autocomplete and suggest Russian companies or entrepreneurs.

Suggest Belarus Party

Tool to autocomplete and suggest Belarusian companies or entrepreneurs.

Suggest Kazakhstan Company

Tool to autocomplete and suggest Kazakhstan companies or entrepreneurs.

Suggest Postal Office

Suggests Russian Post offices by postal code or address.

Suggest Postal Unit

Suggests Russian Post offices (Почта России) by postal code or address.

FAQ

Frequently asked questions

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.

Yes, you can. LlamaIndex 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.

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.

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.

Start with Dadata ru.It takes 30 seconds.

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

Start building