MCP Server Memos

Created By
ChenyqThua year ago
Overview

What is MCP Server Memos?

MCP Server Memos is a server designed to interact with the Memos note-taking service using the MCP protocol, allowing users to manage their notes through natural language commands.

How to use MCP Server Memos?

To use MCP Server Memos, you need to configure the server with your Memos URL and access token, then run the server and interact with it through supported clients.

Key features of MCP Server Memos?

  • 🔍 Search notes
  • ✨ Create new notes with visibility settings
  • 📖 Retrieve note content
  • ✏️ Update existing notes
  • 🔐 Secure authentication using access tokens

Use cases of MCP Server Memos?

  1. Quickly searching for notes using keywords.
  2. Creating and managing notes through voice or text commands.
  3. Updating notes on-the-fly during meetings or brainstorming sessions.

FAQ from MCP Server Memos?

  • Can I use MCP Server Memos with any client?

Yes! As long as the client supports the MCP protocol, you can use it with MCP Server Memos.

  • Is there a limit to the number of notes I can create?

No, you can create as many notes as your Memos server allows.

  • How do I secure my access token?

It is recommended to use environment variables for sensitive information instead of command-line parameters.

Server Config

{
  "mcpServers": {
    "mcp-server-memos": {
      "command": "npx",
      "args": [
        "-y",
        "@chenyqthu/mcp-server-memos"
      ],
      "env": {
        "MEMOS_URL": "https://your-memos-server",
        "MEMOS_TOKEN": "your_access_token"
      }
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
ChenyqThu
Star
0
Language
JavaScript
License
-
Category
note-taking
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago