MCP Server Connector Certification – Unable to Create Test Flow with Custom Connector Actions

(0) Share

Report

Posted on by IV-07041135-0

Hello,
I am currently working on MCP Server Connector certification and following the steps outlined in the official documentation:https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#step-4-prepare-the-connector-and-related-artifacts

According to Step 4, I need to create a Test Flow for my custom connector. I attempted to create a cloud flow with a manual trigger (Solution → New → Automation → Cloud Flow → Instant), then added my custom connector (MCP Server). However, no actions are available for selection:

I also attempted to proceed without this step, but the package structure validation failed with the following error:

Flow solution should contain both 'Connector' and 'Workflows' folders.

Questions:
1. How should the test flow be properly implemented for an MCP Server Connector?
2. Are there any specific requirements or considerations for MCP certification that differ from standard custom connector certification?

Any guidance or documentation references would be greatly appreciated.

Thank you.

Categories:

Model context protocol

Publish & channel management

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Sunil Kumar Pashikanti

1,681 Moderator on at

Like (0)

Report

Copy link

Link copied!

Hi @IV-07041135-0,

MCP Server Connectors are not classic Power Platform connectors. Their actions are:

Invoked by Copilot / agents
Exposed via MCP protocol, not Power Automate
Not selectable in Flow designer

Because of that:

The Flow designer shows no actions
This is by design
Certification still requires a Workflows folder, so a placeholder flow is needed

This behavior is expected and correct for MCP Server Connectors
MCP connectors do not expose Power Automate actions, so no actions will appear in a flow
The required test flow is a structural (empty) flow, not a functional one
The goal is to satisfy solution packaging requirements, not to execute MCP actions
In short: You must include an “empty” instant cloud flow (manual trigger only) in the same solution as the MCP connector.

Questions:
1. How should the test flow be properly implemented for an MCP Server Connector?

Follow these exact steps:

Open Solutions
Select the solution that contains your MCP Server Connector
Create a new flow:
1. New > Automation > Cloud Flow > Instant
2. Use Manually trigger a flow
Do NOT add any actions
Save the flow
Ensure:
1. The flow is part of the same solution
2. The solution now contains:
  1. /Connector
  2. /Workflows

This satisfies certification requirements. The test flow is only for packaging validation, not execution.

2. Are there any specific requirements or considerations for MCP certification that differ from standard custom connector certification?

Area	Standard Custom Connector	MCP Server Connector
Actions in Flow designer	Yes	No
Test flow contains actions	Yes	No
Required Workflows folder	Yes	Yes (empty flow accepted)
Execution context	Power Automate	Copilot / Agent runtime

MCP connectors are validated structurally, not functionally, at the flow level.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No

IV-07041135-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, I tried steps you suggested, but got this error:

Should at least contain one trigger and one action

Was this reply helpful? Yes No