MULTI-APP TOOLKIT
Build with Anthropic (Claude) + Canvas
- Multi-app
- One MCP session
- 7 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Anthropic (Claude) and Canvas 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": "anthropic,canvas",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Anthropic (Claude) and Canvas tools arrive
// together, each keyed by its own app's slug.
// e.g. run Chat:
const result = await mcp.callTool({
name: "anthropic-chat",
arguments: {
model: "Model",
userMessage: "User Message",
},
})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 [anthropicTools, canvasTools] =
await Promise.all([
pd.components.list({ app: "anthropic" }),
pd.components.list({ app: "canvas" }),
])
// 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=anthropic" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=canvas" \
-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
Anthropic (Claude)
Connected account
Canvas
Connected account
TOOLS
Anthropic (Claude) tools
The Anthropic (Claude) tools this pairing puts in reach, each one running on your user's own connected account.
Actions
Triggers
No Anthropic (Claude) triggers are available yet.
TOOLS
Canvas tools
The Canvas tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
List Account ID Options
actionRetrieves available options for the Account ID field.Read-onlyv0.0.1 -
List Assignments
actionRetrieve a list of assignments for a course. See the documentationRead-onlyv0.0.2 -
List Courses
actionList all the courses associated with a given user. See the documentationRead-onlyv0.0.1 -
Search Course Content
actionSearch for content in a course. See the documentationRead-onlyv0.0.1 -
Update Assignment
actionUpdate an assignment. See the documentationWritev0.0.2
Triggers
No Canvas triggers are available yet.
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
- anthropic,canvas
- Primary app
- Anthropic (Claude) (anthropic)
- Second app
- Canvas (canvas)
- Authentication
- API key + API key
- Available actions
- 7
- Available triggers
- 0