MCP Server for MemOS API

A Model Context Protocol (MCP) implementation for the MemOS API service. This package provides a command-line interface to interact with MemOS API using MCP standards.

MCP Configuration

To use this package In MCP Client, use the following configuration: （You may need to install Node.js first）

Configuration Explanation

• command: Uses npx to run the package

• args: Arguments passed to npx to run the package

• env: Environment variables

  • MEMOS_API_KEY: Your Memos API key for authentication (Get your API Key in Dashboard[https://memos-dashboard-pre.openmem.net/cn/quickstart/])

  • MEMOS_USER_ID: Stable per-human identifier. MUST be deterministic and non-PII, and MUST remain the same for the same person across devices/sessions. NEVER reuse across different people. DO NOT use random values, device IDs, or model/chat session IDs. Recommended: SHA-256(lowercase(trim(email))) or your SSO subject/employee ID.

  • MEMOS_CHANNEL: The site where you are seeing this document. Candidate values: MODELSCOPE, MCPSO, MCPMARKETCN, MCPMARKETCOM, GLAMA, PULSEMCP, MCPSERVERS,LOBEHUB,MEMOS(meaning the MemOS official website), GITHUB(meaning this README file)

Available MCP Tools

This package provides the following MCP tools:

1. add_message

   • Adds a new message to a conversation

   • Parameters:

     • conversation_id: Unique identifier of the conversation associated with the feedback.

     • messages: Array of messages containing role and content information.

       • role: Role of the message sender (user or assistant).

       • content: Message content.

       • chat_time: (Optional) Message timestamp.

2. search_memory

   • Searches for memories in a conversation.

   • Parameters:

     • query: Search query to find relevant content in conversation history.

     • conversation_id: Conversation ID to define the search scope.

     • memory_limit_number: Maximum number of results to return (default: 6).

3. delete_memory

   • Delete specific memories by their IDs.

   • Parameters:

     • user_ids: List of user IDs whose memories will be deleted.

     • memory_ids: List of memory IDs to delete.

4. add_feedback

   • Submit user feedback to the MemOS system.

   • Note: Feedback is applied asynchronously — add_feedback returns immediately (often with a task_id), and the effect may take a short time to appear.

   • Parameters:

     • user_id: The user identifier associated with the feedback.

     • conversation_id: Unique identifier of the conversation associated with the feedback.

     • feedback_content: The specific content of the feedback.

     • agent_id: (Optional) Agent ID associated with the feedback.

     • app_id: (Optional) App ID associated with the feedback.

     • feedback_time: (Optional) Feedback time string (default: current UTC time).

     • allow_public: (Optional) Whether to allow public access (default: false).

     • allow_knowledgebase_ids: (Optional) List of knowledge base IDs allowed to be written to.

All tools use the same configuration and require the MEMOS_API_KEY environment variable.

Features

• MCP-compliant API interface

• Command-line tool for easy interaction

• Built with TypeScript for type safety

• Express.js server implementation

• Zod schema validation

Prerequisites

• Node.js >= 18

• npm or pnpm (recommended)

Installation

You can install the package globally using npm:

Or using pnpm:

Usage

After installation, you can run the CLI tool using:

Or if installed globally:

Development

1. Clone the repository:

2. Install dependencies:

3. Start development server:

4. Build the project:

Available Scripts

• pnpm build - Build the project

• pnpm dev - Start development server using tsx

• pnpm start - Run the built version

• pnpm inspect - Inspect the MCP implementation using @modelcontextprotocol/inspector

Project Structure

Dependencies

• @modelcontextprotocol/sdk: ^1.0.0

• express: ^4.19.2

• zod: ^3.23.8

• ts-md5: ^2.0.0

Version

Current version: 1.0.0-beta.2