Pocketnook MCP server

pocketnook MCP server

Deploy a repository to a private URL without leaving the agent that wrote it.

> deploy this somewhere private

  owner/studio-board is deployed: https://pocketnook.dev/s/nook-…/
  It is private — only you can open it until you share it. (static, 42 files)

The deploy step belongs inside the tool where the software is being written, which is both the distribution and the product.

Install

1. Get a token. Sign in at pocketnook.dev, open Agent access on the home page, and create one. It is shown once.

2. Add the server.

claude mcp add pocketnook \
  --env POCKETNOOK_TOKEN=pnka_… \
  -- npx -y @pocketnook/mcp

Or, from a checkout of this repository, point at the entry directly:

claude mcp add pocketnook \
  --env POCKETNOOK_TOKEN=pnka_… \
  -- node /absolute/path/to/apps/mcp/bin/pocketnook-mcp.mjs

The server has no dependencies and runs on Node 22.18 or newer — the floor package.json declares, so an older Node warns rather than silently half-works. Any MCP client works; the commands above are Claude Code's.

3. Optionally add the skill, which teaches the agent the things the tool descriptions cannot say on their own — that a deploy builds what is pushed rather than what is on disk, and that sharing does not notify anyone:

cp -r skills/pocketnook ~/.claude/skills/

Or install both at once, as a Claude Code plugin

This repository is also a Claude Code plugin: the skill above and the MCP server, wired together, with the token read from your environment.

claude plugin marketplace add shotintoeternity/pocketnook-mcp
claude plugin install pocketnook@pocketnook-mcp

Then check it: claude plugin details pocketnook@pocketnook-mcp should report one skill and one MCP server.

That check is worth running, because the obvious one does not cover it. claude plugin validate reads plugin.json and the skills, and does not read .mcp.json at all — it reports ✔ Validation passed on a plugin whose .mcp.json is not even parseable JSON. details is what counts the components, and it reports MCP servers (0) for exactly that plugin.

The marketplace manifest and the plugin manifest are both here, in one repository, because a plugin-only repository is not installable: plugin marketplace add fails with Marketplace file not found, and plugin install answers not found in any configured marketplace. .claude-plugin/marketplace.json lists this repository's root as its one plugin.

Configuration

Tools

The two deploys, and why they are two tools

deploy builds what GitHub has. deploy_directory uploads what is on the disk, including uncommitted work, and needs no repository at all. It exists because the person an agent is writing for may never make a push.

They are not merged into one tool with a heuristic, because the heuristic has two silent failure modes: guess towards the repository and an afternoon of work is quietly not deployed; guess towards the directory and half-finished local edits go live. Neither announces itself, which is what makes the guess unaffordable: a wrong answer that stays quiet is worse than a question.

What is deliberately absent

Shortened. The full README is on GitHub.