How to integrate Dadata ru MCP with OpenAI Agents SDK

Framework Integration Gradient
Dadata ru Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Dadata ru to the OpenAI Agents SDK 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 OpenAI Agents SDK 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:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Dadata ru
  • Configure an AI agent that can use Dadata ru as a tool
  • Run a live chat session where you can ask the agent to perform Dadata ru operations

What is open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Dadata ru project
  • Some knowledge of Python or Typescript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Dadata ru.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Dadata ru Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["dadata_ru"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only dadata_ru.
  • The router checks the user's Dadata ru connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Dadata ru.
  • This approach keeps things lightweight and lets the agent request Dadata ru tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Dadata ru. "
        "Help users perform Dadata ru operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Dadata ru and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Dadata ru operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Dadata ru.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Dadata ru and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["dadata_ru"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Dadata ru. "
        "Help users perform Dadata ru operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Dadata ru MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Dadata ru.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Dadata ru MCP Agent with another framework

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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.