Connect LiveDune to Microsoft Copilot via MCP

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

LiveDune + Microsoft Copilot

LiveDune social media analytics: tracked Instagram, VK, Telegram, YouTube, TikTok and other accounts, period analytics and daily history, posts, stories and videos with their metrics, audience demographics, any public account by URL, plan quota, and autoposting (writes installed switched off).

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:

LIVEDUNE_ACCESS_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a LiveDune account whose plan or API package includes API access.

1. In LiveDune open Settings, API (pro.livedune.com/settings/api) and copy the API token. Whether you have API access depends on your plan or on an API package.
2. Paste the token into LIVEDUNE_ACCESS_TOKEN: only the token, without spaces.
3. Install the connector and run livedune_get_tariff_info to check the connection. It shows how many requests are left and the history window your plan allows, and it does not count against your quota.

One token, sent with every call: AnythingMCP passes the token to https://api.livedune.com as the access_token query parameter. Cloud and self-hosted work the same way: there is nothing else to set up.

Where to start: livedune_list_accounts gives each account on your dashboard its id, which the other tools take as accountId. For an account that is not on your dashboard, such as a competitor, livedune_search_account with its URL returns an id, or a temporary UUID, to use the same way. livedune_list_projects and livedune_list_tags show how your accounts are grouped.

Request quota: every call except livedune_get_tariff_info counts against the API request quota of your plan, and livedune_search_account on a new account also starts a fast analysis of it. One call for a whole period costs less than many single-day calls.

Full metrics need a linked account: reach, impressions, stories and demographics need an account linked to LiveDune (is_linked true); other accounts have public figures only. Some metrics are empty depending on the network. Audience demographics cover Instagram, Threads, VK and OK accounts; videos cover VK and your own Facebook accounts; stories cover VK, Instagram and Telegram, and Telegram works without a linked account.

Dates and paging: dates are YYYY-MM-DD and must lie in the history window of your plan. Lists return at most 100 items with count and after; the AI passes after to get the next page, until it is missing or 0.

Common errors: 401 or 403 means a wrong or expired token, or no API access on your plan. 400 is a mistake in the request, explained in the message LiveDune returns. 404 is an unknown account or post. 429 means the request quota is used up: livedune_get_tariff_info shows what is left.

What it reads: your plan, its request quota and history window; the projects, tags and tracked accounts of your dashboard on Instagram, VK, Telegram, YouTube, TikTok, Dzen, OK, Facebook, X and MAX; for each account the totals of a period (followers and their change, posts, likes, comments, reposts, views and the engagement rates er and erv) and the same figures day by day; the audience by gender and age; posts, stories and videos with their reactions, reach and impressions; the autoposting posts not yet published; and any public account found by its URL.

Switched off at install: livedune_add_account, livedune_remove_account, livedune_create_scheduled_post, livedune_update_scheduled_post and livedune_delete_scheduled_post. They add an account to your dashboard, which uses one of the account slots of your plan; remove an account for good, which stops its statistics; and create, change or delete autoposting posts. A scheduled post is published to the social network on its own at its time. Switch on only the ones you need on the connector page; the AI asks you to confirm every change first. livedune_create_tag is switched on: it only creates a dashboard tag to group accounts.

Not covered: uploading media files (autoposting takes the URL of an image or video that is already online) and LiveDune's other modules, such as direct messages and the competitor reports in the LiveDune interface.

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 LiveDune 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

• "Compare followers, views and engagement rate of all my accounts for October."
• "Which posts of my VK group had the most reach in the last 30 days?"
• "Show me the age and gender split of my Instagram audience."
• "Analyse instagram.com/livedune: how did its followers and engagement change over the last month?"
• "Which posts are queued in autoposting for my Instagram account, and when do they go out?"

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