Skip to content

feat(claude-code): publish the EverMe plugin for the Claude plugin directory - #25

Merged
alwaysday1 merged 1 commit into
mainfrom
chore/publish_claude_directory_plugin
Nov 11, 2026
Merged

alwaysday1 merged 1 commit into
mainfrom
chore/publish_claude_directory_plugin

Conversation

@alwaysday1

Copy link
Copy Markdown
Collaborator

What

Adds the EverMe plugin for the Claude plugin directory:

  • plugins/claude-directory/: the plugin. Configuration and Markdown only, no scripts and no dependencies.
  • .claude-plugin/marketplace.json: a marketplace manifest at the repository root, so the repository can be added with /plugin marketplace add EverMind-AI/EverMe.

How it works

The hooks are of type mcp_tool and call the EverMe MCP server at https://api.everme.evermind.ai/mcp:

  • UserPromptSubmit: recall memories for the prompt (mem_search with format: "hook"), and save the prompt.
  • PostToolUse and PostToolUseFailure: save the tool call and its result or error.
  • Stop: save the final reply and trigger extraction.

The user signs in with OAuth from /mcp. .mcp.json has no headers and no credential.

Not changed

  • plugins/everme/ (the Codex plugin) and .agents/plugins/marketplace.json are already at 0.7.10.
  • plugins/claude-code/ is unchanged.

Checks

  • claude plugin validate plugins/claude-directory --profile directory: passed.
  • claude plugin validate .: passed.
  • No executable files in plugins/claude-directory/.
  • Private key check and internal reference check from ci.yml, run locally: passed.

🤖 Generated with Claude Code

…rectory

Add plugins/claude-directory and a root .claude-plugin/marketplace.json, so
the repository can be added as a Claude Code marketplace and submitted to
the Claude plugin directory.

The plugin has configuration and Markdown only. Its hooks are of type
mcp_tool and call the EverMe MCP server at https://api.everme.evermind.ai/mcp:
recall before each prompt, and save the prompt, each tool call that ends or
fails, and the final reply. The user signs in with OAuth from /mcp.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alwaysday1
alwaysday1 merged commit be7bba4 into main Nov 11, 2026
7 checks passed

@gloryfromca gloryfromca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blockers; suggestions only, and they are marked inline.

I reviewed the complete PR diff against 89f20a2, the repository rules in AGENTS.md, the existing Claude Code plugin and memory-MCP contracts, the current official Claude plugin/hook/marketplace documentation, and the branch history. I also checked backward compatibility and architecture constraints: this is additive, keeps the stable mem_* tool names, uses the required plugin-scoped MCP server name, and documents the full prompt/tool/result data flow and lack of secret redaction. No existing tests were weakened.

Verification: Claude Code 2.1.322 strict validation passed for both the root marketplace and plugins/claude-directory; npm ci succeeded; all plugin workspace tests passed with TMPDIR moved off the full system /tmp; and npm audit --audit-level=moderate reported 0 vulnerabilities. GitHub CI is also green. The only note is the unused icon declaration below; it does not block merge.

"homepage": "https://everme.evermind.ai",
"repository": "https://github.com/EverMind-AI/EverMe",
"license": "Apache-2.0",
"privacyPolicyUrl": "https://everme.evermind.ai/legal/privacy",

@gloryfromca gloryfromca Nov 11, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blockers; suggestions only, and they are marked inline.

The new 1024×1024 icon is not referenced anywhere. The Anthropic directory reads supplied branding only through the manifest icon field, so as written the asset is dead and the listing will not use it. Consider adding "icon": "./.claude-plugin/icon.png" here.

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.

3 participants