Repository navigation
MCP registry: describe recording + proof of work - #30
Conversation
Set the registry listing description so search can match recording, browser, and proof of work, and bump server.json to 1.27.2. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Point server.json at the production MCP version and describe what the server can do: read a Jam, or create a Recording Link. MCP cannot record. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Use the exact registry copy for video, console, network, context, and proof of work. Keep version 1.36.3. Co-authored-by: Tomasz Cichocinski <baransu@users.noreply.github.com>
| "title": "Jam", | ||
| "description": "Jam recordings (video, console, network, logs) as context for your coding agent.", | ||
| "version": "1.27.1", | ||
| "description": "Jam recordings (video, console, network) as context and proof of work for your coding agent.", |
There was a problem hiding this comment.
🟡 Browser searches miss the Jam listing
Searching the registry for browser no longer finds Jam; neither its name nor description contains that word. Users seeking its browser Recording Link cannot discover the server through that search.
Learn more
The registry entry describes the remote Jam MCP server. Registry search uses the entry's name and description, so removing browser removes the matching term for a supported browser feature. What the server can do lists Recording Links, while the registry name is only dev.jam/jam.
Example: A developer searches the MCP Registry for browser to find a tool that creates a browser Recording Link. The entry has no matching term, so the developer does not find Jam through that search.
Recommended fix: Include browser in the registry description while staying within the 100-character limit; align the changelog text with the final description.
Was this helpful? React with 👍 or 👎 to provide feedback.
What changed
server.jsondescription is now:Jam recordings (video, console, network) as context and proof of work for your coding agent.(92 characters, under the registry 100-character limit).1.36.3, matching productionMCP_SERVER_VERSIONin jamdotdev/apiofjam (services/graphql-api/src/mcp/transport/version.ts). Registry latest was1.27.1and was stale.CHANGELOG.mdUnreleased note that tracksserver.jsonnow says 1.36.3 and matches this description. Plugin manifests stay at 2.0.0; they do not track the MCP server version.Validated locally with mcp-publisher v1.8.1 (same as
.github/workflows/publish-mcp.yml):./mcp-publisher validate server.jsonpassed. Did not run login or publish.Why
MCP Registry search matches only name and description. The previous description ("Jam recordings (video, console, network, logs) as context for your coding agent.") does not match searches for browser, record, proof of work, or verify. The new copy keeps recordings, video, console, network, and context, and adds proof of work.
Release (maintainer)
Do not ship this from the PR. After merge, push tag
mcp-v1.36.3to trigger the Publish to MCP Registry workflow. A published registry version cannot be changed.