Repository navigation
Prepare the MCP registry manifest + submission path (fixes #21) - #26
Merged
Merged
Conversation
Issue mienetic#21 asked for a PR adding Mnema to the old modelcontextprotocol/servers README list. That process has been retired (that repo now hosts only reference servers); the current mechanism is modelcontextprotocol/registry — a live API servers publish to via mcp-publisher, using a server.json manifest validated against the published JSON Schema. There's no PR to open and no category field anymore. Adds: - packages/mnema-python/server.json: schema-valid manifest (name, description, version, repository incl. monorepo subfolder). Validated against https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json with jsonschema, plus the registry's own name/version regexes. - README.md: new "MCP Registry" section explaining current status, the process change, and the remaining steps (this is a maintainer-only action — the io.github.mienetic namespace is GitHub-OAuth-verified). - packages/mnema-python/README.md: pre-added the mcp-name ownership marker PyPI verification will look for once the package is published there (release.yml already states Mnema isn't on PyPI yet, so no packages entry is included in server.json — inventing one would describe an artifact that doesn't exist). No submission is made to any external registry; that remains the maintainer's act. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
|
Clean and correct — the manifest follows the MCP schema exactly, and the README verification marker is well-documented. Thanks for handling this so we're ready to submit to the registry. Merging! 🧠 |
mienetic
pushed a commit
that referenced
this pull request
Jul 19, 2026
…registry) Comprehensive doc update after merging PRs #25-#28: README: - Features: 5 backends, dashboard, browser ext, Auto Dream, 142+51 tests - Project layout: add dashboard/, pgvector, lancedb, eval_harness, dream - CLI section: add 'mnema dashboard' + 'mnema serve' - Backend table: add pgvector + LanceDB rows - Roadmap summary: 'Shipped' now lists all done items including 5 backends - Credits: all 5 contributors named CHANGELOG [0.3.0]: - pgvector backend (@Adiiiipawar, #25) - LanceDB backend (@Oneshot1123, #27) - Web dashboard (@NEMEZIZ1234, #28) - MCP registry manifest (@Nitjsefnie, #26) ROADMAP Phase 2: pgvector/LanceDB/dashboard/registry all → ✅ done docs/architecture.md: - New Dashboard layer section - Interfaces table: 5 → 6 (add Web dashboard) docs/deployment.md: - New section 5: Dashboard mode (mnema dashboard) docs/backends.md: - New pgvector section (asyncpg, parameterized, <=> cosine) - Extras table: add pgvector, lancedb, ollama, api
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
2 participants
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.
#21's described flow turned out to be stale, so this PR prepares the current path and documents the change rather than following the outdated one:
modelcontextprotocol/serversno longer takes directory PRs — its README now houses only the steering group's reference servers and points atregistry.modelcontextprotocol.io. The real path today is aserver.jsonmanifest published via themcp-publisherCLI (GitHub OAuth). The current schema (2025-12-11) has no category field at all — discovery is search-based, so the issue's "memory/RAG category" ask has no target anymore.What's in:
packages/mnema-python/server.json— validated against the fetched2025-12-11schema (and cross-checked against the registry's own internal validator copy + its Go name/version regexes). Every field derives from the repo: name from the GitHub namespace convention, version frompyproject.toml, repository id fetched live,subfolderpointing at the actual server in this monorepo.packages/mnema-python/README.md: the inertmcp-nameownership-verification marker, format checked against the registry's boundary-matching code.One honest gap, deliberately not papered over: the manifest has no
packagesentry, because there's nothing to truthfully cite — yourrelease.ymlstates Mnema isn't on PyPI, and the registry supports exactly six package registries (npm/pypi/nuget/cargo/oci/mcpb), none of which is a git+installer distribution. A metadata-only manifest is structurally legal (the validators makepackagesoptional), just install-less in the directory until you publish. The README section spells out the order: publishmnema-mcpto PyPI → add thepackagesentry →mcp-publisher login && publish. The publish itself is yours — it lists under your name.CI gates green (ruff clean, 142 pytest passed); none of the three files gitignored (checked explicitly, given #23's history).
Generated by Claude Fable 5 (brief, review), Claude Sonnet 4.6 (implementation)