Memos MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Memos MCPCreate a memo saying 'pick up milk'."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Memos MCP
Feature-complete MCP server for self-hosted Memos, with optional OAuth 2.1 (PKCE) for remote clients (Cursor / Claude custom connectors).
Inspired by Red5d/memos_mcp and jtsang4/memos-mcp.
OAuth accounts are local to this gateway (configured via env). They do not sync with Memos users. Memos API access always uses
MEMOS_ACCESS_TOKEN.
Features
Area | Tools |
Memo CRUD |
|
Attachments |
|
Relations / comments |
|
Reactions |
|
Shares |
|
Meta |
|
Related MCP server: Memos MCP Server
Requirements
Node.js 20+
A running Memos instance and an Access Token (Settings → Access Tokens)
Quick start
git clone https://github.com/YOUR_USER/memos-mcp.git
cd memos-mcp
cp .env.example .env
# edit .env — at least MEMOS_BASE_URL + MEMOS_ACCESS_TOKEN
npm installLocal stdio (Cursor / Claude Desktop)
No OAuth needed; the process uses MEMOS_ACCESS_TOKEN from env.
{
"mcpServers": {
"memos": {
"command": "npx",
"args": ["tsx", "/absolute/path/to/memos-mcp/src/index.ts"],
"env": {
"MEMOS_BASE_URL": "http://localhost:5230",
"MEMOS_ACCESS_TOKEN": "your-token"
}
}
}
}HTTP + OAuth (remote MCP)
npm run start:httpDefault: http://127.0.0.1:3781/mcp
Set PUBLIC_URL to the URL clients will open (e.g. https://memos-mcp.example.com). Put nginx/Caddy in front for TLS.
In Cursor, add a remote MCP URL pointing at /mcp, then sign in with OAUTH_USERNAME / OAUTH_PASSWORD from .env.
Optional: set MCP_API_KEY and call Authorization: Bearer <key> to skip the browser OAuth flow (scripts / automation).
Environment
Variable | Description |
| Memos base URL |
| Memos access token ( |
| Local OAuth login (HTTP mode) |
| Multi-user JSON: |
| Public origin for OAuth metadata |
| Listen address (default |
|
|
| Optional static Bearer |
| OAuth state dir (default |
OAuth endpoints
Compatible with MCP OAuth 2.1 clients:
GET /.well-known/oauth-authorization-serverGET /.well-known/oauth-protected-resourceGET/POST /oauth/authorizePOST /oauth/tokenPOST /oauth/registerGET /health·POST /mcp
Architecture
AI Client ──OAuth / API key──► memos-mcp (/mcp)
│
│ Bearer MEMOS_ACCESS_TOKEN
▼
Memos (/api/v1/…)Development
npm run typecheck
npm test
npm run dev:httpSecurity notes for operators
Never commit
.envordata/oauth.json.Prefer strong
OAUTH_PASSWORD/MCP_API_KEYwhen exposing HTTP publicly.Rotate Memos access tokens if they leak.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Securely search, create, and organize your Mem notes and collections from AI assistants.
Connect AI to your flomo notes. Search, create, edit notes and manage tags via MCP.
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Full-control memory API for AI agents — memories, collections, links, search, and bulk operations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Memos instances for personal note-taking and knowledge management. Supports creating, searching, updating, and organizing memos with tags, dates, and visibility settings through natural language.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Memos instances for knowledge management. Supports searching, creating, updating, and retrieving memos with markdown content, tags, and visibility controls.45MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, read, update, delete, and list memos via the MCP protocol.3MIT
- AlicenseAqualityDmaintenanceConnects to Memos note-taking service to read, write, search, filter, and manage memos, including creating comments and managing users.81MIT