Skip to main content
Memory MCP lets Claude Code, Cursor, or your own agent retrieve company-specific context from PAM — people, projects, decisions, processes, priorities, history, customers, and internal terminology — without writing to PAM Chat history.
New to Memory MCP? Start with the Quickstart to generate a key, connect your client, and run your first retrieve_memory call.

​
What Memory MCP does

  • Exposes a dedicated MCP server at POST /v1/mcp/memory (JSON-RPC 2.0 over HTTP)
  • Provides one production tool in v1: retrieve_memory
  • Authenticates with a static pam_mkey agent API key (desktop agents) or OAuth 2.1 Bearer tokens (Claude web, ChatGPT)
  • Keeps retrieval audit logs separate from in-app PAM Chat
  • Enforces per-account quotas on retrieval calls

​
What it does not do

  • Write to PAM Chat threads or modify your workspace
  • Expose write access to your memory or integrations

Quickstart

Generate a key, paste MCP config, and test retrieval.

retrieve_memory

Tool reference: parameters, responses, and examples.

Client setup

Step-by-step guides for ChatGPT, Claude, Cursor, Perplexity, and more.

MCP reference

Endpoint, JSON-RPC methods, and protocol details.

​
Prerequisites

Before you connect an MCP client:
  1. Connect at least one memory source in PAM (Gmail, Drive, Notion, Slack, or another supported integration)
  2. Wait for memory readiness to complete initial sync and processing
  3. Choose your client type on Setup — generate a pam_mkey for desktop agents, or copy the MCP URL for browser LLM connectors
Generate keys and copy your MCP URL on Setup. Rotate keys or manage browser connections on Access. See Setup and keys and Client setup for details.