System · MODEL CONTEXT PROTOCOL
KunihiroS mem0 mcp for pm
Forked repo to customize into Project Management purpose.
WHAT IT CONNECTS
What KunihiroS mem0 mcp for pm gives an AI Agent
- Project memory storage and retrieval
- Semantic search for project information
- Structured project management data handling
- Fully tested stdio-based MCP Server tools
- Flexible logging: stderr by default, file output via `--logfile`
- Smart CLI invocation via pipx-compatible interface
- `--log=off` : Disable all logging (no logs are written)
- `--log=on --logfile=/absolute/path/to/logfile.log` : Enable logging and write logs to the specified absolute file path
- Both arguments are **required** when logging is enabled. The server will exit with an error if either is missing, the path is not absolute, or if invalid values are given.
- `add_project_memory`
- `get_all_project_memories`
- `search_project_memories`
- `update_project_memory`
- `delete_project_memory`
- `delete_all_project_memories`
- Default: stderr
- Optional: `--logfile /path/to/logfile.log`
- Check the source code.
- All project memory entries must be provided as TOML-formatted strings.
- Always include at least the following top-level fields:
- `category` (e.g., "Task Management", "Project Status", etc.)
- `project` (project name)
- `timestamp` (ISO 8601 format, e.g., "2025-04-29T16:00:00+09:00")
- Use the `run_id` parameter to logically group related entries.
- Recommended format:
- Example:
- Always add a `[metadata]` TOML table to enhance search and filtering.
- Example:
- Use `immutable = true` to prevent updates.
- Use `expiration_date = "YYYY-MM-DD"` to set expiry.
- Be consistent with field names and structure.
- Always include `project` and `timestamp`.
- Use clear, descriptive tags and metadata.
- Leverage TOML comments for human/AI hints if needed.
- The following is just sample, find the best by yourself !!
- **Standard Metadata**: Always include the project name and timestamp.
- **Data Format**: Use TOML for all entries, and include a `[metadata]` table.
- **Context Management**: Use `run_id` hierarchically to maintain information relevance.
- **Search Efficiency**: Consistent metadata and structure improve search efficiency.
- **Enhance the `add_project_memory` Method**:
- Update documentation strings: Improve usage examples and parameter descriptions.
- Error handling: Provide more detailed error information.
- Response format: Explicitly state the parameters used.
- **Update Custom Instructions**:
- Enrich template examples.
- Clarify recommended usage of `run_id` (introduce hierarchical structure).
- Standardize metadata schema.
- Provide practical usage examples.
SECURITY
An MCP listing is not a security review
An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.