Rewrite MCP server page for the 10-tool upload architecture - #59
Merged
Conversation
Covers list_job_types, upload_media's session flow, complete_upload, and get_upload, none of which were documented before. Leads with the zero-key OAuth connect, adds a phone walkthrough for clients with no filesystem and a shell-agent walkthrough showing the upload-then-chain flow, and moves the local npx server to its own power-user section.
a-essawy
added a commit
to rendobar/mcp
that referenced
this pull request
Jul 26, 2026
The registry entry is published by a step that is continue-on-error, so anything wrong with it degrades to a warning in a log nobody reads. That is how the docs restructure in rendobar/docs#59 went unnoticed here: websiteUrl still pointed at /docs/mcp/, which now answers 405, and that URL is live in published registry version 1.7.1. The page moved to /docs/mcp-server. package.json homepage carried the same stale value. Adds scripts/check-registry-entry.mjs, run as its own CI job on every PR. It cross-checks the fields that break a publish after npm has already gone out - server.json name against package.json mcpName, the three release-please version fields against each other, the package identifier - enforces the registry's 100-char description cap, asserts a remotes entry exists, and fetches every URL in the entry. The icon URLs are the fragile ones: they resolve to the brand CDN, which is synced from a different repo, so nothing in this repo would otherwise notice them going dead. Also adds a post-publish verification step to release.yml that polls the registry until the released version is present and marked latest, and fails the job if it never is. That failure routes into the existing rollback-on-failure job, which opens an issue. npm has already published by then, so the fix is always forward. The script takes no dependencies. Node has fetch, and the failures that actually occur here are cross-file drift and dead URLs rather than exotic schema violations, which the post-publish check catches anyway.
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
1 participant
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.
Documents the new remote MCP surface: OAuth one-liner install first, 10-tool table, phone upload walkthrough (tokenized page), shell-agent walkthrough (presigned PUT + { job } chaining, ffmpeg inputs only), local @rendobar/mcp as the power-user path. Matches prod as deployed today. Validators pass; mint CLI checks skipped locally (Node 25 unsupported) and will run in CI.