This is Part 3 of a series documenting a non-engineer CEO's attempts to connect Copilot Studio to LDX hub's StructFlow API.

Part 1 — It didn't work yet. Part 2 — REST API, 8 errors, 3 hours, finally working.

In Part 2, I got the REST API route working through Power Automate. It took 3 hours and 8 errors. The moment it worked, I immediately wondered: is there a simpler path?

There is. It's called MCP.

Instead of building a Power Automate flow, configuring polling loops, and debugging HTTP connectors — I connected LDX hub's MCP server directly to the Copilot Studio agent. The whole thing took about 2 hours, and most of that was figuring out two non-obvious settings.

Here's the full account.

Environment

Microsoft Copilot Studio (Kawamura International tenant)

LDX hub MCP Server ( https://gw.ldxhub.io/mcp )

Existing agent: Minutes Assistant (議事録アシスタント)

Time required: ~2 hours

Why MCP instead of Power Automate?

The REST API route in Part 2 works.…