MULTI-APP TOOLKIT
Build with GitHub + Linear (API key)
- Multi-app
- One MCP session
- 74 actions
- 33 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitHub and Linear (API key) 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": "github,linear_app",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: GitHub and Linear (API key) tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Issue:
const result = await mcp.callTool({
name: "github-create-issue",
arguments: {
repoFullname: "Repository",
title: "Title",
},
})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 [githubTools, linearAppTools] =
await Promise.all([
pd.components.list({ app: "github" }),
pd.components.list({ app: "linear_app" }),
])
// 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=github" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=linear_app" \
-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
GitHub
Connected account
Linear (API key)
Connected account
TOOLS
GitHub tools
The GitHub tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 48
-
Create Issue
actionCreate a new issue in a repository, optionally with labels, assignees, and a milestone. Provide the repository as anowner/repostring. Labels and assignees are passed by name/login (e.g.bug,octocat) — setting them requires push access to the repo. To comment on an existing issue instead, use Create Issue Comment; to change an existing issue, use Update Issue. See the documentationWritev0.4.3 -
Search Issues and Pull Requests
actionSearch issues and pull requests across GitHub using the issues-search query DSL. This is the escape hatch for finding items by keyword, state, label, author, or assignee when you don't already know the issue/PR number. Build thequeryfrom space-separated qualifiers:repo:owner/nameto scope to one repo (a barerepo:namewith no owner is auto-resolved to your own account),is:issue/is:pr,is:open/is:closed,label:bug,author:octocat,assignee:octocat,in:title/in:body, and free-text keywords. Example:repo:PipedreamHQ/pipedream is:issue is:open label:bug raptor. Returns matching items (each withnumber,title,state,labels,html_url); feed a result'snumberinto Get Issue, Get Pull Request, or Create Issue Comment. See the query syntaxRead-onlyv0.3.3 -
Create Branch
actionCreate a new branch in a repository, pointing at the tip of a source branch. Provide the repository as anowner/repostring, the newbranchName, and optionally thesourceBranchto branch from (defaults to the repository's default branch). Use Create or Update File Contents to add commits to the new branch, then Create Pull Request to open a PR. See the documentationWritev1.0.2 -
Create Gist
actionAllows you to add a new gist with one or more files. See the documentationWritev0.0.18 -
Create Issue Comment
actionAdd a comment to an existing issue or pull request (GitHub treats PRs as issues for comments, so the samenumberworks for both). Provide the repository as anowner/repostring, the issue/PR number, and the comment body. If you only know the issue/PR by title, call Search Issues and Pull Requests first to resolve its number. See the documentationWritev0.1.3 -
Create or Update File Contents
actionCreate a new file or overwrite an existing one in a repository with a single commit. Provide the repository as anowner/repostring, the filepath, the raw textcontent(passed as-is — do not base64-encode it yourself), and a commit message. If the file already exists on the target branch it is overwritten; the required blob SHA is resolved for you automatically. Defaults to the repository's default branch unlessbranchis set. See the documentationWritev1.0.3 -
Create Pull Request
actionOpen a pull request proposing to merge one branch into another within a repository. Provide the repository as anowner/repostring, theheadbranch (the source containing your changes) and thebasebranch (the target, e.g.main), plus a title. The head and base branches must already exist and differ. For a cross-fork PR, setheadtousername:branch. Use Create or Update File Contents to push changes to a branch before opening the PR. See the documentationWritev1.0.3 -
Create Pull Request Review
actionSubmit a review on a pull request: approve it, request changes, or leave a general comment. SeteventtoAPPROVE,REQUEST_CHANGES, orCOMMENT— abodyis required forREQUEST_CHANGESandCOMMENT. Optionally attach inlinecommentstied to specific lines of the diff. GitHub forbids approving your own pull request, so useCOMMENTto leave feedback on PRs you authored. Provide the repository as anowner/repostring and the PR number. Use Get Pull Request Files to find the file paths and lines to comment on, and Search Issues and Pull Requests withis:prto resolve the PR number from a title. See the documentationWritev0.0.3
Triggers top 4 of 27
-
New Branch Created
triggerEmit new event when a branch is created.Instantv1.0.16 -
New Card in Column (Classic Projects)
triggerEmit new event when a (classic) project card is created or moved to a specific column. For Projects V2 useNew Issue with Statustrigger. More information hereInstantv1.0.15 -
New Collaborator
triggerEmit new event when a collaborator is addedInstantv1.0.16 -
New Commit
triggerEmit new event when commits are pushed to a branchInstantv1.0.17
TOOLS
Linear (API key) tools
The Linear (API key) tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 26
-
Create Comment
actionAdd a comment to a Linear issue. Use Search Issues to find the target issue ID first. Returns the new comment's ID and body. Example:issueId: "iss_01abc",body: "Fixed in PR #123."→ returns{success: true, comment: {id: "cmt_xyz", body: "Fixed in PR #123."}}. See the documentationWritev1.0.0 -
Create Initiative
actionCreate a new initiative in Linear to track a cross-team strategic goal. Initiatives group multiple projects toward a shared objective. Use List Users to find a valid owner ID. Example:initiativeName: "Q4 Platform Upgrade",status: "Active",targetDate: "2024-12-31"→ returns{success: true, initiative: {id: "ini_01abc", name: "Q4 Platform Upgrade"}}. See the documentationWritev1.0.0 -
Create Initiative Update
actionPost a status update on a Linear initiative. Use List Initiatives first to obtain the initiative ID. Updates appear in the initiative's activity feed and can include a health status. Example:initiativeId: "b2c3d4e5-0000-0000-0000-000000000002",body: "Two projects completed; on track for Q4.",health: "onTrack"→ returns{success: true, initiativeUpdate: {id: "iu_01xyz"}}. See the documentation.Writev0.0.1 -
Create Issue
actionCreates a new issue in Linear. Requires a team ID and title; all other fields are optional. Use Get Teams to discover valid team IDs, List Workflow States to find state IDs, List Users to find assignee IDs, and List Labels to find label IDs. Example:teamId: "9d1c3f7e-2b48-4c6a-9f1e-5a7b8c9d0e1f",title: "Fix login redirect on mobile"→ returns{success: true, issue: {id: "iss_01", identifier: "ENG-42", title: "Fix login redirect on mobile"}}. See the documentation.Writev0.4.22 -
Create Project
actionCreate a new project in Linear to track a body of work. Projects group related issues within a team. Use Get Teams for team IDs, List Project Statuses to find status IDs, List Users for member IDs, and List Project Labels for label IDs. Example:teamId: "9d1c3f7e-...",projectName: "Mobile App v2",statusId: "s2abc"→ returns{success: true, project: {id: "proj_01", name: "Mobile App v2"}}. See the documentation.Writev1.0.0 -
Create Project Update
actionPost a status update on a Linear project. Use List Projects first to obtain the project ID. Updates appear in the project's activity feed. Example:projectId: "a1b2c3d4-0000-0000-0000-000000000001",body: "Q3 milestone complete; all P0 issues resolved.",health: "onTrack"→ returns{success: true, projectUpdate: {id: "pu_01xyz"}}. See the documentation.Writev0.0.1 -
Get Initiative Update
actionRetrieve a single initiative update by its ID in Linear. Use List Initiative Updates first to obtain a valid update ID. Returns the full update includingid,body,health,createdAt, and author. Example:initiativeUpdateId: "530f4366-88ab-4866-a44b-c2326728c32d"→ returns{id: "530f4366-88ab-4866-a44b-c2326728c32d", body: "Two projects completed.", health: "onTrack", createdAt: "2024-01-15T10:00:00Z"}. See the documentation.Read-onlyv0.0.1 -
Get Issue
actionRetrieve a single Linear issue by its UUID or human-readable identifier. Provide exactly one ofissueId(UUID) orissueIdentifier(e.g.ENG-42). Returns complete issue details: title, description, state, assignee, team, project, labels, and timestamps. Use the optionalfieldsprop to narrow the response to only the keys you need (reduces context for large result sets). Example:issueIdentifier: "ENG-42"→ returns{id: "iss_01abc", identifier: "ENG-42", title: "Fix login redirect", state: {name: "In Progress"}}. See the documentation.Read-onlyv0.2.0
Triggers top 4 of 6
-
Issue Status Updated (Instant)
triggerEmit new event when an issue's workflow state changes (e.g., Todo to In Progress). Returns issue with previous and current state info. Can filter by specific target state. See Linear docs for additional info See the documentation.Instantv0.1.24 -
Issue Updated (Instant)
triggerEmit new event when any issue is updated in Linear. Provides complete issue details with changes. Supports filtering by team and project. Includes all updates except status changes. See Linear docs for additional info See the documentation.Instantv0.3.24 -
New Comment Created (Instant)
triggerEmit new event when a new comment is added to an issue in Linear. Returns comment details including content, author, issue reference, and timestamps. Supports filtering by team. See Linear docs for additional info See the documentation.Instantv0.1.24 -
New Issue Created (Instant)
triggerEmit new event when a new issue is created in Linear. Provides complete issue details including title, description, team, assignee, state, and timestamps. Supports filtering by team and project. See Linear docs for additional info See the documentation.Instantv0.3.24
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
- github,linear_app
- Primary app
- GitHub (github)
- Second app
- Linear (API key) (linear_app)
- Authentication
- OAuth + API key
- Available actions
- 74
- Available triggers
- 33