Memos MCP Server

Created By
stephen9412a year ago
A Model Context Protocol (MCP) server for Memos API with search, create, retrieve, and tag listing capabilities.
Overview

What is Memos MCP Server?

Memos MCP Server is a Model Context Protocol (MCP) server designed to integrate Memos with AI assistants that support the MCP protocol, enabling functionalities like searching, creating, retrieving, and tagging memos.

How to use Memos MCP Server?

To use the Memos MCP Server, install Claude Desktop, configure the server with your Memos API details, and utilize the available tools to manage your memos.

Key features of Memos MCP Server?

  • Search memos using keywords.
  • Create new memos with customizable visibility settings and tags.
  • Retrieve specific memos by ID.
  • Get user information.

Use cases of Memos MCP Server?

  1. Integrating memo management with AI assistants.
  2. Facilitating easy access to memo content through search functionality.
  3. Allowing users to create and manage memos with different visibility settings.

FAQ from Memos MCP Server?

  • What is the purpose of Memos MCP Server?

It serves as a bridge between Memos and AI assistants, allowing for enhanced memo management.

  • Is Memos MCP Server free to use?

Yes, it is open-source and free to use.

  • What technologies are used in Memos MCP Server?

The project is developed using TypeScript and the FastMCP framework.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
stephen9412
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago