PasteHTML MCP server
2026년 11월 11일 커밋OAuth 인증을 통해 AI 클라이언트가 HTML 및 Markdown 페이스트를 폴더별로 게시, 업데이트 및 관리할 수 있게 합니다.
다른 이름 AliOsm/pastehtml.dev, pastehtml-dev
- 스타
- 11
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 1.1.0
- 마지막 커밋
- 2026년 11월 11일
- 라이선스
- —
PasteHTML MCP란?
PasteHTML은(는) MCP server입니다. OAuth 인증을 통해 AI 클라이언트가 HTML 및 Markdown 페이스트를 폴더별로 게시, 업데이트 및 관리할 수 있게 합니다.
프로젝트 README에서 생성된 요약
PasteHTML MCP server 정보
PasteHTML은 AI 에이전트와 개발자가 HTML 및 Markdown 콘텐츠를 게시, 업데이트 및 관리할 수 있는 방법을 제공합니다. 사용자는 파일을 커스텀 서브도메인이나 비밀번호 보호 기능이 있는 공유 링크로 변환할 수 있습니다. 이 서비스는 문서를 자체 오리진의 실제 페이지로 호스팅하도록 설계되어, 다른 콘텐츠와 격리된 상태에서도 스크립트와 로컬 스토리지가 올바르게 작동하도록 보장합니다.
AI 클라이언트를 사용하는 개발자의 경우, 이 서버를 HTTP를 통해 원격 MCP server로 연결할 수 있습니다. 사용자는 수동으로 API key를 관리하는 대신 OAuth 2.1을 사용하여 브라우저를 통해 연결을 인증합니다. 연결이 완료되면 에이전트는 폴더 생성, 이름 변경, 기존 페이스트 업데이트 등 계정 전체를 관리할 수 있습니다. 시스템에는 서브도메인 설정이나 조회 통계 확인과 같이 페이스트의 생명주기를 관리하는 특정 도구가 포함되어 있어, 렌더링된 디자인 문서나 구현 계획을 전달해야 하는 에이전트에게 특화된 도구로 활용됩니다.
활용 사례
- 1디자인 문서 게시AI 에이전트가 새로운 HTML 페이스트를 생성하여 사용자에게 시각적인 구현 계획을 공유할 수 있습니다.
- 2콘텐츠 폴더 정리개발자가 AI에게 관련 HTML 페이스트를 특정 프로젝트 폴더로 그룹화하도록 지시할 수 있습니다.
- 3기존 공유 링크 업데이트에이전트가 기존 URL을 변경하지 않고 기존 페이스트의 내용을 덮어쓸 수 있습니다.
- 4문서 참여도 모니터링사용자가 AI 클라이언트에게 페이스트의 조회 횟수에 관한 분석 데이터를 요청할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
PasteHTML MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 PasteHTML MCP 설치
$ claude mcp add --transport http pastehtml-dev https://pastehtml.dev/mcpCursor에 PasteHTML MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"pastehtml-dev": {
"url": "https://pastehtml.dev/mcp"
}
}
}VS Code에 PasteHTML MCP 설치
.vscode/mcp.json
{
"servers": {
"pastehtml-dev": {
"type": "http",
"url": "https://pastehtml.dev/mcp"
}
}
}VS Code CLI에 PasteHTML MCP 설치
$ code --add-mcp '{"name":"pastehtml-dev","type":"http","url":"https://pastehtml.dev/mcp"}'Codex에 PasteHTML MCP 설치
$ codex mcp add pastehtml-dev --url https://pastehtml.dev/mcpCodex config.toml에 PasteHTML MCP 설치
~/.codex/config.toml
[mcp_servers.pastehtml-dev] url = "https://pastehtml.dev/mcp"
Gemini CLI에 PasteHTML MCP 설치
$ gemini mcp add -s user --transport http pastehtml-dev https://pastehtml.dev/mcpGemini settings.json에 PasteHTML MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"pastehtml-dev": {
"url": "https://pastehtml.dev/mcp",
"type": "http"
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능aliosm/pastehtml.dev is public and reachablegithub.com/aliosm/pastehtml.dev ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)No license결함 발견
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-11github.com/aliosm/pastehtml.dev ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기pastehtml.dev
Share HTML pages in seconds. Drop an HTML file, get a private link your friends can open, preview, and view the source of. Anonymous publishing still works, and accounts add folders, custom subdomains, view counts, browser-based re-upload updates, and account API keys for agent publishing into folders.
How it works
- Drag and drop (or browse for) an
.html/.htmfile up to 2 MB. - The document is published at
https://<token>.pastehtml.dev/— or at a claimed custom subdomain likehttps://launch-plan.pastehtml.dev/— with an inspector page (copy link, preview, highlighted source) at/p/<token>. Tokens are random 32-character lowercase-alphanumeric IDs (~165 bits of entropy — lowercase because they double as subdomains, and browsers lowercase hostnames), so random links are private unless shared. - Pastes can be password-protected. Locked pastes require the password before the inspector page, raw bytes, rendered preview, or live subdomain are served.
- Signed-in users can save pastes into folders, see view counts, and re-upload a
replacement
.html/.htmfile without changing the share link. Pastes can never be deleted. API-created update tokens still work for token-based automated updates. - The share page offers a live preview (with an in-site fullscreen mode) and a Rouge-highlighted source view.
- Every paste is served as a real page from its own origin —
https://<token>.pastehtml.dev/— so scripts and localStorage work (review-progress checklists persist) while staying fully isolated from other pastes and from the app itself. The path-based/p/<token>/rawendpoint returns the paste's exact bytes astext/plain— a byte-exact copy for programmatic clients, immune to any CDN HTML rewriting in transit — while/p/<token>/renderserves the same bytes astext/htmlinside a CSPsandbox.
Agent API
Publish without a browser — ideal for AI agents that produce design documents
or implementation plans and want to hand back a share link. Anonymous publishing
still works with no credentials; signed-in users can also create account API keys
at /api_keys so an agent can publish into their account and target folders.
# Multipart upload
curl -F "file=@plan.html" https://pastehtml.dev/api/pastes
# Or stream the HTML straight from a pipe
curl --data-binary @plan.html -H "Content-Type: text/html" \
"https://pastehtml.dev/api/pastes?filename=plan.html"
Anonymous creation returns 201 with
{ token, title, custom_subdomain, folder, owner, account_paste, password_protected, views_count, live_url, url, raw_url, render_url, markdown_url, update_token }
(or 422 with { errors }). Account-key creation returns the same paste fields
but omits update_token; update account-owned pastes with the account key so
revoking the key stops that agent's future access. Add password=<secret> (or
custom_subdomain=<name>, which requires an account key) to creation/update
requests; send clear_password=1 on updates to remove a paste password. Fetch raw_url to read a paste's exact bytes
back (text/plain, never rewritten in transit).
Account API keys for agents
A signed-in user can open API keys from the dashboard, create a key, and give
that secret to an agent. Use it as either Authorization: Bearer pht_... or
X-PasteHTML-API-Key: pht_.... When a valid account key is present on
POST /api/pastes, the paste is owned by that user and appears in their
dashboard. Folder targeting is account-only:
curl -H "Authorization: Bearer $PASTEHTML_API_KEY" \
--data-binary @plan.html -H "Content-Type: text/html" \
"https://pastehtml.dev/api/pastes?filename=plan.html&folder_name=Roadmap"
Use folder_name=<name> to find or create a folder under that account,
folder_id=<id> to target an existing folder, and clear_folder=1 on updates
to move a paste back to All pastes. Keys can also be scoped to a default folder
when created; scoped keys always publish there, can update only pastes already
in that folder, reject folder overrides, only list that folder through the folder
API, and cannot create unrelated folders. Scoped keys are revoked automatically
if the folder is deleted. Unscoped agents can discover existing folder IDs with:
curl -H "Authorization: Bearer $PASTEHTML_API_KEY" \
https://pastehtml.dev/api/folders
Unscoped keys can create folders with either nested form params
(folder[name]=Roadmap) or a simple top-level name=Roadmap, whichever is
easier for the client. Folder-scoped keys receive 403 on folder creation.
An account key can update pastes owned by that account, while the per-paste
update_token flow keeps working as long as the paste stays anonymous. If an
agent needs to claim an anonymous paste into an account, send the account key in
Authorization: Bearer ... and the paste secret separately as
X-Update-Token: .... Claiming is one-way: afterward the account key is the
paste's update credential and the old token stops working.
The update_token is revealed exactly once — the server stores only a digest —
and authorizes any number of in-place updates while the paste remains anonymous:
curl -X PATCH -H "Authorization: Bearer $UPDATE_TOKEN" \
-F "file=@plan.html" https://pastehtml.dev/api/pastes/$TOKEN
Updates accept the same two body forms as creation and return 200 with the
refreshed { token, title, custom_subdomain, folder, owner, account_paste, password_protected, views_count, live_url, url, raw_url, render_url, markdown_url },
403 for a wrong or missing update token or an account key that does not own the paste,
and 404 for an unknown paste. Paste publish/update endpoints are rate limited per IP at 20 requests per minute and 1,000 per day; folder API endpoints also require an account key and are rate limited per IP.
Agents discover all of this on their own: the full integration guide lives at
/llms.txt (also pointed to from the
homepage, both visibly and in an HTML comment for raw fetchers). Telling an
agent "publish this on pastehtml.dev" is enough.
MCP server
For agents that speak the Model Context Protocol,
pastehtml.dev is also a remote MCP server at https://pastehtml.dev/mcp
(Streamable HTTP). Instead of a pht_ key, the agent authorizes once through
your browser over OAuth and then works inside your account — the same folders,
view counts, and permanent pastes as the dashboard.
# Claude Code
claude mcp add --transport http pastehtml https://pastehtml.dev/mcp
# Codex
codex mcp add pastehtml --url https://pastehtml.dev/mcp
On first use the client opens a browser consent screen; approve it and the
agent is connected — no key to copy or store. Authorization is OAuth 2.1 with
PKCE and RFC 7591 Dynamic Client Registration, scoped to mcp:read,
mcp:pastes:write, and mcp:folders:write. Review or revoke connected
agents any time under Connected agents in the dashboard.
Ten tools are exposed (pastes are permanent — there is no delete-paste tool):
create_paste— publish a new HTML or Markdown paste, optionally into a folder.update_paste— republish an existing paste's content (overwrites it in place).configure_paste— change a paste's password, custom subdomain, or folder.get_paste— fetch one paste's metadata, URLs, and stored content.get_paste_stats— aggregate view analytics for a paste.list_pastes— page through the account's pastes, optionally filtered by folder.list_folders— list folders with their paste counts.create_folder— create a new, empty folder.rename_folder— rename a folder.delete_folder— delete a folder (its pastes survive, unfiled).
Dynamic Client Registration can be switched off in production with the
MCP_DYNAMIC_REGISTRATION_DISABLED environment variable (any already
pre-registered clients keep working). Smoke-test a deployment by fetching its
discovery document:
curl https://pastehtml.dev/.well-known/oauth-protected-resource
Stack
- Ruby on Rails 8.1 · PostgreSQL · Hotwire (Turbo + Stimulus)
- Tailwind CSS v4 (cssbundling) · esbuild (jsbundling) · Yarn 4
- Tooling via mise, PostgreSQL via Docker Compose
- Comic-book design: Bangers display type over Inter, halftone textures, ink-outlined panels with hard offset shadows
- Installable PWA: manifest + minimal network-first service worker with an offline fallback page (pastes themselves are never cached)
- SEO via meta-tags (OG/Twitter cards with a branded OG image, canonical, noindex on paste pages) and comic-styled static error pages
Development
mise run dev # starts postgres (docker), installs deps, prepares db, runs bin/dev
Or step by step:
mise run docker:start # postgres on localhost:5435
mise run deps # bundle install + yarn install
mise run db:prepare
bin/dev # rails server + js/css watchers on port 3000
Tests and lint
mise run test # rails test
mise run lint # rubocop + brakeman
Deployment
Deploys with Kamal from GitHub Actions (the
"Kamal Run" workflow) to a single server: the app container plus a postgres
18 accessory. db/production.sql creates the Solid Cache/Queue databases on
the accessory's first boot. Pastes are served from <token>.pastehtml.dev
subdomains, so the proxy routes the wildcard with a Cloudflare Origin CA
certificate (wildcards can't get Let's Encrypt certs over HTTP-01).
One-time setup:
- Cloudflare (free plan): add a proxied
Arecord forpastehtml.dev,www, and a proxied wildcard*record, all pointing at the server. Set SSL/TLS mode to Full (strict). Create an Origin Server certificate forpastehtml.dev, *.pastehtml.devand keep the PEM pair. - Repository Actions secrets:
SERVER_IP,SSH_PRIVATE_KEY(root access to the server),RAILS_MASTER_KEY(fromconfig/master.key),POSTGRES_PASSWORD,CLOUDFLARE_ORIGIN_CERTIFICATEandCLOUDFLARE_ORIGIN_KEY(the Origin CA PEM pair). The container registry (ghcr.io) authenticates with the workflow's ownGITHUB_TOKEN. - Run the Kamal Run workflow with the command
setuponce (provisions postgres + proxy), then withdeployfor every release.
For local runs of kamal commands, put the Origin CA pair in
.kamal/certs/origin.pem / origin-key.pem (gitignored), export
SERVER_IP and POSTGRES_PASSWORD, and remove the GHA builder cache block
from config/deploy.yml if you need to build the image locally.
PasteHTML MCP 질문
PasteHTML MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http pastehtml-dev https://pastehtml.dev/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
PasteHTML MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
MCP server를 어떻게 인증하나요?
브라우저를 통한 OAuth로 에이전트가 한 번만 인증하면 되므로, API key를 수동으로 복사하거나 저장할 필요가 없습니다.
MCP server를 사용하여 페이스트를 삭제할 수 있나요?
아니요, 모든 페이스트는 영구적이므로 서버에 삭제 도구가 포함되어 있지 않습니다.
MCP server에서 어떤 도구를 사용할 수 있나요?
페이스트 생성, 업데이트, 설정 및 폴더 관리, 페이스트 통계 확인을 포함한 10가지 도구를 제공합니다.