CONNECT APP
Build with Mem
Artificial Intelligence (AI)
- API key
MCP
Give your agent Mem tools
Every Mem action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Mem account for each tool call — you store no tokens.
// 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": "mem",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Append Mem:
const result = await mcp.callTool({
name: "mem-append-mem",
arguments: {
memId: "Mem ID",
content: "Content",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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": "mem",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Append Mem:
result = await session.call_tool("mem-append-mem", {
"memId": "Mem ID",
"content": "Content",
})API PROXY
Call the Mem API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Mem API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.mem.ai/v0/mems",
})
// Any allowed Mem endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.mem.ai/v0/mems
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkubWVtLmFpL3YwL21lbXM?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Mem actions from your backend
Connect a user's Mem account once, then run Append Mem on their behalf from your own code — TypeScript, Python, or plain HTTP.
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 result = await pd.actions.run({
id: "mem-append-mem",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mem: { authProvisionId: "apn_xxxxxxx" },
memId: "Mem ID",
content: "Content",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="mem-append-mem",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"mem": {"authProvisionId": "apn_xxxxxxx"},
"memId": "Mem ID",
"content": "Content",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "mem-append-mem",
"configured_props": {
"mem": { "authProvisionId": "apn_xxxxxxx" },
"memId": "Mem ID",
"content": "Content"
}
}'TOOLS
Mem actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
No Mem triggers are available yet.
MULTI-APP
Use Mem with other popular apps
Most products don't stop at one integration. Pair Mem with the other apps your users rely on, and ship use cases that span both.
- App slug
- mem
- Authentication
- API key
- Categories
- Artificial Intelligence (AI)
- Actions
- 2
- Triggers
- 0
- API proxy
- Available