Add emem plugin 2.4.0

[kumari-jaya]

Plugin Submission

Plugin information

• Author: vortx-ai
• Plugin name: emem
• Version: 2.4.0
• Source repository: https://github.com/Vortx-AI/emem
• Contact: jaya@vortx.ai

Submission type

• New plugin
• Version update

What changed

Updates the emem plugin package from 2.3.0 to 2.4.0. The package now registers the 16 core tools exposed by https://emem.dev/mcp instead of the full 108 tool catalog. The emem_tools tool remains available for catalog discovery.

The documentation now distinguishes read and write authorization. Reads require no API key, account, token, or client key. Writes require a caller-generated Ed25519 signature supplied in the attester block. Writes do not use an API key.

Risk level

• Low risk
• Medium risk
• High risk

The plugin processes locations and forwards tool arguments to the fixed public endpoint at https://emem.dev/mcp. It does not proxy arbitrary URLs. Agent memory content written through emem is public and persistent unless separately protected as documented in the package privacy policy.

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries.
• The plugin README includes setup steps, usage instructions, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md and manifest.yaml references it.
• All user-facing text is primarily in English.

Security and privacy notes

The plugin forwards tool arguments only to https://emem.dev/mcp. Reads require no credentials. The plugin does not generate, receive through provider configuration, or store private signing keys. Callers that use a write operation must generate and retain their own Ed25519 keypair and provide the signed attester block with that call.

Local validation

Built with Dify Plugin CLI v0.6.10. The package archive passed unzip -t. The packaged manifest reports version 2.4.0 in both required version fields. The provider declares 16 tools, and the archive contains 16 matching YAML definitions and 16 Python implementations.

Reviewer notes

Version 2.3.0 was accepted in #3013. Dify Community Edition and Dify Cloud were not retested locally. The fixed remote MCP endpoint was checked live, and its default tool list contains the same 16 core tools included in this package.

[crazywoola]

CI is green: Pre Check Plugin and PR Risk Label passed.