mirror of
https://github.com/github/awesome-copilot.git
synced 2026-05-15 11:11:48 +00:00
Catherine Han
e67c66c441
* feat(flowstudio): align Power Automate skills with MCP server v1.1.6 Foundation skill (flowstudio-power-automate-mcp) rewritten to use the server's new tool_search and list_skills meta-tools (v1.1.5+) for discovery instead of cataloging every tool by hand. Cut from 519 to 295 lines. New "Which Skill to Use When" intent-keyed decision tree points at the four specialized skills. Build/debug/governance/monitoring updated for use-case framing. Tools that genuinely cross tiers (e.g. debug skill borrowing get_store_flow_summary) are correct when the workflow needs them — the split between skills is by use-case intent, not by tool partition. Build skill: new Step 3a Resolving Dynamic Connector Values covers get_live_dynamic_options outer-parameter auto-bridge (v1.1.6+) and the AadGraph user-picker fallback via shared_office365users.SearchUserV2 (replaces broken builtInOperation:AadGraph.GetUsers). Debug skill: Outlook user-picker failure note pointing at the fallback. Monitoring skill description disambiguates from the server's monitor-flow tool bundle (runtime control of a single flow) — this skill is tenant-wide health analytics over the cached store. All 5 skills validate via npm run skill:validate; line endings LF only; codespell clean; auto-regenerated docs/README.skills.md included. * fix(flowstudio): remove deprecated tool references The v1.1.5 MCP server release marked 5 tools [DEPRECATED] but the previous alignment commit missed them. Replacements per server source: - get_live_flow_http_schema → read trigger.inputs.schema from get_live_flow - get_live_flow_trigger_url → read trigger.metadata.callbackUrl from get_live_flow - get_store_flow_trigger_url → get_store_flow.triggerUrl field - get_store_flow_errors → get_store_flow_runs(status=["Failed"]) - set_store_flow_state → set_live_flow_state Touches build, debug, governance, monitoring SKILL.md and the foundation skill's tool-reference.md. Remaining mentions of the deprecated names are intentional — they live in deprecation notices naming the obsolete wrapper alongside its replacement. * Update FlowStudio Power Automate skills * Cover latest FlowStudio MCP actions * Trim FlowStudio Power Automate skills * Number FlowStudio build workflow steps
79 lines
2.4 KiB
Markdown
79 lines
2.4 KiB
Markdown
# 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:
|
|
|
|
```json
|
|
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:
|
|
|
|
```json
|
|
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:
|
|
|
|
```json
|
|
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
|
|
|
|
```json
|
|
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)
|