Add mcp: pocketnook - #5796
Open
shotintoeternity wants to merge 2 commits into
Open
Conversation
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.
Single-entry submission for
content/mcp/pocketnook.mdx.What it is. An MCP server that deploys a GitHub repository, or the working directory as it is on disk, to a private URL — without leaving the agent that wrote the code. Only the owner can open the URL until they share it by GitHub username; there is no public option.
@pocketnook/mcpon npm, zero dependencies, Node 22.18+io.github.shotintoeternity/pocketnook, active in the Official MCP Registryclaude mcp add pocketnook --env POCKETNOOK_TOKEN=pnka_… -- npx -y @pocketnook/mcpFive tools:
deploy,deploy_directory,list_nooks,nook_logs,stop_nook. There is deliberately no delete tool — deleting a nook destroys its grants and secrets, so that stays in the signed-in browser.safetyNotesandprivacyNotesare filled in per SCHEMA.md, including the two that a reviewer should weigh:deploy_directoryuploads uncommitted work on disk, and a deployed app's own outbound traffic is not bounded over HTTPS, because pocketnook declined TLS interception rather than put itself in a position to read every credential a tenant app presents. The product is in beta and asks for synthetic or non-sensitive data only; the limits are stated at https://pocketnook.dev/limits.I submitted through
/submitfirst — its wizard would not keep the Description and Usage snippet fields, so this is the focused single-entry PR the schema describes instead.