AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

flowstudio-power-automate-mcp

Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills` / `tool_search`, and oversized-response handling. Load this skill first when connecting an agent to Power Automate. For specialized workflows, load `flowstudio-power-automate-build`, `flowstudio-power-automate-debug`, `flowstudio-power-automate-monitoring` (Pro+), or `flowstudio-power-automate-governance` (Pro+) — each contains the workflow narrative, this skill provides the plumbing they all rely on. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--flowstudio-power-automate-mcp at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 5

references/MCP-BOOTSTRAP.md

MCP Bootstrap — Quick Reference

Everything an agent needs to start calling the FlowStudio MCP server.

Endpoint:  https://mcp.flowstudio.app/mcp
Protocol:  JSON-RPC 2.0 over HTTP POST
Transport: Streamable HTTP — single POST per request, no SSE, no WebSocket
Auth:      x-api-key header with JWT token (NOT Bearer)

Required Headers

Content-Type: application/json
x-api-key: <token>
User-Agent: FlowStudio-MCP/1.0    ← required, or Cloudflare blocks you

Step 1 — Discover Tool Bundles

Preferred cold-start call:

POST {"jsonrpc":"2.0","id":1,"method":"tools/call",
      "params":{"name":"list_skills","arguments":{}}}

Returns the current bundles (build-flow, create-flow, debug-flow, monitor-flow, discover, governance) and their member tool names. Free — not counted against plan limits.

Then load the relevant schemas:

POST {"jsonrpc":"2.0","id":2,"method":"tools/call",
      "params":{"name":"tool_search","arguments":{"query":"skill:create-flow"}}}

Use query:"select:tool1,tool2" to load exact tools and keyword search such as query:"send email" when the user intent is ambiguous.

Fallback for very low-level MCP clients:

POST {"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}

tools/list returns all tools with names, descriptions, and input schemas, but it is heavier and should not be the first choice for agents that know the FlowStudio meta-tools.

Step 2 — Call a Tool

POST {"jsonrpc":"2.0","id":1,"method":"tools/call",
      "params":{"name":"<tool_name>","arguments":{...}}}

Response Shape

Success → {"result":{"content":[{"type":"text","text":"<JSON string>"}]}}
Error   → {"result":{"content":[{"type":"text","text":"{\"error\":{...}}"}]}}

Always parse result.content[0].text as JSON to get the actual data.

Key Tips

  • Tool results are JSON strings inside the text field — double-parse needed
  • "error" field in parsed body: null = success, object = failure
  • environmentName is required for most tools, but not for: list_live_environments, list_live_connections, list_store_flows, list_store_environments, list_store_makers, get_store_maker, list_store_power_apps, list_store_connections
  • When in doubt, check the required array in each tool's schema from tool_search (or tools/list as a fallback)