Add plugin: memorysync 1.0.0 - long-term user memory tools

[mdhaseeb343q-pixel]

Plugin Submission

Plugin information

• Author: memorysync
• Plugin name: memorysync
• Version: 1.0.0
• Source repository: https://github.com/memorysyncio/memorysync-dify
• Contact: support@memorysync.io

Submission type

• New plugin
• Version update

What changed

MemorySync (https://memorysync.io) gives Dify apps cross-conversation, per-user long-term memory — the thing conversation variables and the knowledge base don't cover. Four curated tools:

• Recall Context — a prompt-ready block of the user's relevant memories, for wiring into any LLM node
• Remember — stores a fact/turn with deterministic idempotency (node re-runs converge on one row)
• Search Memories — scored JSON list, tolerant parsing, capped at 25 results
• Forget Memory — deletes exactly ONE memory by id, loudly; there is deliberately no delete-everything tool

User identity auto-resolves from Dify's runtime user (with an optional per-call override), sessions are recorded as dify::<conversation_id>, calls run under a 10s budget with structured branchable error JSON, and quota limits degrade gracefully. Credential validation checks the API key against the live API on save.

Docs: https://docs.memorysync.io/guides/dify

Risk level

• Low risk
• Medium risk
• High risk

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, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

The plugin sends user-provided conversation text (the content passed to Remember, and query strings for Recall/Search) to the MemorySync API over HTTPS (api.memorysync.io, or a user-configured base URL), authenticated by the customer's own API key — this is the plugin's documented purpose. No command or code execution, no SQL, no SSH/SFTP, no file operations, no browser automation, and no arbitrary URL fetching (the only configurable endpoint is the base URL credential, intended for staging). It does not target health, financial, biometric, or children's data; what is stored is whatever facts the app's users choose to remember. Privacy policy ships as PRIVACY.md and is referenced from manifest.yaml.

Local validation

• dify-plugin plugin package ./memorysync -o memorysync-1.0.0.difypkg (CLI 0.6.10) — packaged successfully; archive verified to contain only runtime files (17 entries, no caches/secrets/binaries).
• pytest tests — 32 checks driven through the dify_plugin SDK's offline harness (Tool.from_credentials): the user-resolution ladder, idempotent Remember, capped scored Search, loud single-id Forget, credential validation, quota modes, and manifest/provider/tool YAML schema sanity.
• Live end-to-end run of all four tools against the production MemorySync API (store → recall → search → forget, with cleanup verified against the raw list endpoint).

Reviewer notes

Testing limitation, per the checklist: the plugin was validated through the official dify_plugin SDK's offline harness plus a live run against the production MemorySync API, not on a running Dify Community Edition / Dify Cloud installation. The harness drives the same Tool entrypoints Dify invokes at runtime. Happy to address any findings from a marketplace-side installation test.

[mdhaseeb343q-pixel]

Template filled in - Medium risk selected (the plugin sends user content to an external HTTPS service, per the risk classification). Also repackaged the .difypkg on this branch: added the plugin README, stripped __pycache__ directories, and aligned the internal client version with the manifest (1.0.0). Source repository: https://github.com/memorysyncio/memorysync-dify