MCP server

Memoth over MCP

A hosted Model Context Protocol server at mcp.memoth.ai. Your AI client signs in as you, searches the memory you are allowed to see, and can remember things back into it. No API key to paste, nothing to install.

What you get

Memoth extracts typed memory from the tools your organisation already uses, governs who can see each piece, and serves it to agents. The MCP server is the door for the AI assistants people use directly. Once connected, Claude, Cursor or ChatGPT can:

Search memory in natural language and get back fragments with their provenance (which source, which document, when) and a receipt id for the read.
Remember something from the conversation as your private memory, and be told what the memory layer did with it.
Replay a receipt: reopen an earlier read and see what was served then, what the same read would serve now, and the difference.
Ask who it is: the identity, scopes and tools the server believes the connection holds, straight from the verified token.

Everything is scoped to the person who signed in. The server never accepts a user, tenant or role as a tool argument: identity comes only from the OAuth token, so a prompt cannot talk the assistant into reading as somebody else.

Endpoints

url

https://mcp.memoth.ai/mcp             read and write
https://mcp.memoth.ai/mcp/readonly    read only — never writes

Both are Streamable HTTP endpoints (MCP revision 2026-07-28, and every client revision from 2025-06-18 up). Transport is stateless: no session ids, no server-sent event stream to hold open.

Connect in a minute

Add https://mcp.memoth.ai/mcp to your client. For Claude Code that is one command:
shell
```
claude mcp add --transport http memoth https://mcp.memoth.ai/mcp
```
The first request opens a browser tab at auth.memoth.ai. Enter your work email; Memoth finds your workspace and sends you to its sign-in (your company IdP, or the Memoth console).
Approve the consent screen. It names the client and the two things it asks for: read your memory, add to your memory.
Back in the client, ask something your organisation knows. Try whoami first if you want to see exactly what the server thinks you are.

Read-only connections

Point a client at /mcp/readonly instead and it can never write. The server drops the write tool from the list rather than refusing calls one by one, so the assistant does not see a tool it cannot use.

How it works

The server is an OAuth 2.1 resource server. It verifies the token your client presents, then exchanges it, per request, for a short-lived credential to Memoth’s memory service and calls that service as you. It holds no database and no standing credential of its own: every request is verified, exchanged and served, and the exchanged token dies with it.

Every search is recorded as a serving receipt: what was asked, under which identity and role audience, and what was served. The receipt id comes back with the result, and the memory_receipt tool reopens it. That record is the basis for the governance claims on the security page.