Mem MCP connector for AI agents

Tools your agent reaches for on Mem, scoped per user.

CALL ANY TOOL

Create, search, and organize notes and collections in the user's own Mem workspace.

memmcp_add_note_to_collection

Add an existing note to an existing collection. this operati

Add an existing note to an existing collection. this operation only creates the membership link and does not modify note or collection content. use create endpoints to create notes or collections. when to use: - you need to link an existing note to an existing collection. when not to use: - you need to create notes or collections first (`create_note` or `create_collection`). - you need to transfer a note out of one collection into another (`move_note`).

Parameters

Name

Type

Required

Description

collection_id

string

Required

UUID of the collection that will receive the note. Use an ID returned by create/list/search. The caller must be able to contribute to this collection.

note_id

string

Required

UUID of the note to add. Use an ID returned by create/list/search. The caller must be able to access this note.

memmcp_answer_question_about_attachment

Ask one focused question about a single attachment by kind a

memmcp_create_collection

Create a collection with optional caller-provided id and tim

memmcp_create_note

Create a note with an optional note id and collection links.

memmcp_delete_collection

Permanently delete a collection. hard-deleting removes the c

memmcp_extended_search_notes

Search notes and note-linked attachments together. returns n

memmcp_find_related_notes

Find notes semantically related to the current persisted con

memmcp_get_audio_recording

Fetch the current public transcript and metadata for a singl

memmcp_get_collection

Fetch metadata for a single collection by id. this tool retu

memmcp_get_note

Fetch the full current state of a single note by id. if the

memmcp_get_note_attachment_download_url

Generate a temporary signed download url for a note attachme

memmcp_list_collections

List collections visible to the authenticated caller with cu

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="memmcp")

mcp = MultiServerMCPClient({
    "memmcp": {
        "url": "https://mcp.scalekit.com/memmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "memmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/memmcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "memmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/memmcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="memmcp")
# Connect to MCP at https://mcp.scalekit.com/memmcp
# Pass: Authorization: Bearer + token

Try these prompts

Copy any prompt into your agent. Each maps directly to a Mem tool. Click to copy, paste into your agent, done.

Get started

Copy the prompt

Copied

Submit a complete markdown body for a note and the exact version being updated?

Copy the prompt

Copied

Soft-delete a note by moving it to trash?

Advanced

Copy the prompt

Copied

Set a note’s visible creation timestamp without changing its content?

Copy the prompt

Copied

Search notes using a required free-text query and structured filters?

SEE HOW AUTH WORKS

Your users connect once. Their Mem credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Mem MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Mem MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Mem MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Mem MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Mem as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Mem OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Mem?
Yes. Pass a tool name filter to listScopedTools so the AI agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Mem.

What happens when a user revokes Mem access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent read all my Mem notes?
Only the authorizing user's own notes and collections. Search, creation, and organization run per user, so personal knowledge bases stay personal.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit