Memos MCP Server

MCP wrapper for memos-mcp

Remote serverstreamable-httpTypeScript

What is the Memos MCP server?

Memos MCP server exists for a simple reason — assistants are far more useful when they can act on Memos directly instead of describing what you should do. MCP wrapper for memos-mcp.

What you get

MCP (Model Context Protocol) server for the self-hosted notes app Memos.

  • Search memos with filters and pagination
  • Create, read, update, delete memos
  • Access token authentication via Bearer token
  • Thin TypeScript wrapper for npx stdio startup

What the assistant can call

Once Memos is connected, these are the calls the assistant has available:

  • memos_search — query (string)
  • memos_get — memo_uid (string)
  • memos_create — content (string)
  • memos_update — memo_uid (string)
  • memos_delete — memo_uid (string)

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 4 environment variables: MEMOS_BASE_URL, MEMOS_ACCESS_TOKEN, MEMOS_API_TOKEN, YOUR_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • A running Memos instance (default http://localhost:5230) - An access token (Settings → Access Tokens)

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Memos's toolset — memos_search, memos_get, memos_create and 2 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Memos's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the memos mcp server does with a few real requests.

Available tools

ToolWhat it does
memos_searchquery (string)
memos_getmemo_uid (string)
memos_createcontent (string)
memos_updatememo_uid (string)
memos_deletememo_uid (string)

How to install the Memos MCP server

## MCP client config

```json
{
  "mcpServers": {
    "memos": {
      "command": "memos-mcp",
      "args": ["--base-url", "http://localhost:5230", "--access-token", "YOUR_TOKEN"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • A running Memos instance (default http://localhost:5230) - An access token (Settings → Access Tokens)
VariableDescriptionRequired
MEMOS_BASE_URLEndpoint or connection string the server talks to.Yes
MEMOS_ACCESS_TOKENCredential the server authenticates with.Yes
MEMOS_API_TOKENCredential the server authenticates with.Yes
YOUR_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Memos to memos search.
  • Use Memos to memos get.
  • Use Memos to memos create.

Frequently asked questions

It connects Memos to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (memos_search, memos_get, memos_create, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memos directly.