mcpbeat

List Connections

microsoft/list-connections

Lists Power Platform connections in the current environment. Use when you need a connection ID before adding a connector to a code app.

441 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
601
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/power-platform-skills --skill list-connections

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

4 sections, as written by the author

📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns (Windows CLI compatibility, memory bank, etc.).

List Connections

Lists all Power Platform connections in the current environment using the Power Apps CLI.

Workflow

  • Fetch Connections → 2. Present Results

Step 1: Fetch Connections

> Resolve the CLI first (see cli-binary.md): run as $PA connection list (npx --no-install pa …), never a bare pa. On power-apps-only projects, translate to power-apps list-connections.

pa connection list

If the CLI is not authenticated, it will open a browser for login automatically. Complete the login and retry.

Other failures:

  • Non-zero exit for any reason other than auth: Report the exact output. STOP.
  • No output or empty results: Verify the correct environment ID is set in power.config.json, then retry once.

Step 2: Present Results

Show the connection list to the user. The Connection ID is what goes into -c <connection-id> when adding a data source.

If the needed connector is missing:

  • Share the direct Connections URL using the active environment ID from context (from power.config.json or a prior step): https://make.powerapps.com/environments/<environment-id>/connections → + New connection
  • Search for and create the connector, then complete the sign-in/consent flow
  • Re-run /list-connections to get the new connection ID

How to use it

Copy the folder

Take microsoft/list-connections from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.