MULTI-APP TOOLKIT
Build with Linear + Todoist
- Multi-app
- One MCP session
- 72 actions
- 14 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Linear and Todoist 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": "linear,todoist",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Linear and Todoist tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Comment:
const result = await mcp.callTool({
name: "linear-create-comment",
arguments: {
issueId: "Issue",
body: "Body",
},
})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 [linearTools, todoistTools] =
await Promise.all([
pd.components.list({ app: "linear" }),
pd.components.list({ app: "todoist" }),
])
// 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=linear" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=todoist" \
-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
Linear
Connected account
Todoist
Connected account
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 27
-
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 documentationWritev0.0.3 -
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 documentationWritev0.0.3 -
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.17 -
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.Writev0.0.5 -
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 Current User
actionRetrieve rich context about the authenticated Linear user, including core profile fields, recent timestamps, direct team memberships, and high-level organization settings. 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. Use the optionalfieldsprop to return only the top-level sections you need (reduces context for large workspaces). Example: call with no parameters → returns{user: {id: "usr_01", name: "Jane Doe", email: "jane@acme.com"}, organization: {id: "org_01", name: "Acme Inc"}, teams: {nodes: [{id: "9d1c3f7e-2b48-4c6a-9f1e-5a7b8c9d0e1f", name: "Engineering", key: "ENG"}], pageInfo: {endCursor: "...", hasNextPage: false}}, teamMemberships: {nodes: [{id: "tm_01"}], pageInfo: {endCursor: "...", hasNextPage: false}}}. See the documentation.Read-onlyv0.1.0 -
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
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.22 -
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.21 -
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.20 -
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.21
TOOLS
Todoist tools
The Todoist tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 45
-
Create Filter
actionCreates a filter. See the documentationWritev0.0.10 -
Create Label
actionCreates a label. See the documentationWritev0.0.10 -
Create Project
actionCreates a project. See the documentationWritev0.0.10 -
Create Project Comment
actionAdds a comment to a project. See the documentationWritev0.0.10 -
Create Section
actionCreates a section. See the documentationWritev0.0.10 -
Create Task
actionCreates a task. See the documentationWritev0.0.12 -
Create Task Comment
actionAdds a comment to a task. See the documentationWritev0.0.10 -
Delete Comment
actionDeletes a comment. See the documentationWritev0.0.10
Triggers top 4 of 8
-
New or Modified Task
triggerEmit new event for each new or modified task. See the documentationv0.0.12 -
New Completed Task
triggerEmit new event for each completed Todoist task, including recurring task completions. Non-recurring completions are polled viaGET /tasks/completed/by_completion_date. Recurring completions don't appear there - Todoist reschedules a recurring task instead of marking it completed there - so they're additionally polled via the v1 Activity Log (GET /api/v1/activities), detected as anitem:completedevent withextra_data.is_recurringset totrue. Accessing recurring task completions older than 7 days requires a Todoist premium/business plan. Respects the Projects filter. See the documentation.v2.0.0 -
New Incomplete Task
triggerEmit new event for each new incomplete task. See the documentationv0.1.6 -
New or Modified Project
triggerEmit new event for each new or modified project. See the documentationv0.0.12
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
- linear,todoist
- Primary app
- Linear (linear)
- Second app
- Todoist (todoist)
- Authentication
- OAuth + OAuth
- Available actions
- 72
- Available triggers
- 14