MULTI-APP TOOLKIT
Build with Jira + Linear
- Multi-app
- One MCP session
- 56 actions
- 10 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Jira and Linear 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": "jira,linear",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Jira and Linear tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add Attachment To Issue:
const result = await mcp.callTool({
name: "jira-add-attachment-to-issue",
arguments: {
cloudId: "Cloud ID",
issueIdOrKey: "Issue ID or Key",
},
})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 [jiraTools, linearTools] =
await Promise.all([
pd.components.list({ app: "jira" }),
pd.components.list({ app: "linear" }),
])
// 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=jira" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=linear" \
-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
Jira
Connected account
Linear
Connected account
TOOLS
Jira tools
The Jira tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 39
-
Add Attachment To Issue
actionAdds an attachment to an issue. See the documentationWritev1.0.18 -
Add Comment To Issue
actionAdds a new comment to an issue. See the documentationWritev0.1.25 -
Add Multiple Attachments To Issue
actionAdds multiple attachments to an issue. See the documentationWritev1.0.18 -
Add Watcher To Issue
actionAdds a user as a watcher of an issue by passing the account ID of the user, For example,5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentationWritev0.0.25 -
Assign Issue
actionAssigns an issue to a user. See the documentationWritev0.0.24 -
Check Issues Against JQL
actionChecks whether one or more issues would be returned by one or more JQL queries. See the documentationRead-onlyv0.0.11 -
Count Issues Using JQL
actionProvide an estimated count of the issues that match the JQL. See the documentationRead-onlyv0.0.11 -
Create Custom Field Options (Context)
actionCreate a context for custom field options. See the documentation.Writev0.0.17
Triggers
-
New Event
triggerEmit new event when an event with subscribed event source triggered, See the documentationv0.0.25 -
New Issue Created Event (Instant)
triggerEmit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please useNew Eventsource and select multiple events.v0.0.25 -
New Issue Deleted Event (Instant)
triggerEmit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please useNew Eventsource and select multiple events.v0.0.25 -
New Issue Updated Event (Instant)
triggerEmit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please useNew Eventsource and select multiple events.v0.0.25
TOOLS
Linear tools
The Linear tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 17
-
Create Comment
actionCreate a comment in Linear. See the documentationWritev0.0.2 -
Create Initiative
actionCreate an initiative in Linear. See the documentation.Writev0.0.2 -
Create Issue
actionCreates a new issue in Linear. Requires team ID and title. Optional: description, assignee, project, state. Returns response object with success status and issue details. Uses OAuth authentication. See Linear docs for additional info here.Writev0.4.16 -
Create Project
actionCreate a project in Linear. See the documentation.Writev0.0.4 -
Get Current User
actionRetrieve rich context about the authenticated Linear user, including core profile fields, recent timestamps, direct team memberships, and high-level organization settings. Returns the user object, a paginated team list (with names, keys, cycle configs, etc.), associated team memberships, and organization metadata such as auth defaults and SCIM/SAML flags. Use this when your workflow or agent needs to understand who is currently authenticated, which teams they belong to, or what workspace policies might influence subsequent Linear actions. See Linear's GraphQL viewer docs here.Read-onlyv0.0.6 -
Get Issue
actionRetrieves a Linear issue by its ID. Returns complete issue details including title, description, state, assignee, team, project, labels, and timestamps. Uses OAuth authentication. See Linear docs for additional info here.Read-onlyv0.1.16 -
Get Teams
actionRetrieves all teams in your Linear workspace. Returns array of team objects with details like ID, name, and key. Supports pagination with configurable limit. Uses OAuth authentication. See Linear docs for additional info here.Read-onlyv0.2.17 -
Get View Issues
actionGet issues from a custom view in Linear. See the documentation.Read-onlyv0.0.2
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. Uses OAuth authentication. See Linear docs for additional info here.Instantv0.1.21 -
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. Uses OAuth authentication. See Linear docs for additional info here.Instantv0.3.20 -
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. Uses OAuth authentication. See Linear docs for additional info here.Instantv0.1.19 -
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. Uses OAuth authentication. See Linear docs for additional info here.Instantv0.3.20
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
- jira,linear
- Primary app
- Jira (jira)
- Second app
- Linear (linear)
- Authentication
- OAuth + OAuth
- Available actions
- 56
- Available triggers
- 10