feat(neo4j): migrate mcp-neo4j from external submodule to built-in plugin

[amondnet]

Summary

• Remove external-plugins/mcp-neo4j git submodule (was pointing to amondnet/mcp-neo4j fork)
• Add plugins/neo4j/.claude-plugin/plugin.json as a built-in plugin using uvx to run all four Neo4j MCP servers directly from PyPI
• Update marketplace.json source from {"source": "github", "repo": "amondnet/mcp-neo4j"} to "./plugins/neo4j"
• Update release-please-config.json to track plugins/neo4j releases
• Update README.md: move MCP Neo4j entry from External Plugins to Built-in Plugins section
• Update CLAUDE.md: remove mcp-neo4j from external submodule list

MCP Servers included

Server	PyPI package
mcp-neo4j-cloud-aura-api	mcp-neo4j-aura-manager
mcp-neo4j-cypher	mcp-neo4j-cypher
mcp-neo4j-data-modeling	mcp-neo4j-data-modeling
mcp-neo4j-memory	mcp-neo4j-memory

Motivation

Since all Neo4j MCP servers are available as PyPI packages runnable via uvx, maintaining a git submodule fork is unnecessary overhead. Moving to a built-in plugin simplifies the setup and removes a dependency on the fork.

---

Summary by cubic

Migrates mcp-neo4j from an external submodule to a built-in plugin that runs all four Neo4j MCP servers from PyPI via uvx. This simplifies setup, removes the fork dependency, and enables release tracking.

• Migration
  • Removed external-plugins/mcp-neo4j; added plugins/neo4j/.claude-plugin/plugin.json to run aura-manager, cypher, data-modeling, and memory via uvx.
  • Updated marketplace source to ./plugins/neo4j and added plugins/neo4j to release-please-config.json.
  • Docs: moved Neo4j to Built-in Plugins and updated install examples.
  • Adoption: no user action needed; keep using /plugin install mcp-neo4j@pleaseai. Ensure uvx is available in the environment.

^{Written for commit fd2a6a4. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
claude-code-plugins	Ready	Preview, Comment	Mar 5, 2026 5:48am

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the integration of the Neo4j plugin by transitioning it from an external git submodule to a built-in component. This change simplifies the project's dependency management by leveraging PyPI packages for the Neo4j MCP servers, reducing overhead and making the plugin easier to maintain and use within the system. The necessary configuration and documentation have been updated to reflect this architectural shift.

Highlights

• Plugin Migration: The Neo4j plugin has been migrated from an external git submodule (external-plugins/mcp-neo4j) to a built-in plugin located at plugins/neo4j.
• Simplified Dependency Management: The Neo4j MCP servers are now run directly from PyPI packages using uvx, eliminating the need for a git submodule fork and simplifying setup.
• Configuration Updates: The marketplace.json has been updated to reflect the new source path for the Neo4j plugin, and release-please-config.json now tracks releases for the built-in plugins/neo4j.
• Documentation Alignment: The README.md and CLAUDE.md files have been updated to correctly categorize the Neo4j plugin as a built-in component and remove references to its former external submodule status.

Changelog

• .claude-plugin/marketplace.json
  • Updated the 'source' field for the 'mcp-neo4j' entry to point to the new built-in plugin path './plugins/neo4j'.
• .gitmodules
  • Removed the entry for the 'external-plugins/mcp-neo4j' submodule.
• CLAUDE.md
  • Removed the 'mcp-neo4j' entry from the external plugins directory structure.
  • Removed the 'external-plugins/mcp-neo4j' entry from the list of external submodules.
• README.md
  • Removed the 'MCP Neo4j' section from the 'External Plugins' list.
  • Added a new 'MCP Neo4j' section to the 'Built-in Plugins' list, updating its source to 'plugins/neo4j'.
  • Removed the old '/plugin install mcp-neo4j@pleaseai' command from the 'External Plugins' installation examples.
  • Added the '/plugin install mcp-neo4j@pleaseai' command to the 'Built-in Plugins' installation examples.
• external-plugins/mcp-neo4j
  • Removed the 'external-plugins/mcp-neo4j' submodule entirely.
• plugins/neo4j/.claude-plugin/plugin.json
  • Added a new plugin definition file for 'mcp-neo4j', specifying its version, description, and the uvx commands for its four MCP servers (cloud-aura-api, cypher, data-modeling, memory).
• release-please-config.json
  • Added a new configuration entry for 'plugins/neo4j' to track its releases, specifying 'simple' release type, 'neo4j' component, and linking its version to the '.claude-plugin/plugin.json' file.

Activity

• No human activity (comments, reviews) has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully migrates the mcp-neo4j plugin from an external git submodule to a built-in plugin, simplifying the repository structure and dependency management. The changes across marketplace.json, .gitmodules, README.md, and release-please-config.json are all consistent with this goal. I have one suggestion to enhance the new plugin.json file by adding standard metadata fields, including the author field which should credit the upstream organization as per repository guidelines, to improve its completeness and align it with documented best practices.

[cubic-dev-ai]

No issues found across 7 files