docs(minimax-mem0): clarify OAuth-only auth in the package + fix MCP URL trailing slash (review)

This commit is contained in:
Himanshu-Sangshetti
2026-08-31 18:41:32 +05:30
parent fa80bfdb3f
commit 9b7001e44c
+3 -3
View File
@@ -13,7 +13,7 @@ minimax-mem0/
.minimax-plugin/
plugin.json # manifest (schemaVersion 1)
icon.png # 180x180 square Mem0 icon
mem0.mcp.json # remote MCP: https://mcp.mem0.ai/mcp (streamable-http)
mem0.mcp.json # remote MCP: https://mcp.mem0.ai/mcp/ (streamable-http)
skills/
memory/
SKILL.md # when to recall / save / update memory
@@ -21,12 +21,12 @@ minimax-mem0/
Two capabilities:
- **MCP** (`mem0.mcp.json`) points at Mem0's hosted MCP server (`https://mcp.mem0.ai/mcp`), which exposes the memory tools (`add_memory`, `search_memories`, `update_memory`, `delete_memory`, and more). No secrets are stored in the package.
- **MCP** (`mem0.mcp.json`) points at Mem0's hosted MCP server (`https://mcp.mem0.ai/mcp/`), which exposes the memory tools (`add_memory`, `search_memories`, `update_memory`, `delete_memory`, and more). No secrets are stored in the package.
- **Skill** (`skills/memory/SKILL.md`) tells the agent when to search, save, update, and delete memory so recall happens automatically.
## Authentication
Mem0's MCP server is authenticated. It supports OAuth browser sign-in (the client authorizes the user's Mem0 account on first use) or an API-key bearer token for headless clients. No key is committed in this package. Get a key from the [Mem0 dashboard](https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-minimax).
Mem0's MCP server requires authentication. Per the MiniMax plugin spec, no credentials are placed in this package; the MiniMax client authorizes the user's Mem0 account through the MCP OAuth flow on first use. Users get a Mem0 account from the [Mem0 dashboard](https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-minimax).
## Links