Skip to content

MCP registry: describe recording + proof of work #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
baransu merged 3 commits into from
Nov 3, 2026
Merged

MCP registry: describe recording + proof of work #30

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
67700da
MCP registry: describe recording and proof of work
cursoragent Nov 3, 2026
6febf98
MCP registry: match live 1.36.3 and drop record claim
cursoragent Nov 3, 2026
4d904f8
MCP registry: set listing description to recordings as context
cursoragent Nov 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
- Added `add-voiceover`: voice a spoken script line by line and lay each line under its moment in any video, with a WebVTT subtitle file. The agent asks which voice to use: ElevenLabs (`eleven_v4`), Kokoro (free, local, a one-time 340 MB download), the OS voice, or the team's own command. A video with its own sound keeps it under the narration, lowered together with it only if the mix would clip. The script runs on Node 22 or later with nothing to install. No Jam account needed.
- Added `record-terminal-proof`: record a terminal run with asciinema and render a GIF for the pull request, plus an MP4 when needed. No Jam account needed.
- `scripts/check.mjs` counts Jam mentions in an unbranded skill in prose only, so a "With Jam" line can show the command.
- `server.json` follows Jam MCP 1.27.1, the version production serves.
- `server.json` follows Jam MCP 1.36.3, the version production serves. The registry description is "Jam recordings (video, console, network) as context and proof of work for your coding agent.", because registry search matches only name and description.
- `jam-fix` hands a narrated walkthrough that asks for several changes to `jam-to-tasks`, when installed, instead of diagnosing it as one bug.
- Added `jam-to-tasks`: turn a narrated Jam into a numbered list of every change asked for, each tied to its moment, frame and quote, then work through the list.
- Added `jam-to-ticket`: file a Jam as a ready-to-work issue in Linear, GitHub Issues or Jira, after checking the Jam's own integrations and the tracker for an existing ticket.
Expand Down
4 changes: 2 additions & 2 deletions server.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"name": "dev.jam/jam",
"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.",

@devin-ai-integration devin-ai-integration Bot Nov 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 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.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

"version": "1.36.3",
Comment thread
baransu marked this conversation as resolved.
Resolved
"websiteUrl": "https://jam.dev/mcp",
"repository": {
"url": "https://github.com/jamdotdev/skills",
Expand Down
Loading