Repository navigation
Package the MCP server as a plugin - #10
Merged
Merged
Conversation
The endpoint has been reachable by `claude mcp add` for a while, but that is a URL somebody has to know and type. A plugin makes it installable, and gives the tools somewhere to carry the things their descriptions cannot. `plugins/htmlcsspdf/.mcp.json` is the whole of the connection: `type: "http"` and the URL. No key, no client id, nothing to fill in — the endpoint answers an unauthenticated call with an RFC 9728 challenge and the client discovers the rest from there, so a config that carried credentials would be describing a handshake that already works without them. The bundled skill is the part worth having. Two facts decide whether a document comes out right, and neither fits in a tool description: page size and margins come from an `@page` rule and nowhere else, and saving runs an element allowlist. The allowlist is the one that bites — it drops rather than escapes, and it has no `<svg>`, so a document that draws its logo in markup saves without it and nothing says why. Both are written down, along with the fact that `update_document` replaces both panes and needs a read first. `.claude-plugin/marketplace.json` makes it installable from this repo, so `/plugin marketplace add afternoon/htmlcsspdf` is the whole of the setup. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
htmlcsspdf | 1a14653 | Commit Preview URL Branch Preview URL |
Sep 01 2026, 10:15 AM |
The plugin existed but the README did not mention it, so the documented way to connect an agent was still to read the MCP section and work out a URL. The install goes above Running, because connecting an agent to the deployed app is not the same errand as building the thing locally, and most people wanting the former never need the latter. It says what there is to configure — nothing — since a reader who has met other MCP servers will go looking for the API key that this one does not have. The MCP section links back to it, so the protocol detail and the packaged path are reachable from each other. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The install section covered Claude Code and stopped there, which reads as though a plugin were the only way in. It is not: a plugin is a Claude Code packaging format, and what it wraps is an ordinary remote MCP endpoint that claude.ai can be pointed at directly. The instruction is to paste the URL and leave the credentials blank, which is worth saying rather than implying — someone who has added other connectors will go looking for the client id this one does not need. That it works at all is a property of the server: registration is open and the token endpoint accepts `none`, so Claude can register itself as a public client and consent stays the boundary. Verified against production with an `https://claude.ai/...` callback. Two things do not carry over, so both are stated. The skill is part of the plugin, not the endpoint, so a connector gets the six tools and none of the guidance about `@page` and the allowlist. And a connector must be https on a public hostname, so the loopback trick above is Claude Code's alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
Packages
/api/mcpas an installable Claude Code plugin, so connecting is/plugin marketplace add afternoon/htmlcsspdfrather than a URL somebody has toknow and type into
claude mcp add.What's here
No credentials in the config
.mcp.jsonis four lines:type: "http"and the production URL. The endpointanswers an unauthenticated call with an RFC 9728
WWW-Authenticatechallengeadvertising
documents:read documents:write, and the client discoversregistration, consent and token exchange from there — so a config carrying a
client id would be describing a handshake that already works without one.
Verified against production; the challenge is live and names both scopes.
The skill is the part worth having
Two facts decide whether a document comes out right and neither fits in a tool
description:
@pagerule and nothing else. A stylesheet without onegets the renderer's default rather than the page you meant.
no
<svg>— so a document that draws its logo in markup saves without it andnothing says why. The full element and attribute lists are written down, along
with the allowed URL schemes.
It also records that
update_documentreplaces both panes, so an edit needs aget_documentfirst, and that rendering is deliberately not a tool.Checks
claude plugin validatepasses on both the plugin and the marketplace--plugin-dir; the skill registers ashtmlcsspdf:writing-documentsPOST /api/mcpreturns the expected 401 challengeNo application code is touched — this is additive packaging only.
🤖 Generated with Claude Code