
Company News
Socket Joins New OpenJS Program to Fund Node.js Security Work
Socket is joining the OpenJS Security Stewardship Program to fund Node.js vulnerability research, maintainer remediation, and security releases.
@memtensor/memos-api-mcp
Advanced tools
A Model Context Protocol (MCP) implementation for the [MemOS](https://github.com/MemTensor/MemOS) API service. This package provides a command-line interface to interact with MemOS API using MCP standards.
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.
To use this package In MCP Client, use the following configuration: (You may need to install Node.js first)
{
"mcpServers": {
"memos-api-mcp": {
"command": "npx",
"args": ["-y", "@memtensor/memos-api-mcp"],
"env": {
"MEMOS_API_KEY": "your-api-key",
"MEMOS_USER_ID": "your-user-id",
"MEMOS_CHANNEL": "the-site-where-you-are-seeing-this-document"
}
}
}
}
command: Uses npx to run the packageargs: Arguments passed to npx to run the packageenv: 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)This package provides the following MCP tools:
add_message
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.search_memory
query: Text content to search within the memories. The token limit for a single query is 4k.filter: (Optional) Filter conditions, used to precisely limit the memory scope before retrieval.knowledgebase_ids: (Optional) Array specifying the knowledge bases to search.
["all"].include_preference: (Optional) Enable preference memory recall. Default: true.preference_limit_number: (Optional) Max preference memories to return. Default: 9, max 25.include_tool_memory: (Optional) Enable tool memory recall. Default: false.tool_memory_limit_number: (Optional) Max tool memories to return. Default: 6, max 25.include_skill: (Optional) Enable Skill recall. Default: false.skill_limit_number: (Optional) Max Skills to return. Default: 6, max 25.relativity: (Optional) Relevance threshold (0-1) for recalled memories. A value of 0 disables relevance filtering.conversation_first_message: First user message in the thread (used to generate conversation_id).memory_limit_number: Maximum number of memories that can be recalled. Default: 9, max 25.delete_memory
user_ids: List of user IDs whose memories will be deleted.memory_ids: List of memory IDs to delete.add_feedback
add_feedback returns immediately (often with a task_id), and the effect may take a short time to appear.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.get_user_profile
include_preference: (Optional) Whether to include preference memories.include_tool_memory: (Optional) Whether to include tool trajectory memories.current: (Optional) Page number.size: (Optional) Number of entries per page.create_knowledge_base
knowledgebase_name: Name of the knowledge base.knowledgebase_description: (Optional) Description of the knowledge base.remove_knowledge_base
knowledgebase_id: Target knowledge base ID.add_kb_document
knowledgebase_id: Target knowledge base ID.file: Document list.
content: Local absolute path, public URL, or Base64 Data URI.file_name: (Optional) File name.mime_type: (Optional) MIME type. Required when content is a local file path.get_kb_documents
file_ids: List of document IDs.delete_kb_documents
file_ids: List of document IDs.All tools use the same configuration and require the MEMOS_API_KEY environment variable.
You can install the package globally using npm:
npm install -g @memtensor/memos-api-mcp
Or using pnpm:
pnpm add -g @memtensor/memos-api-mcp
After installation, you can run the CLI tool using:
npx @memtensor/memos-api-mcp
Or if installed globally:
memos-api-mcp
git clone <repository-url>
cd memos-api-mcp
pnpm install
pnpm dev
pnpm build
pnpm build - Build the projectpnpm dev - Start development server using tsxpnpm start - Run the built versionpnpm inspect - Inspect the MCP implementation using @modelcontextprotocol/inspectormemos-mcp/
├── src/ # Source code
├── build/ # Compiled JavaScript files
├── package.json # Project configuration
└── tsconfig.json # TypeScript configuration
@modelcontextprotocol/sdk: ^1.0.0express: ^4.19.2zod: ^3.23.8ts-md5: ^2.0.0Current version: 1.1.0
FAQs
A Model Context Protocol (MCP) implementation for the [MemOS](https://github.com/MemTensor/MemOS) API service. This package provides a command-line interface to interact with MemOS API using MCP standards.
The npm package @memtensor/memos-api-mcp receives a total of 0 weekly downloads. As such, @memtensor/memos-api-mcp popularity was classified as not popular.
We found that @memtensor/memos-api-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 8 open source maintainers collaborating on the project.

Company News
Socket is joining the OpenJS Security Stewardship Program to fund Node.js vulnerability research, maintainer remediation, and security releases.

Security News
Two compromised GitHub Actions were re-enabled with malicious tags intact, exposing thousands of downstream repositories to Mini Shai-Hulud.

Research
/Security News
A malicious Firefox extension fetches its payload after installation to evade detection, steal Google session cookies, and automate account takeover.