feat(mcp): list the server in the official MCP Registry - #102
Merged
Merged
Conversation
Add server.json and the mcp-name marker the registry's PyPI ownership check reads from the README. A registry client starts a PyPI server as `uvx --from "PyMemoryEditor[mcp]==X" pymemoryeditor mcp`, by the project name, so `pymemoryeditor mcp [flags]` now runs the MCP server (without Qt), the same as `pymemoryeditor-mcp`. Tests keep server.json, the README marker and the package version in step.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #102 +/- ##
=======================================
Coverage 89.89% 89.89%
=======================================
Files 41 41
Lines 3682 3682
=======================================
Hits 3310 3310
Misses 372 372
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares PyMemoryEditor's MCP server for the official MCP Registry, which directories such as PulseMCP ingest from.
Changes
server.json: the listingio.github.JeanExtreme002/PyMemoryEditor, validated against the 2025-12-11 schema. It's left out of the sdist.<!-- mcp-name: ... -->marker. The registry checks it in the description PyPI shows to confirm the package is ours, so it only counts once a release carries it.pymemoryeditor mcp [flags]runs the MCP server, the same aspymemoryeditor-mcp [flags]. A registry client builds<runtimeHint> <runtimeArguments> <identifier> <packageArguments>, and the identifier has to be the PyPI project, so the only command it can reach ispymemoryeditor, which opened the Qt app. The listing makes it runuvx --from "PyMemoryEditor[mcp]==3.0.1" pymemoryeditor mcp. The subcommand is handled before any Qt import and leaves the server's signal handling alone.pymemoryeditorbecause uvx looks the executable up by its exact name: withPyMemoryEditorit finds nothing on Linux.docs/mcp.mdmentions the subcommand.Tests
tests/mcp_server/test_registry.pychecks that:server.json;server.jsonand the--frompin equal__version__, so the next version bump has to updateserver.jsontoo;main_cli;main_cli([..., "mcp", ...])reaches the server with the flags and never imports PySide6.Without the subcommand the dispatch test fails.
End to end in a clean
python:3.12-slimcontainer,uvx --from "pymemoryeditor[mcp] @ <this wheel>" pymemoryeditor mcp --read-onlycompleted the MCP handshake. It listed 13 tools, sincewrite_valuedrops out under--read-only. flake8 passes, as dotests/mcp_server(733) andtests/app(165).After merging
server.json, which the test enforces) and release it to PyPI.mcp-publisher login githubandmcp-publisher publish.