# Connect your AI in minutes

MemScope speaks MCP for assistants and agents, and a plain REST API for internal apps.

## Connect ChatGPT

1. In ChatGPT, open Settings → Connectors and add MemScope.
2. Sign in and pick the organization to connect.
3. Review the permissions MemScope asks for on the consent screen and approve.
4. Ask ChatGPT to save something to MemScope, then ask it back. It calls save_memory and search_memories.

## Connect other MCP clients

Any MCP-capable client (Claude, Cursor, a custom agent) can connect to the remote MCP endpoint over streamable HTTP.
Auth is OAuth 2.1 with PKCE, dynamic client registration and a consent screen.

- MCP endpoint: https://mcp.memscope.ai/mcp
- Discovery: /.well-known/oauth-protected-resource
- Exact commands and config per client: https://memscope.ai/agents.md

## Save your first memory

1. Ask: “Remember that Project Falcon switched to Supplier B.” The AI calls save_memory.
2. In a new chat, ask: “Which supplier does Project Falcon use?” The AI calls search_memories and answers from the memory.
3. Open Memories in MemScope to see it, with its audience and sensitivity.
4. Ask: “Who can see that memory?” The AI calls explain_memory and names the rule.

## MCP tools reference

- `save_memory(content, scope?, team?, teams?, project?, importance?, idempotency_key?, kind?, valid_until?, supersedes?, agent?, run_id?)` — Store an explicit memory. Classified asynchronously; returns immediately. (Old name: remember.)
- `search_memories(query, project?, team?, topics?, teams?, limit?, detail?, max_chars?, kind?, include_expired?, include_superseded?, run_id?)` — Search memory by meaning. Only memories the authenticated human may read are returned. (Old name: recall.)
- `grep_memories(pattern, ignore_case?, teams?, projects?, topics?, kind?, include_expired?, include_superseded?, limit?, cursor?)` — Find exact text (names, IDs, error strings), like grep: matching lines in context, newest first, with counts per team, project and tag. Only memories the person may read are searched.
- `list_teams(kind?)` — List the teams and projects the signed-in person's organization exposes — the valid values for `search_memories`' team/project filters and `save_memory`'s filing targets. kind is teams, projects or all (default all). Never lists another organization's groups.
- `list_topics()` — List the organization's sensitive topics (HR, Legal, Finance and any the org added) — good `search_memories` query terms for guarded subjects. Read-only; only the caller's organization's topics.
- `explain_memory(memory_id)` — Why a memory is or is not accessible, including the governing rule.
- `correct_memory(memory_id, new_content, reason, kind?, valid_until?, agent?, run_id?)` — Create a new immutable version of a memory with a corrected body.
- `forget_memory(memory_id, reason, confirm_human?, agent?, run_id?)` — Forget a memory, only when the person asks (needs their confirmation). Authorized users can restore it for 30 days; then it is erased for good.
- `list_memories(filter?, limit?, cursor?, kind?, agent?, run_id?)` — Browse memories the person may read (filter: mine, needs_review, team, project, forgotten).
- `get_memory(memory_id)` — Full detail of one memory, including its version history.
- `change_scope(memory_id, scope, reason, team?, teams?, project?, confirm_widen?, confirm_human?, agent?, run_id?)` — Change who may read a memory. A change that could give more people access needs the person’s confirmation.
- `change_sensitivity(memory_id, sensitivity, reason, confirm_widen?, confirm_human?, agent?, run_id?)` — Change a memory’s sensitivity. Lowering it needs the person’s confirmation.
- `review_queue(limit?)` — Flagged memories waiting for the person to review.
- `review_memory(memory_id, action, reason, scope?, team?, project?, sensitivity?, confirm_widen?, confirm_human?, agent?, run_id?)` — Resolve a review: approve, reroute to a team or project, or tighten.
- `supersede_memory(memory_id, replaced_by, undo?, agent?, run_id?)` — Mark a memory as replaced by a newer one; it leaves default recall, history kept.
- `restore_memory(memory_id, reason, agent?, run_id?)` — Bring back a forgotten memory.

## REST API

Internal applications use the same memory service over REST. Browser clients authenticate with an HttpOnly session cookie; programmatic clients may use an OAuth bearer token.

- Interactive API reference: https://api.memscope.ai/docs
- OpenAPI schema: https://api.memscope.ai/openapi.json

---

Web page: https://memscope.ai/docs · All facts for AI agents: https://memscope.ai/llms.txt
