Connect DataDriven to Microsoft Copilot Studio

Make the DataDriven MCP server available to your Copilot Studio agents through a Power Platform custom connector. This guide is written for IT / Power Platform administrators and takes about 15 minutes.

MCP — streamable HTTP API-key auth (no OAuth setup) Power Platform custom connector
https://api.datadriven.ro/mcp

What you are connecting to

The DataDriven MCP server exposes Romanian public-procurement data — tenders, awards, company information and tender documents — as Model Context Protocol tools your agent can call.

Endpointhttps://api.datadriven.ro/mcp
ProtocolModel Context Protocol — streamable HTTP (mcp-streamable-1.0)
AuthenticationAPI key in HTTP header Ocp-Apim-Subscription-Key
Required planDataDriven Premium with API access enabled
Connector typePower Platform custom connector (API Key)

1. Before you start

A few things to have in place:

  • Generative orchestration must be turned on for the agent — MCP tools only work with generative orchestration enabled (Copilot Studio → your agent → Settings → Generative AI).
  • A DataDriven Premium subscription with API access enabled, and its API key (see step 2).
  • Permission to add tools to the agent. The wizard (step 3) builds the connector for you. The manual file-import path (step 4) additionally needs the Environment Maker role in the target Power Platform environment.
  • If your tenant uses DLP policies, an admin may need to allow the connector — see step 5.
Copilot Studio supports the Streamable HTTP transport. SSE was deprecated and is no longer supported for MCP — the DataDriven server is Streamable HTTP, so you're current.

2. Get the API key

Use the API key, not OAuth. Copilot Studio's MCP wizard supports both, but DataDriven's OAuth flow requires an interactive sign-in by the account owner and isn't suited to an IT-managed connection. The API key is a single static secret you enter once — no OAuth app, redirect URI, or Entra consent required.
A

The API key belongs to your organisation's DataDriven account. The account owner retrieves it once and passes it to IT through your normal secret-sharing channel:

  1. Sign in at datadriven.ro/app → API & MCP
  2. Copy the API key (or Regenerate — note that regenerating invalidates any previous key).

Treat the key as a password — it grants full Premium API access to your account's data.

3. Add the server — MCP onboarding wizard (recommended)

The fastest path. You don't need an OpenAPI file — Copilot Studio creates the underlying custom connector for you from the details below.

A
  1. In Copilot Studio, open your agent → Tools page.
  2. Select Add a tool → New tool → Model Context Protocol. The MCP onboarding wizard opens.
  3. Fill in:
    • Server name: DataDriven
    • Server description: e.g. Romanian public-procurement tenders, awards, company data and tender documents. (The orchestrator uses this to decide when to call the server — keep it clear.)
    • Server URL: https://api.datadriven.ro/mcp
  4. Set Authentication = API key, then:
    • Type: Header
    • Header/parameter name: Ocp-Apim-Subscription-Key
  5. Select Create. On Add tool, choose Create a new connection, paste the API key from step 2, then Add to agent.

4. Alternative — import a custom connector (OpenAPI)

Prefer to manage a versioned connector definition (e.g. inside a Solution)? Use the ready-made OpenAPI file instead of the wizard. Requires the Environment Maker role.

OpenAPI (YAML)

Recommended for the Power Platform custom-connector importer.

ddro-mcp-connector.yaml
OpenAPI (JSON)

Same definition in JSON, if your tooling prefers it.

ddro-mcp-connector.json
A
  1. In Copilot Studio: Tools → Add a tool → New tool → Custom connector (this takes you to Power Apps). Or go directly to make.powerapps.com → Custom connectors, selecting the target environment first.
  2. + New custom connector → Import an OpenAPI file.
  3. Name it DataDriven MCP and select ddro-mcp-connector.yaml → Continue → Create connector. Host, the POST /mcp action (with x-ms-agentic-protocol: mcp-streamable-1.0) and the Ocp-Apim-Subscription-Key API-key security are pre-filled.
  4. Create a connection: on the connector's Test tab → + New connection → paste the API key → save.
  5. Back in Copilot Studio: Tools → Add a tool → Model Context Protocol, pick DataDriven MCP and the connection → Add to agent.

5. Allow the connector in DLP (admin)

Access to MCP servers in Copilot Studio runs through Power Platform connectors, so any Data Loss Prevention policy that governs connectors also governs this MCP server. A new connector reaching an external host is often blocked by default. A Power Platform admin must place DataDriven MCP in the Business group (or a group usable with your other agent connectors): Power Platform admin center → Policies → Data policies → edit the policy for the environment → move the connector → Save. Symptom if skipped: the tool appears but calls fail with a policy/blocked error.

6. Use the tools in your agent

A

Once added, Copilot Studio discovers the server's tools automatically (tender lookup, awards search, company data, tender documents, …) and keeps them in sync if the server changes. All tools are on by default — use the per-tool toggles to disable any you don't need. Save / Publish the agent, and it can call DataDriven to answer procurement questions.

Troubleshooting

SymptomLikely causeFix
MCP tools never get called / no Model Context Protocol optionGenerative orchestration is offTurn on generative orchestration (agent → Settings → Generative AI).
401 unauthenticatedWrong/empty key, or wrong headerRe-check the connection; header must be Ocp-Apim-Subscription-Key. Re-copy the key.
401 … must transit api.datadriven.roHost is not api.datadriven.roFix the connector Host.
Connector/tool blocked at runtimeDLP policyComplete step 5.
Cannot create the connectorMissing Environment Maker roleGrant the role, or have an admin create it.
403 access_deniedSubscription/plan not activeConfirm the DataDriven Premium subscription is active.

Need a hand?

See the full API & MCP overview, or reach the team for help with keys, plans or onboarding.

API & MCP overview Technical documentation Contact the team