How to Connect DaData to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → DaData, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

DaData + Microsoft Copilot

Suggest and look up Russian addresses, companies and sole proprietors by INN or OGRN (ЕГРЮЛ/ЕГРИП), banks by BIC, full names and emails, reverse geocode coordinates, find the city of an IP and search Russian reference lists with DaData. Optional paid standardisation of addresses, phones and names, switched off until you allow it.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

DADATA_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a DaData account: the free plan includes 10,000 suggestion and lookup requests a day.

1. Sign up at dadata.ru and open Профиль → API-ключи (Profile, API keys).
2. Copy the Ключ API (API key), 40 hexadecimal characters, into DADATA_API_KEY. Paste the key alone, without the word Token or spaces: the connector adds the Authorization: Token header itself.
3. Optional: copy the Секретный ключ (secret key) from the same page into DADATA_SECRET_KEY. Everything works without it except dadata_get_balance, dadata_get_daily_stats and dadata_clean.
4. Install the connector and run dadata_find_party with the INN 7707083893: it returns that company's ЕГРЮЛ record and costs nothing within the daily limit.

What it reads: address suggestions from free text, with postal code, FIAS/GAR and KLADR ids, OKATO/OKTMO, tax office, coordinates and time zone; one address by FIAS/GAR id, KLADR code or cadastral number; the addresses nearest to a pair of coordinates; the city of an IP address in Russia; companies and sole proprietors from ЕГРЮЛ/ЕГРИП by name, INN, OGRN, address or director, with KPP, OKVED, director, status and registration and liquidation dates; banks by name, BIC, SWIFT or INN, with the correspondent account; full names (ФИО) split into surname, first name and patronymic with the gender; email completion; and DaData's reference lists: passport issuing offices by code, post offices, tax and customs offices, courts, metro stations, car brands, countries, currencies, OKVED2, OKPD2, OKTMO and MKTU classes.

Your plan decides the details: suggestions and lookups are part of your DaData subscription. Paid plans add data fields such as finances and more company details. dadata_find_affiliated, which finds the companies where a person or company is a founder or manager, needs the Maximum plan; other plans answer 403.

How the answers work: for a company by INN the AI asks for the head office (branch_type MAIN) unless you want the branches too; for a company name it suggests first and then looks up the INN it found. Company dates arrive as Unix milliseconds and the AI turns them into normal dates. Address suggestions cover Russia; for Belarus, Kazakhstan, Uzbekistan and other countries the AI widens the search with locations. Email completion does not check that a mailbox exists, and IP lookups only know Russian addresses.

Asks before every paid call: no tool changes anything in your DaData account. The one tool that costs money is the standardisation: before each call the AI checks the balance with dadata_get_balance, tells you how many values will be cleaned and what that will cost, and waits for your yes.

Switched off at install: dadata_clean (Стандартизация). It standardises and checks raw addresses, phones, names, emails, passports, birthdates and vehicles, and DaData charges every value to the account balance on every plan. It needs DADATA_SECRET_KEY, takes up to 50 values per call and is never run in a loop. An administrator turns it on deliberately.

Limits: the free plan includes 10,000 requests a day, and DaData accepts about 30 requests a second. dadata_get_daily_stats shows how much of today's limit is used.

Common errors: 403 with "Feature ... disabled for token" means the API key is wrong or the service is not on your plan: copy the key again from Профиль → API-ключи. 401 on the balance, the statistics or the standardisation means the secret key is missing or wrong. 429 means the rate or the daily limit was reached: wait, or check the usage.

The connector does not top up your balance, change your plan or keys, or confirm that an email mailbox really exists.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the DaData tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Look up the company with INN 7707083893: is it active, who is the director, and what is its legal address and main OKVED code?"
• "Is our supplier Romashka LLC from Kazan still active? Give me its INN, KPP and OGRN."
• "Find the bank with BIC 044525225 and give me its correspondent account and address."
• "Turn this into a full address with postal code and FIAS id: moscow sukhonskaya 11 apt 89."
• "How many DaData requests have we used today, and what is left on the balance?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse