Add Data Source
Wire SharePoint, Dataverse, SQL, or API connectors into a Power Apps canvas app when the agent cannot add connections programmatically.
Overview
Add Data Source is an agent skill for the Build phase that guides you to add canvas app data sources and connectors in Power Apps Studio, then verifies them via MCP.
Install
npx skills add https://github.com/microsoft/power-platform-skills --skill add-data-sourceWhat is this skill?
- Routes list-vs-add requests: use list_data_sources or list_apis instead of this skill when only inventory is needed
- Phase 0 maps request type to verification via list_data_sources, list_apis, get_data_source_schema, or describe_api
- Explicitly states connections cannot be added by the coding agent—only through Power Apps Studio
- Post-Studio verification through canvas-authoring MCP tools before continuing pending app work
- Covers SharePoint, Dataverse, SQL, Excel, OneDrive, Teams, Office 365, and custom connectors
- Phase 0 verification matrix maps data sources to list_data_sources and APIs to list_apis
Adoption & trust: 68 installs on skills.sh; 349 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent can edit canvas logic but cannot attach new SharePoint, Dataverse, or API connections without you adding them in Studio first.
Who is it for?
Solo builders pairing Claude or Cursor with Power Apps MCP who are mid-build and need a new connector without guessing verification steps.
Skip if: Listing or describing existing data sources and APIs—invoke list_data_sources or list_apis directly instead.
When should I use this skill?
User asks to add a data source, connection, API, or connector (SharePoint, Dataverse, SQL, Excel, OneDrive, Teams, Office 365, etc.); not when listing existing sources.
What do I get? / Deliverables
You complete the Studio connection flow, the skill confirms the source or API is visible to the agent, and implementation work can resume on a verified integration.
- Studio steps for the requested connection type
- MCP-verified confirmation that the new source or API is available to the app
Recommended Skills
Journey fit
How it compares
Use for human-in-the-loop Studio wiring plus MCP verification, not as a substitute for built-in list or schema MCP calls.
Common Questions / FAQ
Who is add-data-source for?
Power Apps builders using an AI coding agent with canvas-authoring MCP who need to attach a new data source or connector the agent cannot create alone.
When should I use add-data-source?
During Build integrations when you ask to add a connection, API, or connector to SharePoint, Dataverse, SQL, Excel, OneDrive, Teams, or Office 365; not when you only want an inventory of what is already connected.
Is add-data-source safe to install?
It is a procedural guide plus MCP read/list verification tools; review the Security Audits panel on this Prism page and your org’s Power Platform policies before granting MCP access to production tenants.
SKILL.md
READMESKILL.md - Add Data Source
Data sources, connections, and API connectors cannot be added by the coding agent — they must be added through the Power Apps Studio interface. This skill informs the user, guides them to add the connection in their Studio session, verifies it is available via the MCP server, and then continues with any pending work. ## Phase 0 — Identify the Connection Type From the user's request, determine what they want to add and how to verify it: | Request type | Verify with | |---|---| | Data source (SharePoint list, Dataverse table, SQL table, Excel file, OneDrive, etc.) | `list_data_sources` | | API / connector (Office 365 Users, Teams, custom connector, etc.) | `list_apis` | | Unclear | Both `list_data_sources` and `list_apis` | Note what the user is trying to add so you can look for it by name in Phase 3. ## Phase 1 — Inform the User Explain that this step requires action in their Studio session. Tell the user: - The coding agent cannot add data sources or connections programmatically — this must be done directly in Power Apps Studio. - To add the connection, follow these steps in their open Studio session: 1. Open the **Data** panel in the left sidebar 2. Click **Add data** 3. Search for the data source or connector they want (e.g., "SharePoint", "Dataverse", "SQL Server", "Office 365 Users") 4. Follow the authentication prompts and select the specific table, list, file, or dataset - Once added, the connection will be available to the MCP server and you can continue. ## Phase 2 — Wait for Confirmation Use `AskUserQuestion` to pause until the user has completed the steps in Studio: > "Please add the data source or connection in your Power Apps Studio session. Reply here when it's ready and I'll verify the connection before continuing." Do not proceed until the user confirms they have added it. ## Phase 3 — Verify the Connection Once the user confirms, call the appropriate MCP tools to check that the connection is now available: - If the request was for a **data source**: call `list_data_sources` - If the request was for an **API / connector**: call `list_apis` - If the type was unclear: call both in parallel Scan the results for the connection the user added: **Found** — Confirm to the user that the data source or connection is now visible to the agent. Include the exact name as returned by the MCP tool (this is how it must be referenced in Power Fx formulas). If it is a data source, call `get_data_source_schema` to retrieve its column names and types, and include the schema summary in your response so it is ready for use in edits. Similarly, for APIs/connectors, call `describe_api` to retrieve the available endpoints and their parameters, and include the schema summary in your response. **Not found** — Inform the user that the connection is not yet visible. Ask them to: 1. Confirm they completed the Studio steps and the connection appears in the Data panel there. 2. Check that their Studio session is still active (the MCP server must be connected to a live coauthoring session). 3. Let you know when ready to try again. Use `AskUserQuestion` to wait for their follow-up, then re-run Phase 3. ## Phase 4 — Continue After th