Skip to content

Add opt-in MemCode Memory plugin - #1

Open
vivekgupta-memcode wants to merge 1 commit into
skalesapp:mainfrom
vivekgupta-memcode:memcode-memory-plugin
Open

vivekgupta-memcode wants to merge 1 commit into
skalesapp:mainfrom
vivekgupta-memcode:memcode-memory-plugin

Conversation

@vivekgupta-memcode

@vivekgupta-memcode vivekgupta-memcode commented Sep 29, 2026 •

Copy link
Copy Markdown

Plugin

What it does, in one sentence: Lets a signed-in user explicitly save, check, search and recall personal MemCode memories from a Skales plugin page.

Why it needs the permissions it declares: The four named MCP tools call the user-configured MemCode remote server. It has no file or Skales shared-memory access. The user connects https://mcp.memcode.in/mcp as server memcode and signs in via Skales' OAuth flow; the page never receives a key or token.

Following skalesapp/skales#312, this adds an optional plugin, leaving Skales' local memory as it is. Nothing reads chat history or uploads data automatically. Saves happen only on the user's button press. MemCode is freemium, as disclosed in the manifest.

Checklist

  • The plugin lives in a public GitHub repository I own.
  • The repository has a plugin.json at the submitted path, and it validates against schema/plugin.schema.json.
  • The id is com.github.<owner>/<slug>, with the owner spelled exactly as the GitHub repository owner.
  • The id is new and does not appear in removed.json.
  • The name does not use "Skales".
  • version is semver and matches a tag or release; minAppVersion is a version I actually tested against. (Tag and app test pending.)
  • description is one factual sentence, no marketing.
  • class describes the plugin's main job.
  • permissions is the smallest set that works. (Awaiting in-app MCP permission test.)
  • No secrets in the repository, no telemetry, no code loaded and executed at runtime.
  • If the plugin is paid or freemium, business says so.
  • I commit to maintaining this plugin: keeping it working against current Skales releases, answering issues in my repository, and telling you when I stop.
  • This PR adds exactly one entry, at the end of plugins.json, and touches nothing else.
  • node scripts/validate.js passes locally. (11 entries, 10 featured, 0 retired ids.)

Co-authored-by: DisturbedCrow <277257760+DisturbedCrow@users.noreply.github.com>
@vivekgupta-memcode
vivekgupta-memcode marked this pull request as ready for review September 29, 2026 15:12
@talentsache

Copy link
Copy Markdown
Member

Thanks, the page itself looks clean. Before we merge: (1) please tag/release 0.1.0 in your repo (CONTRIBUTING #6), (2) test the plugin in Skales 12.9.50 and set minAppVersion to what you tested, (3) drop "memory": "own" if the page doesn't use the plugin store, and confirm whether network is needed when only the MCP tools go online. Then tick the two open boxes and we'll take it in.

@vivekgupta-memcode
vivekgupta-memcode force-pushed the memcode-memory-plugin branch 2 times, most recently from e12814e to 60cdb05 Compare October 20, 2026 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants