MULTI-APP TOOLKIT
Build with GitLab + Microsoft Power BI
- Multi-app
- One MCP session
- 43 actions
- 13 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitLab and Microsoft Power BI tool at once — connect once, list tools, and call them like any single-app session.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "gitlab,microsoft_power_bi",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: GitLab and Microsoft Power BI tools arrive
// together, each keyed by its own app's slug.
// e.g. run Approve Merge Request:
const result = await mcp.callTool({
name: "gitlab-approve-merge-request",
arguments: {
projectId: "Project",
mergeRequestIid: 10,
},
})import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [gitlabTools, microsoftPowerBiTools] =
await Promise.all([
pd.components.list({ app: "gitlab" }),
pd.components.list({ app: "microsoft_power_bi" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=gitlab" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=microsoft_power_bi" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
GitLab
Connected account
Microsoft Power BI
Connected account
TOOLS
GitLab tools
The GitLab tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 28
-
Approve Merge Request
actionApprove a merge request as the authenticated user, or withdraw an earlier approval by setting Action tounapprove. Call Get Merge Request first to check the merge request is actually ready — itsreadinessrollup reports the pipeline status, conflicts and how many approvals are still required — and Get Merge Request Diffs to read the changes being approved. Two things commonly go wrong: GitLab refuses to let you approve your own merge request, and a project may require approval from a specific approval rule that the authenticated user does not satisfy; both surface as a401. To approve as part of leaving review feedback in one step, use Create Merge Request Review with its Action set toapproveinstead. Optionally pass SHA to make the approval conditional on the merge request's head commit, so it fails rather than silently approving work that was pushed after you read the diff. See the documentationWritev0.0.1 -
Create Branch
actionCreate a new branch in the repository. See the documentationWritev0.3.4 -
Create Epic
actionCreates a new epic. See the documentationWritev0.0.6 -
Create issue
actionCreates a new issue. See the documentationWritev0.2.4 -
Create Merge Request
actionOpen a new merge request from one branch into another. Use this for "open an MR", "raise a merge request", "submit my branch for review". Both branches must already exist in the project — use List Repo Branches to check, or Create Branch to make one. Reviewers and assignees are given as usernames and resolved to IDs automatically; a username that is not a member of the project is rejected rather than silently dropped. Set Draft totruefor work that is not ready for review — GitLab expresses this by prefixing the title withDraft:, which this action does for you and which blocks merging until removed. After creating, use Get Merge Request to check its pipeline and merge readiness. See the documentationWritev0.0.1 -
Create Merge Request Comment
actionPost a comment on a merge request. It works in three modes, chosen by which props you set: leave File Path and Discussion ID blank for a plain comment on the merge request as a whole; set File Path plus a line number to open an inline thread anchored to that line of the diff; or set Discussion ID to reply inside an existing thread. Use Get Merge Request Diffs first to get valid file paths and line numbers, and List Merge Request Discussions to get a Discussion ID to reply to. Line numbers follow GitLab's diff rules: for a line the merge request adds or leaves unchanged, pass New Line; for a line it removes, pass Old Line; for an unchanged context line, pass both. Getting that wrong is the usual cause of a rejected inline comment. To post several review comments at once, and optionally approve in the same step, use Create Merge Request Review instead. See the documentationWritev0.0.1 -
Create Merge Request Review
actionSubmit a whole review on a merge request in one step: any number of inline comments anchored to lines of the diff, an overall summary comment, and optionally an approval. This is the tool for "review this MR" — call Get Merge Request and Get Merge Request Diffs first to read the changes, then send the findings back here. GitLab has no single submit-review API, so this action posts each inline comment as its own thread and then approves if asked; if an individual comment is rejected (usually a line that is not part of the diff) the rest are still posted and the failures are returned infailed, so check that array rather than assuming everything landed. Line numbers follow GitLab's diff rules:new_linefor a line the merge request adds,old_linefor a line it removes, both for an unchanged context line. There is no REST equivalent of GitLab's Request changes state — to block a merge request, leave the findings as comments and do not approve. See the documentationWritev0.0.1 -
Get Issue
actionGets a single issue from repository. See the documentationRead-onlyv0.2.4
Triggers top 4 of 10
-
New Commit (Instant)
triggerEmit new event when a new commit is pushed to a branchInstantv0.1.4 -
New Branch (Instant)
triggerEmit new event when a new branch is createdInstantv0.1.3 -
New Project
triggerEmit new event when a project (i.e. repository) is createdv0.1.4 -
New Audit Event (Instant)
triggerEmit new event when a new audit event is createdInstantv0.1.4
TOOLS
Microsoft Power BI tools
The Microsoft Power BI tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 15
-
Add Rows to Dataset Table
actionAdds new data rows to the specified table within the specified dataset from My workspace. See the documentationWritev0.0.6 -
Add Rows To Push Dataset
actionAppend rows to a table in a Power BI Push Dataset (streaming / realtime data). Only works for datasets created via the REST API withdefaultMode: Push— these datasets exposeaddRowsAPIEnabled: trueon the object returned by List Datasets. Use List Datasets first to resolve a dataset name →datasetIdand inspect itstablesfor the exacttableName(case-sensitive). PassworkspaceId(from List Workspaces) orworkspaceNameto target a specific workspace, or omit both for My workspace. Rows must match the table's column schema.rowsaccepts either a JSON array ([{...}, {...}]) or a JSON-stringified array. Each row is an object ofcolumnName → value. Common mistakes: (1) case mismatch ontableNamereturns 404 — copy the exact string from the dataset'stablesarray. (2) Sending values that don't match the declared column data type returnsRequestedResourceNotFoundorDMTS_DatasourceHasNoCredentialsError. Push-dataset rows have no individual IDs and cannot be updated or deleted — only appended or bulk-cleared. See the documentationWritev0.0.3 -
Cancel Dataset Refresh
actionCancels a refresh operation for a specified dataset in Power BI. See the documentationWritev0.0.5 -
Create Dataset
actionCreates a new Push Dataset in Power BI. See the documentationWritev0.0.4 -
Execute DAX Query
actionExecute a DAX (Data Analysis Expressions) query against a Power BI dataset (semantic model). This is the primary analytics tool — use it to answer questions about values, aggregates, or filtered rows in a dataset. Use List Datasets first to resolve a dataset name →datasetId. The query must be a single valid DAX expression starting withEVALUATE. Table discovery (standard datasets): For datasets published from Power BI Desktop, the RESTGET /datasets/{id}/tablesendpoint is scoped to push datasets only and will not list tables. UseEVALUATE INFO.TABLES()instead — it returns every table name in the semantic model. Typical agent flow: List Workspaces → List Datasets → Execute DAX Query (EVALUATE INFO.TABLES()) → Execute DAX Query (EVALUATE 'TableName'). Common patterns: • Discover all tables —EVALUATE INFO.TABLES()(use this before querying an unknown dataset) • List all rows of a table —EVALUATE 'Species'• Filter —EVALUATE FILTER('Species', 'Species'[dietType] = "Carnivore")• Top N by column —EVALUATE TOPN(5, 'Species', 'Species'[weightKg], DESC)• Aggregate single value —EVALUATE ROW("Total", SUMX('Species', 'Species'[weightKg]))• Peek at a table's columns —EVALUATE TOPN(0, 'Species')(returns an empty rowset with column names in the response). Limits: max 100,000 rows or 1,000,000 values per query, andDEFINE/multiple-statement queries are not supported via REST. The tenant must have 'Dataset Execute Queries REST API' enabled (admin setting) or the call returns 401/403. PassworkspaceId(from List Workspaces) orworkspaceNameto target a specific workspace, or omit both for My workspace. See the documentationRead-onlyv0.0.4 -
Export Report
actionExport a Power BI report to a file format such as PDF, PPTX, or PNG. Requires a report ID (use List Reports to find it) and defaults to PDF if no format is given. PassworkspaceId(from List Workspaces) orworkspaceNameto target a specific workspace, or omit both for My workspace. Supportedformatvalues depend on the report type: Power BI reports supportPDF,PPTX,PNG. Paginated reports additionally supportCSV,XLSX,DOCX,XML,MHTML. This API is Premium-only: requires the workspace to be backed by Premium capacity, Premium Per User, or Embedded capacity. On shared (free) capacity it returnsFixedCapacityLimitExceeded/ 403. The export is asynchronous — this tool starts the export, then polls until the job reachesSucceededorFailed(orpollTimeoutSecondselapses), then downloads the file and returns it as base64 along with the job metadata. PNG exports only work for single-page reports. For PPTX/PDF, passpages(array of page names, e.g.,["ReportSection", "ReportSection1"]) to limit the export. See the documentationWritev0.0.3 -
Get Dataset Refresh
actionTriggers a refresh operation for a specified Power BI dataset. See the documentationRead-onlyv0.0.3 -
Get Refresh History
actionGet the refresh history for a Power BI dataset. Use List Datasets first to resolve a dataset name →datasetId. PassworkspaceId(from List Workspaces) orworkspaceNameto scope to a specific workspace, or omit both for My workspace. Each entry includesrequestId,refreshType(OnDemand,Scheduled,ViaApi, etc.),startTime,endTime,status(Completed,Failed,Disabled,Cancelled,Unknown—Unknownmeans still in progress), andserviceExceptionJsonon failures. See the documentationRead-onlyv0.0.3
Triggers
-
Dataset Refresh Completed
triggerEmit new event when a dataset refresh operation has completed. See the documentationv0.0.7 -
Dataset Refresh Failed
triggerEmit new event when a dataset refresh operation has failed in Power BI. See the documentationv0.0.7 -
New Dataset Refresh Created
triggerEmit new event when a new dataset refresh operation is created. See the documentationv0.0.4
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- gitlab,microsoft_power_bi
- Primary app
- GitLab (gitlab)
- Second app
- Microsoft Power BI (microsoft_power_bi)
- Authentication
- OAuth + OAuth
- Available actions
- 43
- Available triggers
- 13